City of Peoria Press Release
Printer Friendly Version
This is a description of the issue we discussed with Polaris on May 13, 2009 at 9:30 a.m. Configuring the Production database server as Polaris would like deviates from our standard.
Our standard is to put the System (C:\) on one array, the Applications (D:\) on one array and the SQL database (F:\) on one array.
Polaris believes we will take a performance hit unless we separate the SQL TempDB into it’s own array. They use the Temp DB heavily to process transacations and is by design setup as they believe Microsoft recommends.
Microsoft does recommend separating TempDB on separate physical drives for performance sake but their recommendation further states that performance gains are greatest when the physical drives are on their own array controller, or separate array controller channel. Leading industry tuning experts such as Kimberly Tripp at www.sqlskills.com and http://www.sqlskills.com/BLOGS/KIMBERLY/post/Understanding-TempDB-table-variables-v-temp-tables-and-Improving-throughput-for-TempDB.aspx and Microsoft Software Architect Gert Drapers at http://blogs.msdn.com/gertd/default.aspx also recommend separate drive controllers or array controller channels. The language most often used when describing this is “separate IO subsystem.” In Microsoft language, these experts and Microsoft themselves describe this as physical controllers and disk drives.