MMDeveloper
asked on
Sql Server 2008 SSIS, disable pre-execute validation
I have an SSIS package that utilizes a "Script Task" on the Control Flow tab as the first step in the process. The package has a series of variables, but here are the ones pertinent to the question:
workingDistrict
sourceDB
workingDistrict is a variable that is set via the "Package Configuration" functionality.
The DataFlow tab has a series of "Flat File -> transformation -> OLE Destination" entries. The database connection utilizes the "sourceDB" variable in its connection string. The "Script Task" is a C# script that queries a database for configuration information (sourceDB, FTP folder names, etc) using the "workingDistrict" number in its query. It then assigns the query values to the package variables (such as sourceDB).
The problem is.... When the package is executed, it tries to validate the database connections BEFORE the script task is run. This obviously creates fatal errors because the connection string is incomplete at that time. If I manually enter data into the "sourceDB" package variable it will validate (which then the script task changes the variable values before the actual work begins).
Is there a way to tell SSIS to NOT validate the connections before runtime, or a way to turn off connection validation for a single entry in my Connections window?
workingDistrict
sourceDB
workingDistrict is a variable that is set via the "Package Configuration" functionality.
The DataFlow tab has a series of "Flat File -> transformation -> OLE Destination" entries. The database connection utilizes the "sourceDB" variable in its connection string. The "Script Task" is a C# script that queries a database for configuration information (sourceDB, FTP folder names, etc) using the "workingDistrict" number in its query. It then assigns the query values to the package variables (such as sourceDB).
The problem is.... When the package is executed, it tries to validate the database connections BEFORE the script task is run. This obviously creates fatal errors because the connection string is incomplete at that time. If I manually enter data into the "sourceDB" package variable it will validate (which then the script task changes the variable values before the actual work begins).
Is there a way to tell SSIS to NOT validate the connections before runtime, or a way to turn off connection validation for a single entry in my Connections window?
ASKER
I tried that but the error still happens. Looking deeper into the error message, it's the OLE DB Destination parts in the Data Flow portion of the package because it complains that the tables dont exist. I thought that your suggestion (after reading up on it) would prevent even the OLE DB Destination validations to hold off but (unless they have their own personal "delay validation" setting) it doesnt :(
Anything you can think for for Data Flow database references?
Anything you can think for for Data Flow database references?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok I'll do that when I get to work monday, I appreciate your suggestions
ASKER
beautiful, straight, concise answer, to the point, and 100% correct, thank you!
http://wiki.sqlis.com/default.aspx/SQLISWiki/DelayValidation.html
Greg