I am wondering if sql server 2008 r2 integration services can accomplish the following task(s) and/or at least part of the following tasks? My company recieves an excel woorkbook 2003 from our customer daily. The data that needs to be loaded to the sql server database is always on the 6th tab in the workbook. The problem is sometimes there are links to other parts of the spreadsheet we do not have access to when we receive the file. Also some of the columns and/or rows may be hidden. I know my company will not ask the customer to change the way we receive the data. We need to just take the data the way we receive it. Thus can you tell me what task(s) SSIS can complete and where I need to place error handling logic to account for the tasks SSIS can not complete? Also, can you point me to a reference how to setup error handling in SSIS?

I personally would say to the person requesting the import. If you are not willing to get the data in a usable format - then continue doing whatever manual process you are doing right now. The situation you are describing is a no win for the person developing and supporting the ETL process. Excel is a horrible data source to begin with, but the workbook you are describing is even worse than the norm.Chuck

you can use use ssis even handler for customised error handling. ssis also contains logging for error but using event handler its the best method.Regards, nishantcomp2512 Please mark posts as answered where appropriate

Can you give me more details for using logging and the event handler