Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS Package Configurations - Validation Warnings Expand / Collapse
Author
Message
Posted Thursday, May 22, 2008 2:47 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, March 24, 2014 8:46 AM
Points: 50, Visits: 128
Problem: Package configurations mean that some of the settings of the package (database connections, logging connections) are set to correct values after the package has started executing. This means the starting values will change from their incorrect setting to a correct value for the execution environment.

Solution: The DelayValidation option on Packages and objects (containers, connections, ect) can stop Validation messages meaning that they are not shown (unless the Validation pre-Execution fails which means that as execution is immenent chance of a valid value for the item is zero).

Actual Problem: The DelayValidation works for our x64 Xeon boxes, our IA64 single core dev box. What it doesn't do is work on our IA64 dual-core live machine. The same package executed usign a configuration file has different behaviour on the dual-core IA64 box.

The x64 Xeon test was against a DB on the IA64, with logging and connections also to that box. Permissions correctly setup so the job could run the SSIS on the x64.

Any ideas - has anyone else seen this behaviour??

It wouldn't suprise me if it was an IA64 "problem" - they are that good.
Post #505039
Posted Thursday, May 22, 2008 6:26 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 10, 2010 5:07 AM
Points: 2,732, Visits: 23,078
"are set to correct values after the package has started executing"

This is not correct. Package configurations are set before validation. Then validation is run, then pre-execute, then execute. You should not have to use DelayValidation to handle package configurations. You should only have to use DelayValidation is you are using expressions, variables, or script tasks to set connection information, or if you are doing something like copying an excel spreadsheet to the location that your excel connection manager is pointing to.

What sp of SSIS are you using?

You can further delay validation using sequence containers, so if you are finding that something is being changed further into your package than setting DelayValidation on the package can handle, throw everything that needs to be delayed into a sequence container and set the DelayValidation on the sequence container to True. This will delay the validation of the conponents within until the execution of the package reaches the sequence container and will actually not validate the components if the package execution never reaches the sequence container (if you had some conditional logic).
Post #505118
Posted Thursday, May 22, 2008 7:03 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, March 24, 2014 8:46 AM
Points: 50, Visits: 128
"Package configurations are set before validation. "

I am not here to argue about the exact timings of the Validation -> Package Execution -> Object/Container Pre-Execute Validation -> Execute Object/Container sequence.

It is a matter of fact that the package validation occurs before execution and expressions and the like are set. Therefore, if any non-trival configuration is done that changes values to be correct for the execution environment which would otherwise be invalid then DelayValidation has to be set to TRUE.

The Questions is:

Is there anyone out there that is using Itanium2 Servers (Dual-Core) and seeing a different behaviour for a package execution when compared to x64 Xeon and Single core Itanium2?

I get validation warnings on IA64 (DC) for connections, the same package executes on x64 Xeon with no warnings and it is ETL'ing to the same IA64 (DC) Sql Server engine. Is this a broken IA64 build WRT SSIS, at least in this regard?
Post #505148
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse