InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 03:40:03 GMT20http://www.sqlservercentral.com/Forums/Topic569123-31-1.aspxThanks for the presentation. I use variables in stead of a connectionstring myself for a while. The reason is that it makes it easy to switch between test and production server. I even added a small script as a first step to my package. When this step fails, I know I made a mistake in the server name.Sat, 27 Sep 2008 02:02:12 GMTRené Kapiteinhttp://www.sqlservercentral.com/Forums/Topic569123-31-1.aspxBrian,Our development group currently uses this same method to dynamically assign connections as well. What I am curious about is that you stated it was better to assign the dynamic values to the database and server values rather than the connection string. Could you elaborate further? In our environment we have been assigning the dynamic value to the connection string and I am wondering if by doing that is that the source of the problems we seem to have when promoting SSIS packages to our production environment and the server names are different.Thu, 25 Sep 2008 05:26:50 GMTSheldon Williams-262462http://www.sqlservercentral.com/Forums/Topic569123-31-1.aspxYou are inspiring me to develop something .....Thu, 25 Sep 2008 03:24:49 GMTAnipaulhttp://www.sqlservercentral.com/Forums/Topic569123-31-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Video/64262/">Making SSIS Connections Dynamic - SQL School Video</A>[/B]Sat, 13 Sep 2008 20:04:45 GMTBrian Knight