7/12/2023 0 Comments Toad sql server transaction logThe answer is that the log records will be created, just not immediately, by a mechanism called ‘deferred drop’, which was added in SQL Server 2000 SP3. So where are the log records for the operations? That small number doesn’t correlate with the size of the table being truncated or dropped, so it seems as if DROP and TRUNCATE operations are non-logged.īut they’re fully logged, as I demonstrated above. They will complete almost instantaneously, and if you look in the transaction log using fn_dblog right afterwards, you’ll only see a small number of log records generated from the operation. It comes from the behavior of DROP and TRUNCATE operations on large tables. So where does the misconception come from? Clearly the TRUNCATE operation must be logged otherwise the roll back operation would not work.
0 Comments
Leave a Reply. |