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

Package configurations Expand / Collapse
Author
Message
Posted Friday, September 26, 2008 11:31 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, June 30, 2014 1:23 PM
Points: 336, Visits: 866
Package configurations
Hi all..

Can anyone tell me how to use package configurations..
can we use them also if the sql authentication is required to be changed where we deploy our packages..

I mean what is the use of having a congiguration file in our deplyment...
wat does it reain when we deploy ir?

Do we need to edit it after deployment?

how?


any help is appreciated.
Thanks



---------------------------------------------------

Thanks
Post #577263
Posted Monday, September 29, 2008 7:10 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 1:13 PM
Points: 774, Visits: 1,734
Just go through the below link. Hope this would help you out.

http://www.sqlis.com/26.aspx
Post #577689
Posted Monday, September 29, 2008 9:53 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Thursday, August 7, 2014 3:54 PM
Points: 4,065, Visits: 5,296
You would have to edit the config file after creating it if you want to keep any connection passwords in it. Passwords aren't saved in the file, so you need to add them afterward.

Greg
Post #577818
Posted Tuesday, September 30, 2008 3:01 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, November 3, 2010 2:32 AM
Points: 1,249, Visits: 400
For me, package configurations all boil down to one thing - portability...

Basically if you have an environment where some level of change control is enforced, package configurations become sort of a not negotiable, wether you go for SQL or XML configurations.

Consider:
You are developing on your local C drive pointing to your local SQL server, or perhaps even a mapped network drive.
Now you need to deploy your package to a different machine where the job will be tested. For you to do this without package configurations, you would now have to manually go and update the package to point to the new drive letters.
After testing, your job needs to be productionalised. Once more you would need to change some settings to do this.

Why not simply have package configurations take care of all of this for you, have a configuration per environment. As an added bonus, once you have created a configuration, you can reuse it in multiple places provided you have the same naming conventions (which is a bonus as you now align to some kind of standard).

Some of the other benefits include for example when a setting changes. For example, what if a FTP site changes IP address? Are you going to go and change every package manually? Why not change it within your configuration and all your packages adjust automatically...

Good luck though, getting the understanding of Configurations going takes a while and a whole lot of discipline.

~PD
Post #578139
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse