How do I migrate SSIS packages to a new server with a different name?
I need to migrate about 20 SSIS packages to a new server environment. The new server has a different name.
I am mostly concerned with the variables on each package and especially regarding server environments and pathing.
Let me know if I can provide any additional information to assist.
Microsoft SQL ServerSSIS
Last Comment
EugeneZ
8/22/2022 - Mon
Jim Horn
>I am mostly concerned with the variables on each package
You should be able to migrate the .dtsx without any changes, but in the scheduler (SQL Agent, ActiveBatch, whatever) that executes these package, as long as all connections to this server are parameter-driven, then pass the connection string to that parameter when scheduling the job.
You'll need to provide us more details on 'variables on each package' for a more precise answer.
You should be able to migrate the .dtsx without any changes, but in the scheduler (SQL Agent, ActiveBatch, whatever) that executes these package, as long as all connections to this server are parameter-driven, then pass the connection string to that parameter when scheduling the job.
You'll need to provide us more details on 'variables on each package' for a more precise answer.