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

ssis package deployment Expand / Collapse
Author
Message
Posted Thursday, June 20, 2013 5:01 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 30, 2013 5:00 PM
Points: 8, Visits: 33
Hi,

I have deployed an SSIS project that has one parent package which calls two child packages. want to deploy this project to sql server 2012. I use the sql server developer tools (VS 2010 shell) to disign my packages.

My packages use OLEDB connection managers (different oledb connection managers for each package pointing to the same connection).

I have set the expression for connectionstring property of each of these connection managers in every package. It looks like follows:

"Data Source="+ @[$Project::DataSource] +";User ID="+ @[$Project::UserName] +";Pwd="+ @[$Project::Password] +";Initial Catalog="+ @[$Project::InitialCatalog] +";Provider=SQLNCLI11.1;Persist Security Info=True;"

I have 4 project parameters for data source, username, password and initial catalog.

Now when I deploy the package to my local machine, (which has the same server name as I used while designing the package) it runs fine. For this, I had to create SQL server agent jobs for each of 3 packages and change the "Execute Child Package" task in the "Main Package" to "Execute SQL Server Agent Job" task.

In the Job step properties >> Counfiguration tab >> Parameters for the Job for Main package, I set the parameter values to point to the server that I deployed the report on. But in the connection Managers tab, the values stay the same as the design time values.

Is it something I have to set for every package? Is the overall design I did bad?
The thing is, I want to be able to deploy the package on any server with minimal changes.

I have gone through following links, but they explain the deployment and design for sql server 2008.

ssis package deployment - part 1
ssis package deployment - part 2

passing values to child packages - youtube
deploying ssis package designed ib above link - Youtube

I am a n00bie. Please correct me if I have used any term incorrectly.
TIA.
Post #1465991
Posted Thursday, June 20, 2013 11:08 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, September 21, 2014 6:45 PM
Points: 20, Visits: 103
Try the following link for deployment to 2012 using the project deployment method
http://msdn.microsoft.com/en-us/library/hh231102.aspx
and
http://sqlmag.com/sql-server-integration-services/ssis-deployment-sql-server-2012
Post #1466042
Posted Friday, June 21, 2013 1:49 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 30, 2013 5:00 PM
Points: 8, Visits: 33
Thank you so much! 2nd link was very helpful. It explains creation of environments so clearly.
Post #1466081
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse