|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 1:39 PM
Points: 2,818,
Visits: 1,038
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, March 06, 2013 3:02 PM
Points: 268,
Visits: 1,055
|
|
Thats a really neat approach. Good article.
Kindest Regards,
Frank Bazan @Bikeride2Africa
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 2:53 PM
Points: 375,
Visits: 947
|
|
Hi Scott,
Great article and excellent use of SSIS Package Configurations. I really like centralizing the application tier (Dev, Test, Prod) selection at the configuration server. Elegant solution.
How would you apply this to environments with firewalls between application tiers? I've used a two-step approach with an environment variable that points to a configuration database for individual tiers.
Andy
Andy Leonard CSO, Linchpin People Follow me on Twitter: @AndyLeonard
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:11 PM
Points: 143,
Visits: 183
|
|
Scott:
Excellent article! Your insight to the configuration issue is spot on and brings with it a tremendous amount of merit.
When you mentioned that you started with the group and discovered all the great opportunities to improve things (newly ported DTS packages to SSIS with no CFG file), I thought about how you went about deriving your clever solution and the angst from your peers and management in terms of your future implementation plan for integrating. I wonder how tough of a "sell" it was to your peers and management. This is ALWAYS where the rubber meets the pavement...delivery of the concept is key and requires a grass roots or bottom up sell.
It seems this is where some of us get into trouble when conveying a solution to a problem and managing the push-back from others. Your solution is obvisouly clever and in my opinion extremely well-thought out. Your solution here is a testament to your future success.
Kudos.
-M
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 11:55 AM
Points: 1,
Visits: 44
|
|
Any chance you can post sample of your technique to swap connections based on environment dynamically. Thanks
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 1:39 PM
Points: 2,818,
Visits: 1,038
|
|
Andy Leonard (6/3/2009) How would you apply this to environments with firewalls between application tiers? I've used a two-step approach with an environment variable that points to a configuration database for individual tiers. I considered this issue, and that is the best approach I could think of. You need a separate configuration table for each isolated network, but you still have the benefit of only needing one version of the package that can be deployed anywhere without modification.
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 1:39 PM
Points: 2,818,
Visits: 1,038
|
|
Mike DiRenzo (6/3/2009) I wonder how tough of a "sell" it was to your peers and management. This is ALWAYS where the rubber meets the pavement...delivery of the concept is key and requires a grass roots or bottom up sell. It wasn't a tough sell because there weren't a lot of ingrained bad practices to change, and because I work with people intelligent enough to recognize a better approach. (And who may read these comments. )
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 10:08 AM
Points: 282,
Visits: 2,126
|
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 1:39 PM
Points: 2,818,
Visits: 1,038
|
|
Simon Storey (6/3/2009) Any chance you can post sample of your technique to swap connections based on environment dynamically. The article describes a way of managing multiple package configurations easily, it assumes the reader already has some knowledge of configuration usage. The example package in the article only modifies some package variable values, but it works the same way for connection manager properties, task properties, or anything else you want to configure.
1. Create a package with a connection manager. 2. Use package configuration to put the connection manager properties in a SQL table. 3. Use the techniques in the article to supply multiple values.
The SSISConfiguration.sql file linked under "Resources" in the article has all the code.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, March 15, 2013 2:43 PM
Points: 3,924,
Visits: 1,554
|
|
Very good article and a very comprehensive approach, Scott. Was using same tech for single server but had not for multi-environment. Would definitely try out in near future.
Again, thanks for the sql configuration.sql
SQL DBA.
|
|
|
|