September 26, 2013 at 5:37 pm
I made a practice problem for myself - Using SSIS, make a package to load data from text files located on a Server P, load these files into a table in Server Q. Can I also run this package from a third Server R ? Or should the package be run from Server Q itself because that is where the destination tables are.
Main task - It is easy to load it from my local machine. But, how do I load text files from a different server, i.e not on my system which has the SSIS ?
September 26, 2013 at 10:04 pm
The server name in the connection manager you use for servers P and Q determines where you get or send data to. SSIS doesn't really care. It simply connects to the server/database defined in your connection and then does what you ask it to do.
September 26, 2013 at 10:07 pm
etl.laptop (9/26/2013)
I made a practice problem for myself - Using SSIS, make a package to load data from text files located on a Server P, load these files into a table in Server Q. Can I also run this package from a third Server R ? Or should the package be run from Server Q itself because that is where the destination tables are.Main task - It is easy to load it from my local machine. But, how do I load text files from a different server, i.e not on my system which has the SSIS ?
As long as the connections are defined using 'full' naming conventions (UNC paths for files and not localhost etc for the SQL Server instances), you shouldn't have any problems. Except for when the job is scheduled to run under SQL Agent - then you will have permissions problems on the file access because of the context in which SQL Agent runs (I'd say that this is FAQ #1 for SSIS forums).
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
September 26, 2013 at 10:11 pm
100% Possible.
but should have the adequate permissions.
September 27, 2013 at 12:11 am
etl.laptop (9/26/2013)
I made a practice problem for myself - Using SSIS, make a package to load data from text files located on a Server P, load these files into a table in Server Q. Can I also run this package from a third Server R ? Or should the package be run from Server Q itself because that is where the destination tables are.Main task - It is easy to load it from my local machine. But, how do I load text files from a different server, i.e not on my system which has the SSIS ?
The only restriction you could have is when you use the SQL Server Destination. This component can only be used when the SSIS package is run on the destination server. All the more reason to avoid it.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply