It seems to me, that the best way is to have one Environment Varible containing the name of the SQL Server, so that you can look up the configuration in the SSIS Configuration Table when you run the package.
Is this the preferable way of doing it ? I would like to hear some positive/negative comment of why chosing a configuration type instead of another.
It seems to me that putting all of the configuration in the Environment variable is harder work but most secure (server breakdown vs table corruption/database error...)
Let's have some comments
http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2342.aspx
http://www.windowsitpro.com/SQLServer/Article/ArticleID/47688/SQLServer_47688.html
-Jamie
|||Jamie, You keep on posting this link to Kirk's article... and it looks like a good one; but it's on a for-pay site. Upon investigation it looked like there was a free registration there; but that doesn't seem to give me access to the articles. Is there a way to get these articles without subscribing? Or another link perhaps?|||
Not as far as I know. Maybe Kirk could better answer that question better.
Its unfortunate because it really is a very good article.
-Jamie
sqlsql
No comments:
Post a Comment