SQLIOSim is NOT designed to be a performance testing utility as it combines known I/O patterns with random patterns in an effort to test the data integrity capabilities of your I/O path. As an example, some of the testing phases perform unbounded I/O as we have encountered some drivers that will cause blue screens when the I/O depth becomes aggressive.
We recommend you execute SQLIOSim on all I/O paths before you install the actual SQL Server components or anytime you encounter data integrity issues.
SQLIOSim can be downloaded from the web (
) and is also installed with the SQL Server 2008 components in the MSSQL\BINN location. There are builds available for x86, x64 and ia64 platforms.
GUI version of utility
Command line version of utility
Contains testing configuration files.
Recommended for common testing.
Good for testing behaviors of the hardware cache.
Tests pushing the system and drivers at high queue levels.
Used to simulate load based activities such as BCP and restore.
Tests sparse file behaviors that are used by DBCC and snapshot databases.
Style sheet used to display the sqliosim.log.xml. Created in the specified output directory.
Log file generated by the utility. Multiple executions append to the log file.
Never use the same file names as a SQL Server database file. SQLIOSim generates random data using the Crypro random data generators. It does not understand the SQL Server I/O format and would damage a database file in an unrecoverable fashion.
For most systems, including those with suspected I/O problems such as checksum failures, edit the
in your favorite text editor. Update or add files that exercise the same I/O path as the SQL Server database files.
Be sure to increase the size of the files so that any hardware cache performs physical I/O during the tests. Using files that are smaller than the hardware cache does not exercise the I/O path fully.
You typically have to run the utility with elevated administrator privileges.
We recommend at least 10 test cycles at 300 seconds per cycle using the default.cfg.ini for a basic test.
Success or Failure
The log file contains various details about each test pass executed. We recommend you enable stop on error. If SQLIOSim encounters an error that would lead to possible data integrity issues details are logged and the testing is halted.