March 23, 2009 at 2:38 pm
I am a total newbie to SSIS, so please bear with me.
I wrote a fairly simple SSIS package and had it working in development. I imported it to our production box, but now the datasource still shows the development server name. When I change the datasource on the production box to contain the production server's name, I can manually run the job one time with success. But the new server name doesn't stay. It reverts back to the development server name.
I want to schedule the job to run daily, but didn't want to have to re-write the package on the production server. What are my options to change the datasource name on the prod box? Can I make a one-time change or else read a flat file that contains the server name or ... something?
March 23, 2009 at 3:23 pm
Switch package configurations on, then when you deploy, change the connection string to the production server.
March 23, 2009 at 4:03 pm
Hey that's great! But how do I do that?
If I look at Project menu --> properties --> Configuration Properties --> Deployment Utility -->
AllowConfigurationChanges was already set to true.
March 23, 2009 at 4:23 pm
Click in the main window, then on the menu bar SSIS->Package Configurations. Tick the box "Enable Package Configurations", click Add, give the config file a name etc etc.
Word of advice - we have found it is easiest to have a directory on both the Target server, development server, test server AND the development PC's of the same name. We use "C:\SSISDeploymentInstall\" to hold all our configuration packages.
Deployment is easy: (wish I could figure out how to add images without having a webserver at my disposal...)
When deploying, choose "SQL Server development", click on next, browse to the folder you chose above (c:\ssisdeploymentinstall), edit the config file contents (if necessary), specify the target server details, tick "Rely on SQL Server storage for encryption", click Next, then Finish.
RDP into the server, copy the file from wherever you put it to the SAME folder on the server (C:\ssisdeploymentinstall)
Start in Integration Services session
Navigate to the Stored Packages->MSDB->yourpackagename, right click, select "Run Package"
Click on Configurations (then wait a long time...)
Add your configuration file
Click on Execute (will give you a final opportunity to alter your config settings).
Create the schedule after the package has run successfully.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply