You can set DelayValidation to True on package elements whose configuration is not valid at design time to prevent validation errors. For example, you may have a Data Flow task that uses a destination table that does not exist until an Execute SQL task creates
the table at run time. The DelayValidation property can be enabled at the package level, or at the level of the individual tasks and containers that the package includes. Normally you must leave this property set to True on the same package elements when you
deploy the package, to prevent the same validation errors at run time. For more details about it, please see:
Troubleshooting Tools for Package Development:
If the issue still persists, what is the error message appeared? Please supply more information about the issue, then we could help you better.
Marked as answer byEileen ZhaoMonday, August 06, 2012 5:56 AM