Manual validation of external metadata

Hi,

is there a way to start validation of external metadata manual?

My problem is this:

The package uses a variable as connectionstring for flatfile source, and another variable for the destination table. Running the package gives a warning about external metadata that needs to be updated. Normally I update this data by just opening the data flow, and answering the question for updating with yes. This time that deosnt work, I think because the variable is not set, so there can not be any conflicts with external metadata.

I dont want do disable validation, but just validate one time and then save the package.

Any ideas?

Regards,

Jan

Not sure I got the problem...but have you looked at the DelayValidation property of the flat file connection manager and destination component. Also make sure you give some values to those variables at design time.|||

Hi Jan,

I dont want do disable validation, but just validate one time and then save the package.

I'm not sure this is an option without setting DelayValidation to True for the package. Validation occurs at different times for different objects. For instance, when the package is opened in the development environment, some validation occurs - things like Connection Manager connections are tested, etc. When the package is executed, some other validation is performed.

There's a great description of this here.

Hope this helps,
Andy

|||

Hi,

I tried to set option delayValidation to true, but this didn't help.

My package still logs warning messages because the metadata are not updated, but I cant update them without running the package, but while running the package I don't see a way to update metadata. That's my dilemma.

Regards,

Jan

|||

Hi Jan,

Is it possible to set the variables to a Development instance of SQL Server? The values will still be updated at runtime and if they're not, the worst that will happen is they'll execute against Development.

Hope this helps,
Andy

|||

Hi Andy,

unfortunately it is not an option for me to set the variables to an development instance, because that would not help.

My variables are filled up dynamically with the right values on runtime, and because this is done in a for-each container a lot of values are set. After each iteration the data flow task is started, and this causes in warnings for the metadata. I would need to set each possible value in every variable, disable my scripttask und run the package "manually" step by step. This is my problem with SSIS: sometimes it seems that SSIS wasn't developed for dynamic use, cause everytime you use it this ways you get stopped by strange problems like these.

What I dont get is why doesnt SSIS give me an option to update metadata on runtime, instead of warning me that they needs to be updated, without giving me the possibility to do that....

Thanks for all your help and ideas, I think I will just ignore the warnings.

Regards,

Jan

|||

By any chance are you changing column names or data types in the source/destination components; if so I am afraid that would break the data flow...changing the path or file name of a flat file connection manager; or table names would be fine for SSIS though...