|
|||||
|
As a dba, its important to know that the databases being monitored under our supervision are free from corruption and the below code helps in identifying the last ran clean DBCC CHECKDB date. This technique works only for SQL Server 2005 and above. USE tempdb Update: This post is participating in the 4th installment of the T-SQL Tuesday hosted this time by Mike Walsh. One of the side affects of having Heaps in a system is the possibility of generating forwarded records. When reading data from a heap, Forwarded records (if they are present in a heap) can generate extra, random and . . . → Read More: How can I tell if a SQL Server system is affected by Forwarded records? Update: This post is participating in the 4th installment of the T-SQL Tuesday hosted this time by Mike Walsh .SQL Server 2005 came few years ago with lots of optimizations and in this post I will add some details on one of the lesser known IO enhancement that wasn’t present in previous versions. CHECKSUM was introduced as a PAGE_VERIFY option . . . → Read More: Transaction Log (block) CHECKSUM From SQL Server 2005 onwards, CHECKSUM is available as a PAGE_VERIFY option at the database level. All databases created in SQL Server 2005 & above will have CHECKSUM enabled by default. Even tempdb in SQL Server 2008 has this option enabled. It is recommended by MSFT to change the PAGE_VERIFY option of databases to CHECKSUM when migrating from . . . → Read More: Performance impact of using BACKUP CHECKSUM in SQL Server 2005/2008 |
|||||
|
Copyright © 2010 Sankar Reddy, SQL Server Developer/DBA - All Rights Reserved      |
|||||
Popular posts