Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

SSIS Common Configs Expand / Collapse
Posted Monday, March 14, 2011 7:56 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, June 17, 2016 11:54 AM
Points: 34, Visits: 526
That may be where I go with it. While the common configuration may be convenient in the respect that we can indicate several configurations with one config filter, it is introducing a stigmata in putting packages in production that are throwing warnings. The warnings are not keeping the package from running successfully, but any time I see warnings on a package going into Production, I have issues, harmful to the package or not.

I will likely scale back to single configs, and give MS ideas on how to sculpt Denali to better handle this situation. I don't want to necessarily suppress ALL configuration warnings - some may be legit.

Karl Lambert
SQL Server Database Administration
Business Intelligence Development
Post #1077710
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse