Hello Friend, I am trying to use Execute SQL task in my SSIS package. basically i need to run script which will create 4 tables in the database then it should execute the data flow task which will load the data from Access file but when i try to run the package i get an error that table does not exist ..but i am not getting it when the first step is to create the table then it should go to next step which is loading the data from Access file?

Set the ValidateExternalMetadata property of the OLEDB Source to false. This will delay validation of the command until the package actually runs the DataFlow. By that time your tables should have been created.Russel Loski, MCT, MCITP Business Intelligence Developer and Database Developer 2008 Blog: http://www.bidn.com/blogs/RussLoski/ Twitter: @sqlmovers

Thank you Russ for your quick response...but i am still getting the same error......I am using execute sql task and using direct input to enter my create table script but it is not working as i mentioned above --Please check the screen shot below for more infomation

Creating tables on the fly inside an ssis package is bad design, you are combining a database design/administration task with ETL. Create your tables first in the database (preferably have the prod dba do it during a maint window) And then create the ETL in your SSIS package.Chuck

Thank you Chuck..I understand that it is not a good idea to create table inside an ssis package but i was just wondering if it is at all possible to do this way..(creating table inside ssis and then load the data through same package)

Hi VATiger, Please set DelayValidation to True on package elements whose configuration is not valid at design time to prevent validation errors. I assume 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 information about it, please see: http://www.powerpivotblog.nl/open-ssis-packages-without-validation-using-these-sql-properties http://msdn.microsoft.com/en-us/library/ms137625.aspx Thanks, Eileen

Hi VATiger, Please set DelayValidation to True on package elements whose configuration is not valid at design time to prevent validation errors. I assume 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 information about it, please see: http://www.powerpivotblog.nl/open-ssis-packages-without-validation-using-these-sql-properties http://msdn.microsoft.com/en-us/library/ms137625.aspx Thanks, Eileen

Hi, May be you missed out to put the connection between your "Execute SQL Task" and "Data Flow Task" tasks. As SSIS executes the tasks asynchronously there is a chance of your "Data Flow Task" will executes first before executing the "Execute SQL Task" task. Hope it helpful.Please Mark it as Answered if it answered your question OR mark it as Helpful if it help you to solve your problem --Kiran

Thank you so much Eileen...Your method worked!! You guys are great