Wednesday, February 27, 2013 7:19 PMWould you normally only set ValidateExternalMetaData to False if you did something such as creating a table in a previous task? Is there any other time or other reason why this would be set to False?
Wednesday, February 27, 2013 7:28 PMModeratorAlso helps when using the transactions and better than setting the Delayvalidation to false for the entire package!
Arthur My Blog
Thursday, May 09, 2013 8:33 PM
You'd do this anytime you are sure you don't need to worry about the table schema being out of sync with your package. Creating the table in the previous task is a great example.
There are cases when external metadata validation can be expensive (lots of columns, remote database, slow database server). In these cases, setting ValidateExternalMetadata can improve performance of the validation phase. However, when you do this you run the risk of hitting some weird runtime errors if your package metadata is in fact out of sync with the underlying table. At best you'll fail with an error, at worst the package continues to run with column data in the wrong columns!