InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 23:06:16 GMT20http://www.sqlservercentral.com/Forums/Topic1382456-364-1.aspxOK...thanks.Fri, 09 Nov 2012 10:02:18 GMTCGSJohnsonhttp://www.sqlservercentral.com/Forums/Topic1382456-364-1.aspxFor the sake of readability I use option B. But this is a personal choice.Fri, 09 Nov 2012 00:33:29 GMTKoen Verbeeckhttp://www.sqlservercentral.com/Forums/Topic1382456-364-1.aspxThanks for the reply.Thu, 08 Nov 2012 07:29:43 GMTCGSJohnsonhttp://www.sqlservercentral.com/Forums/Topic1382456-364-1.aspxI'm accustomed to using the package variable, not a script-local one. But that's habit, not something based on actually comparing efficiency/performance/anything.Thu, 08 Nov 2012 07:23:23 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic1382456-364-1.aspxGood morning. I just have a quick question for you folks. Do you know if when using a Script task in SSIS, is it best practice to create a local variable to hold a value from a variable created at the package or container level, as opposed to just reading directly from the package/container-level variable? For example, out of scenarios A and B below, which is better/best practices?A:MessageBox.Show(Dts.Variables["strErrorDescription"].Value.ToString());B:string errDesc = Dts.Variables["strErrorDescription"].Value.ToString();MessageBox.Show(errDesc);Thanks...ChrisThu, 08 Nov 2012 06:20:23 GMTCGSJohnson