Checks if the status of a database is suspect by looking for error 824. Error 824 indicates that a logical consistency error was detected during a read operation. This error frequently indicates data corruption caused by a faulty I/O subsystem component. This is a severe error condition that threatens database integrity and must be corrected immediately. When the SQL Server Database Engine reads a database page that contains an 824 error, the page is considered suspect and its page ID is recorded in the suspect_pages table. Best Practices Recommendations: * Review the SQL Server error log for the details of the 824 error for this database. * Complete a full database consistency check (DBCC CHECKDB). * Implement the user actions defined in MSSQLSERVER_824.
Checks if permission to access the database is enabled for guest user. Remove access to the guest user if it is not required. ...
Checks if the MSCS cluster has been validated and if there are any warnings reported in the MSCS cluster validation report. ...
Checks if the PAGE_VERIFY database option is not set to CHECKSUM to provide a high level of data-file integrity. When CHECKSUM ...
Checks if the selected instance name is already used by an existing cluster-prepared or clustered instance on any cluster ...
Checks if the status of a database is suspect by looking for error 824. Error 824 indicates that a logical consistency error ...
Checks that only members of the sysadmins fixed server role can execute CmdExec and ActiveX Script job steps. Applies only ...
Checks that symmetric keys with a length less than 128 bytes do not use the RC2 or RC4 encryption algorithm. The best practice ...
Checks that the AUTO_ CLOSE option is off for SQL Server Standard and Enterprise Editions. When set to on, this option can ...
Checks that the AUTO_SHRINK option is off for user databases on SQL Server Standard and Enterprise Editions. Frequently shrinking ...