DB Properties - 2

 Blocked process threshold option to specify the threshold, in seconds, at which blocked process reports are generated. The threshold can be set from 5 to 86,400. The lock monitor only wakes up every 5 seconds to detect blocking conditions (it is also looking for other conditions such as deadlocks). Therefore, if you set a 'blocked process threshold' value to 1, it will not detect a process that has been blocking for 1 second. The minimum time it can detect a blocked process is 5 seconds. 

By default, no blocked process reports are produced. This event is not generated for system tasks or for tasks that are waiting on resources that do not generate detectable deadlocks. 

You can define an alert to be executed when this event is generated. So for example, you can choose to page the administrator to take appropriate action to handle the blocking situation. 

Blocked process threshold uses the deadlock monitor background thread to walk through the list of tasks waiting for a time greater than or multiples of the configured threshold. The event is generated once per reporting interval for each of the blocked tasks. 

The setting takes effect immediately without a server stop and restart. 

 

 

The remote login timeout option specifies the number of seconds to wait before returning from a failed attempt to log in to a remote server. For example, if you are trying to log in to a remote server and that server is down, remote login timeout helps make sure that you do not have to wait indefinitely before your computer stops trying to log in. The default value for this option is 10 seconds. A value of 0 allows for an infinite wait. 

 

 

Set the page_verify database option to checksum 

This rule checks whether PAGE_VERIFY database option is set to CHECKSUM. When CHECKSUM is enabled for the PAGE_VERIFY database option, the SQL Server Database Engine calculates a checksum over the contents of the whole page, and stores the value in the page header when a page is written to disk. When the page is read from disk, the checksum is recomputed and compared to the checksum value that is stored in the page header. This helps provide a high level of data-file integrity. If you use the PAGE VERIFY CHECKSUM option for a database, when SQL Server detects a page has been altered after it has been written to disk, SQL Server reports MSSQLSERVER_824 after reading the page back from disk. 

 

A full backup does the following: 

Force a database checkpoint and make a note of the log sequence number at this point. This flushes all updated-in-memory pages to disk before anything is read by the backup to help minimize the amount of work the recovery part of restore has to do.