Hi, I am creating Excel table using Sql Task and then trying to populate data into that table. I am facing problem in executing the package. I can able to execute each task separately but no the whole package. Please help me

Are you trying to diagnose the issue? if so, in the control flow tab you can disable tasks by right clicking the task and selecting disable and run it interactively but you cannot disable data transformation tasks within a data flow task. You may need to provide a more information.

I am trying to populate data from a table to Excel destination. But i need to create the Excel dynamically. Excel file not exists already. Please help me on this

you can use an excel template file (by template I mean an excel file with just structure, for example column headers but without data), then use File System Task to generate a copy of the excel file. then you can use this new copy in Excel destination with help of expressions property of excel connection manager. http://www.rad.pasfu.com

But the Excel file in the destination folder will be deleted by other process as it generated. I am creating the Excel file using Execute Sql task and making delay validation = "TRUE" fro the next next DFT , i can populate the data. But is that a right way to do it.

Yes, for the case where the file might be deleted by a different process, the Excel Destination's delay validation property should be set to 'true'. As Reza mentioned, you should keep a template in any root folder and copy the template (using file system task) to the destination before you populate. After the template is copied, you can populate the data. For the next package execution, the template will be copied again, so, you dont have to worry about the previously populated file being deleted by a different process. Don't forget to handle the file names properly while copying the template just in case if the previous file is not deleted.

In the DFT you may be using File Excel Source componentTake the connection used by excel source component, go to connection propertiesGo to expression and variablize the same first (@file_path+@file_name)If generated excel file name is same all the time then hard code the name in variable (or take it from configuration) else use for each loop container and get the file name from it.Set delay validation to true (DFT or inside excel source component)Run your package I have given steps in detail because out of this any 1 or 2 may be missing. Regards, YB

hi Brown256, Check this out, this will help you: http://www.codeproject.com/Articles/301542/Creating-Excel-File-and-ExcelSheets-dynamically-fr http://www.codeproject.com/Articles/368530/Dynamic-Excel-file-loading-with-SSIS Thanks, Khilit http://www.bigator.com

But the Excel file in the destination folder will be deleted by other process as it generated. I am creating the Excel file using Execute Sql task and making delay validation = "TRUE" fro the next next DFT , i can populate the data. But is that a right way to do it. when excel file will be deleted, there will be no difference where you created it, with FIle system task or with execute sql task! but if your solution is working, go with that solution. setting DelayValidation to true will overlook validation at the compile time of package, but will do that in runtime, and in runtime mode destination file will exist so you will be finehttp://www.rad.pasfu.com

But the Excel file in the destination folder will be deleted by other process as it generated. I am creating the Excel file using Execute Sql task and making delay validation = "TRUE" fro the next next DFT , i can populate the data. But is that a right way to do it. when excel file will be deleted, there will be no difference where you created it, with FIle system task or with execute sql task! but if your solution is working, go with that solution. setting DelayValidation to true will overlook validation at the compile time of package, but will do that in runtime, and in runtime mode destination file will exist so you will be finehttp://www.rad.pasfu.com