Comments on: SQL SERVER – Time Out Due to Executing DELETE on Large RecordSet http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/ Personal Notes of Pinal Dave Fri, 17 May 2013 15:26:57 +0000 hourly 1 http://wordpress.com/ By: SQL SERVER – Weekly Series – Memory Lane – #012 « SQL Server Journey with SQL Authority http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-409568 Sat, 19 Jan 2013 01:30:54 +0000 http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-409568 [...] Time Out Due to Executing DELETE on Large RecordSet There are many differences between truncate and delete but I have seen people using them interchangeably without thinking much. In this blog post, the difference is explained with the help of other similar articles. It is not a good idea to use TRUNCATE right away if you DELETE is timing out. The best practice should be to understand the difference. It is also a good idea to delete the data in smaller batch instead of larger batch. [...]

]]> By: Jim P. http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-283919 Fri, 11 May 2012 16:56:34 +0000 http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-283919 >> Also TRUNCATE is not so useful when you are deleting “conditionally”

I do it as a while loop — something like this

while (select count(1) from mytable where indexnum 0
begin
delete top (5000) from mytable where indexnum < 100000
end

That loops through and takes out in chunks. It will grow your tran log, but it shouldn't be as bad, and you don't face a time out issue.

]]> By: naren http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-80498 Fri, 16 Jul 2010 10:32:51 +0000 http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-80498 Hi Pinal,

When i am tryign to use the dbcc

DBCC CHECKIDENT (Schools.tblCaste,reseed,1)

Msg 102, Level 15, State 1, Line 1
Incorrect syntax near ‘.’.

]]> By: R Chella Ganesh http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-33049 Thu, 17 Jan 2008 12:43:05 +0000 http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-33049 Hi Pinal,

When trying to delete 1 M records in a single stretch, Will try to write to the logfile for deletion of all 1 Million records., and then the actual deletion starts. if you try, deleting the records in smaller batch of say 500 records per time, May speed up the process.

This is my opinion. Please correct me if i am wrong.

Regards
Chella Ganesh
C/o Excel Soft Technologies P Ltd.
Mysore
India

]]> By: Jerry Hung http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-32931 Wed, 16 Jan 2008 18:46:05 +0000 http://blog.sqlauthority.com/2008/01/14/sql-server-time-out-due-to-executing-delete-on-large-recordset/#comment-32931 Also TRUNCATE is not so useful when you are deleting “conditionally”
e.g. delete 1M rows, in a table with 3M rows

In this case
- watch for index buildup (maybe drop-and-create index after delete)
- watch for log buildup (maybe switch to SIMPLE, then back to FULL recovery)
- do it in smaller batches

]]>