suppose in a Huge ETL loading about 1 million of Data and in between due to some error got failed, how can we start again that ETL from the last Failing POint instead of restating it from the Starting Point, can this be achieved by CheckPoint. please guide me in detail as i new of all this. many many thanks in advance. Regards, Amitesh Srivastva

Check point works at control flow and not in data flow so if data flow fails then you cannot restart from the point of failure. For further details check this link: http://www.mssqltips.com/tip.asp?tip=1408Nitesh Rai- Please mark the post as answered if it answers your question

Once solution could be re-directing the rows that fail the package to a new source. This way, all those rows that do not have any problems will be transferred successfully, and you can treat the failed rows based on the business logic the package is based on. Let me know if you need help in implementing this work around.Please mark as answer if this helps. Thank you. http://thebipalace.wordpress.com

Yes ,do me favour , i want implement this work, as per my business login there is a Scheduled DTS which transfer Millions of record from two SQL Server Source to one Destination Server on daily basis , now please guide me how should i act if this server fails in between of transfering Data from source to destination. how can i track that how much data have been transferred and how many still need to upload , will all transferred data be rollback or these will remain in destination , after failing will DTS start from the starting and will try to upload again the transfered data to destination. in gross i am completely confused, how this DTS works after failing in between of transfering millions record. please guide me in detail or let me know any valuable link regarding if there is any. tons of thanks in advance.Regards, Amitesh Srivastva

What are the cases that your ETL might fail? Is it because of a server going offline or because of data inconsistencies? Which one is your case??Please mark as answer if this helps. Thank you. http://thebipalace.wordpress.com

Hi, Refer this thread... http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/d8a2698a-f337-40f8-b542-697a04abc959 Regards, Guru

IT might be due to corrupted dataRegards, Amitesh Srivastva

you can add a datetime field at destination, and in the ssis package, right before starting the data flow task, just check the datetime field in destination db, and select data after that datetime. also this solution will only work if you have datetime field in source and you import data orderby datetime. Does it make sense to you?http://www.rad.pasfu.com

Use Datetime as Reza Raad suggested and also add one more column for Row Number./R.

If it is because of corrupted data,follow these steps to re-direct problematic data into another destination: 1- In the Error Output tab of your source component, select each row listed in "Column" column, and change the vale of "Error" column to Redirect Row, and click OK; 2- Add a new Destination component to your DFT, and name it as "Corrupted Data" (choose the type of destination component according to your needs); 3- Get the error output (the red arrow coming out of the source component) and connect it to the Corrupted Data destination component. These steps will make your package to run till the end, no matter there is corrupted data or not. The data that is not in a consistent format will be redirected to the new destination component. Cheers!Please mark as answer if this helps. Thank you. http://thebipalace.wordpress.com