Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Data Warehousing
»
Integration Services
»
Created package on one server, how to use it...
Created package on one server, how to use it in another server ?
Rate Topic
Display Mode
Topic Options
Author
Message
SQL Guy 1
SQL Guy 1
Posted Saturday, September 22, 2012 7:26 PM
SSC Veteran
Group: General Forum Members
Last Login: Yesterday @ 3:12 PM
Points: 268,
Visits: 823
Hi all,
Maybe this is a trivial question, but I am relatively new to SSIS.
I created a SSIS package in BIDS, with connection manager pointing to server1. I deployed it to server2. But the connection manager still shows server1. I may not make any changes to package when it is on server2 (server1 and server2 are identical, the former is dev and the latter is QA).
How can I make connection like "server independant" ? What I mean is whenever I deploy it to a new environment, it will connect to appropriate server. Are there any best practices for this ?
Thanks.
Post #1363184
opc.three
opc.three
Posted Sunday, September 23, 2012 8:14 AM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 1:24 PM
Points: 6,826,
Visits: 11,950
You have numerous configuration management options in SSIS. Personally I like using XML Package Configuration files for this kind of work. When I deploy a package to 'dev' or am working locally I have the 'dev' configuration file in place containing the environment-specific configuration settings relevant to my dev environment. When I push the package to QA I also deploy the 'QA' configuration file with it which has the exact same structure as my 'dev' configuration file but with the values changed for QA. Note that while the data-values within the configuration file are different between dev and QA the XML structure is identical and the physical path to the file must be the same on all machines, e.g. if you point the SSIS package to D:\SSISConfig\MyPackageConfigurationFile.dtsConfig to get the config file in dev then the file must exist there on the QA machine as well.
Understanding Integration Services Package Configurations
Package Configurations
__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Believe you can and you're halfway there.
--Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler
--Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them.
--Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples.
--Giordy
Post #1363230
SQL Guy 1
SQL Guy 1
Posted Sunday, September 23, 2012 12:53 PM
SSC Veteran
Group: General Forum Members
Last Login: Yesterday @ 3:12 PM
Points: 268,
Visits: 823
Thanks, XML config file looks like good idea, I did not start reading the links provided, but first question that I have is : When a XML config file is present, SQL Server just ignores entries in Connection Manager ?
What I mean is for example I created a package and in its Connection Manager server name is SQL_DEV. I deployed this package to another machine which is QA, and in that machine I have XML file with entry SQL_QA, but the package itself still have SQL_DEV.
In this case SQL_DEV will just be overriden ?
Thanks
Post #1363282
opc.three
opc.three
Posted Sunday, September 23, 2012 1:17 PM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 1:24 PM
Points: 6,826,
Visits: 11,950
The short answer is yes, the settings in the configuration file will be used instead of the info hardcoded into the Connection Manager object.
There is an order of precedence on how configuration data is applied at runtime which you can read more about in Books Online. It gets more complicated as you start adding things like setting variables from the DTExec.exe command line and using variables.
__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Believe you can and you're halfway there.
--Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler
--Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them.
--Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples.
--Giordy
Post #1363284
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.