I have an SSIS package that I created that looks like the following:
When I run this package inside Microsoft Visual Studio I get the results I want. It sends the file to the network drive and because there are SSN's in the file, it doesn't actually e-mail the file but puts it in a secure location for the person to get the file.
When I schedule this in SQL Server 2005 I get the file saved to: c:\windows\system32\dynamicfilename.csv
So somehow it is still able to determine what the file name should be, but instead of sending the file to the right destination when you run it through VS, it flops out and sends it to this wacky directory.
I've spent too much time on this and was wondering if someone can point me in the right direction without going to the extent of writing a script like this suggests. thread1555-1265108
Thanks,
Keith
Code:
Execute SQL Task [Determines the file name]
Data Flow Task
Source - Query [Grabs the data]
Destination [Saves data to file on network drive]
Send Mail Task [Tells user to get file from network]
When I run this package inside Microsoft Visual Studio I get the results I want. It sends the file to the network drive and because there are SSN's in the file, it doesn't actually e-mail the file but puts it in a secure location for the person to get the file.
When I schedule this in SQL Server 2005 I get the file saved to: c:\windows\system32\dynamicfilename.csv
So somehow it is still able to determine what the file name should be, but instead of sending the file to the right destination when you run it through VS, it flops out and sends it to this wacky directory.
I've spent too much time on this and was wondering if someone can point me in the right direction without going to the extent of writing a script like this suggests. thread1555-1265108
Thanks,
Keith