April 23, 2013 at 2:41 am
I am using SSIS 2008. The task is following.
1: Execute a storted proc and using the output create a CSV file.
2: this CSV file need to be copy to network drive e.g. (\\servername\datafolder)
please suggest what is the easiest way to acheiev this.
April 23, 2013 at 3:48 am
Use a dataflow. Put an OLE DB source and use your stored procedure there.
Link it to a flat file destination. In the flat file connection manager, configure the file name and your network path as the destination.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 24, 2013 at 7:54 am
Karan_W (4/23/2013)
I am using SSIS 2008. The task is following.1: Execute a storted proc and using the output create a CSV file.
2: this CSV file need to be copy to network drive e.g. (\\servername\datafolder)
please suggest what is the easiest way to acheiev this.
You may already know this, but depending on how the SSIS package is executed (scheduled in SQL Agent job, run manually from SSMS, etc.) it could run either locally on your PC or remotely on the server. Also, insure that account under which the package will execute has access to the file system and network resource.
http://blogs.msdn.com/b/michen/archive/2006/08/11/package-exec-location.aspx
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 24, 2013 at 9:01 am
Eric M Russell (4/24/2013)
Karan_W (4/23/2013)
I am using SSIS 2008. The task is following.1: Execute a storted proc and using the output create a CSV file.
2: this CSV file need to be copy to network drive e.g. (\\servername\datafolder)
please suggest what is the easiest way to acheiev this.
You may already know this, but depending on how the SSIS package is executed (scheduled in SQL Agent job, run manually from SSMS, etc.) it could run either locally on your PC or remotely on the server. Also, insure that account under which the package will execute has access to the file system and network resource.
http://blogs.msdn.com/b/michen/archive/2006/08/11/package-exec-location.aspx
Good advice indeed. If everyone knew this, there would be approximately 12 million fewer Internet pages containing requests for help along the lines of: "My package runs fine in BIDS but fails when scheduled as a SQL Agent job"!
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply