|
|
Posted by Erland Sommarskog on 06/14/05 01:12
joshsackett (joshsackett@gmail.com) writes:
> My problem is that all throughout the day I have constant blocks by the
> WRITELOG waittype. I know my disk I/O is very slow (will be upgraded
> soon) but this is the only database on which these blocks occur. What
> is writing to the transaction log if I have the DB set for SIMPLE
> recovery?
Simple recovery is not the same as no recovery. SQL Server always
writes to the transaction. It first write to the transaction log,
and later to the data tables. The point is that if the server
crashes before the data is written to the table, the transaction
can be rolled forward, if commit record was written. Else the
transaction will be rolled back.
The difference to full and bulk-logged recovery, is that in simple
recovery, SQL Server will automatically truncate the transaction
log every now and then. But truncation is never past the point of
the oldest open transaction.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|