Hi, What's better, enabling or disabling the lock escalation in the tables? I have a large table to load (30Gb), during the loading there is no read access to my tables. so nobody will be locked. what the best lock escalation option? also what are the best option for the indexes used in the destination tables? I read some articles about this, but there is no clear path as they talk about reducing the lock duration while I want to reduce the loading time and the memory usage. thanks.

The best is to disable (Table Lock) it if you have access (Update/delete/insert) on the table, but if during the Load you dont have acess then enable the "Table Lock" in SSIS OLE_destination table Index: if you have your final destination tables Index , you cant do anything about it what we have we load 300Mil records so the final destination tables have Indexing but no relation or F-Key, we have a Auditing system that evaluated the records before the ETL starts basically it is playing a role of f-key check and constrain and integraty check good luckSincerely Nik -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

The best is to disable (Table Lock) it if you have access (Update/delete/insert) on the table, but if during the Load you dont have acess then enable the "Table Lock" in SSIS OLE_destination table Index: if you have your final destination tables Index , you cant do anything about it what we have we load 300Mil records so the final destination tables have Indexing but no relation or F-Key, we have a Auditing system that evaluated the records before the ETL starts basically it is playing a role of f-key check and constrain and integraty check good luckSincerely Nik -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).