December 7, 2006 at 6:00 am
I have found a very usefull article on how to export data to a text file using the bcp utility. Unfortuatly I want the calling SP to save the file to the clients drive instead of a drive on the server.
My code so far is:
Is there a way that I can
December 8, 2006 at 10:25 pm
I'm thinking that a couple of things are missing on this post, but, you can write to the client machine if you use a UNC path AND the SQL Server Service logged in as a power user that can see the client's machine AND has r/w privs in that particular directory.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2006 at 9:44 am
seems like a better solution would be to write the file to a file or web server that the sql server has write perms to, and then return the (web or unc) path to the file from the sproc. then the client just downloads the file after calling the sproc.
Otherwise you have all kinds of messy perms issues between the sql server and EVERY client machine to work out.
---------------------------------------
elsasoft.org
December 9, 2006 at 12:40 pm
Absolutely agree... but lot's of folks have designated "work horse" machines where they might download raw CDR's or other info to and then point SQL Server to that box to get the data. Keeps the server drives free from raw data and provides another layer of protection from the outside world.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply