Checks whether data and log files are placed on separate logical drives. Placing both data and log files on the same drive ...

Checks whether data and log files are placed on separate logical drives. Placing both data and log files on the same drive can cause contention for that drive and result in poor performance. Placing the files on separate drives allows the I/O activity to occur at the same time for both the data and log files. The best practice is to specify separate drives for the data and log when you create a new database. To move files after the database is created, the database must be taken offline. Move the files by using one of the following methods:

* Restore the database from backup by using the RESTORE DATABASE statement with the WITH MOVE option. 
* Detach and then re-attach the database specifying separate locations for the data and log devices. 
* Specify a new location by running the ALTER DATABASE statement with the MODIFY FILE option, and then restarting the instance of SQL Server. 

Note:  This policy cannot detect separate physical devices through mount points.

Checks to see if the SQL Server edition upgrade path selected supports multi-subnet failover clusters. For more information ... Checks whether a database has recent backups. Scheduling regular backups is important for protecting your databases against ... Checks whether an instance of SQL Server 2012 is present on the machine, because uninstalling shared components (such as ... Checks whether Analysis Services is installed as part of a named instance that includes the SQL Server 2000 Database Engine. ... Checks whether data and log files are placed on separate logical drives. Placing both data and log files on the same drive ... Checks whether default trace is turned on to collect information about configuration and DDL changes to the instance of SQL ... Checks whether enforce password expiration on SQL Server logins is enabled. Enforce password expiration should be enabled ... Checks whether for the value specified for network packet size server option is set to the optimal value of 8060 bytes. If ... Checks whether hotfix KB937444 is installed. This is required for FILESTREAM to work on a Windows Server 2003-based cluster. ...