THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » Best Practices » Storage   (RSS)
Showing page 2 of 2 (14 total posts)
  • Disk Partition Alignment in the Published TPC Benchmarks

    In SQL Server related storage literature, it is almost univerally recommended that disk partitions be aligned either on the 32K or the 64K boundary. On this subject, I posted some test results a while back, regarding the performance impact of disk partition misalignment: ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on July 19, 2007
  • Performance Impact of Using NTFS Compression with Read-Only Databases

    SQL Server 2005 supports placing read-only filegroups or read-only databases on NTFS compression. In other words, you can compress the database files in a read-only filegroup or a read-only database. This can be a very useful feature if saving disk storage is of high priority. But what are the performance implications of using this SQL Server ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on May 4, 2007
  • Should I Use a Windows Striped Volume?

    In Windows Server 2003, you can use the Disk Management console to create a striped volume over multiple dynamic disks (well, you can also create a mirrored, a RAID-5 volume, etc). If these disks (or LUNs) are presented from a SAN, most likely you can stripe across the same storage devices--making up these LUNs--inside the SAN to present ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on March 12, 2007
  • Performance Impact of Disk Misalignment

    Just google for Windows disk alignment best practice, and you would find thousands of articles, whitepapers, and posts, all preaching the practice of aligning disk partitions on the 64K boundary. For instance, one of the EMC recommendations prescribes a disk alignment value of 64K for the host file systems when deploying SQL Server 2005. Microsoft ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 1, 2007
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement