Koen Verbeeck (9/20/2012)

---

Your mistake is in using the OLE DB Command for doing updates, which is very, very slow.
Try writing the rows to a staging table and do an UPDATE using TSQL in an Execute SQL Task.

Koen Verbeeck (9/21/2012)

---

Could have been anything. Syntax is probably correct, otherwise it would have errored out.
Maybe a deadlock or something?

Charmer (9/21/2012)

---

I am the only one who is using this table..i can say this database even...so i believe dead locking is not going to be the reason...but it is having 11 million records to be updated...Koen, is that one of the reason?

Koen Verbeeck (9/21/2012)

---

11 million records? Dump the OLE DB command and use a staging table. Unless you like waiting for a few hours for your package to finish.

Charmer (9/21/2012)

---

Even the staging table will be having 10 million records....so Koen, could you tell me how useful it will be? i mean for updating.....

Koen Verbeeck (9/22/2012)

---

Very useful.
Try updating 11 million rows row by row resulting in 11 million different updates and thus 11 million records in the transaction log, or try updating 11 million records in one single transaction/update.

Charmer (9/25/2012)

---

What i do here is, pushing all records into Staging table and using a Execute SQL task to update all the rows in single transaction....well, the way i do is good or any other better way? Could you tell me, Koen?