Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Copy a CSV file to another network drive Expand / Collapse
Author
Message
Posted Tuesday, April 23, 2013 2:41 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, September 26, 2014 6:20 AM
Points: 41, Visits: 125
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.
Post #1445315
Posted Tuesday, April 23, 2013 3:48 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 8:15 AM
Points: 13,017, Visits: 10,800
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.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1445334
Posted Wednesday, April 24, 2013 7:54 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 2:56 PM
Points: 1,677, Visits: 4,785
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
Post #1445987
Posted Wednesday, April 24, 2013 9:01 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:10 PM
Points: 5,103, Visits: 11,906
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"!



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1446050
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse