Comments on: SQLAuthority News – Best Practices for Integration Services Configurations http://blog.sqlauthority.com/2009/10/25/sqlauthority-news-best-practices-for-integration-services-configurations/ Personal Notes of Pinal Dave Fri, 10 Feb 2012 04:45:32 +0000 hourly 1 http://wordpress.com/ By: bob http://blog.sqlauthority.com/2009/10/25/sqlauthority-news-best-practices-for-integration-services-configurations/#comment-82714 Mon, 02 Aug 2010 17:01:45 +0000 http://blog.sqlauthority.com/?p=7106#comment-82714 Pinal:
Have you ever had success in abstracting out the usernames and passwords from SSIS packages so that the packages can be developed in a development environment, and then moved into a production environment without changing the package? Have you ever HEARD of this being done?

it seems the usernames and passwords are included in the package (bad design microsoft), so that the data center is left with two options: (1) edit the package after it’s been QA’d (violates standard QA process of “what we tested goes into production”) or (2) have the same usernames and passwords for both development and production (VERY BAD DESIGN).

until this can be resolved, we’re using compiled languages for our imports and exports.

]]> By: Ramdas http://blog.sqlauthority.com/2009/10/25/sqlauthority-news-best-practices-for-integration-services-configurations/#comment-57036 Mon, 26 Oct 2009 13:51:51 +0000 http://blog.sqlauthority.com/?p=7106#comment-57036 Hi Pinal,
In my usage of SSIS usage, I have used and found the XML configuration option to be really effective and neat, second option would be the SQL Server Configuration option.

]]>