June 22, 2010 at 2:43 am
What are the methods available to move SSIS packages (SQL 2008 to 2008) from Test server to Prod server?
1. Using Package config(XML, Table etc)
2. ????
June 22, 2010 at 3:01 am
Have you tried importing the DTSX packages from one SSIS instance to another?
Ensure you add encryption on them should there be stored passwords etc in them.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
June 22, 2010 at 3:15 am
Yes, tried import of DTSX files from msdb(test) to msdb (prod). But since the server/dbnames are different in test and prod, I have to manually change all the connections. Problem is, I have around 40 to 50 packages. I found deploying and other methods easier for such moves.
June 22, 2010 at 3:28 am
You should set-up a configuration file or config table for each environment.
Then point to this config file/table with an environment variable (this has its advantages and disadvantages, but I'm not going deeper into that topic).
Configure your packages with package configurations. That way, when you copy the package to another environment, it is automatically configured with the correct configuration values.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 22, 2010 at 6:53 am
This was removed by the editor as SPAM
June 23, 2010 at 9:19 am
I have used the deployment utility and I was, underwhelmed..
I think a better method was reference by da-zero, package configurations, using either files or a table. I have used the file method with GREAT success, the package is developed on my workstation and can then be put onto any server because the config information is stored externally. This gives me two important effects.
1. The code is the same between Dev, Test, and Prod. I KNOW that the code was not changed and the package IS the same from when I released it.
2. I can put both the config files and the DTSX in source control.
CEWII
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply