The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect these conditions where the appropriate value for partition starting offset is not configured. SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)ĭisk partition starting offset may be incorrect Product versions against which the rule is evaluated More Informationįor a detailed discussion on the various configuration values that you need to evaluate, please refer to the whitepaper : Disk Partition Alignment Best Practices for SQL Server. This whitepaper contains information on the default values for various Operating Systems where the partitions were created.įor more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table: For example, Partition_Starting_Offset modulo Stripe_Unit_Size should be zero. When you create a partition ensure that the starting offset is an exact multiple of the stripe unit size. This value works well with commonly used stripe unit sizes of 64 KB, 128 KB and 256 KB.
The default value used while creating partitions in Windows Server 2008 is 1,048,576 bytes. The default partition alignment value chosen depends on the Operating System where the partition was created. If the partition alignment is not configured properly, I/O requests could take more time to finish since they might be split into multiple requests. This is very important when these partitions form RAID volumes and the partition alignment is not appropriate for the stripe unit size. If this value is specified incorrectly at the time of creation of the partition, then the I/O performance could suffer. One of the important configuration parameter is the disk partition alignment or the starting offset of a partition on a disk. It is important to review these configuration parameters with the storage system vendor to make sure it is the appropriate setting for SQL Server I/O patterns. In some, these configuration values are left to the default.
In some instances these configuration parameters are tuned at each level to provide optimal performance for the entire storage solution. The performance of a storage system used by SQL Server is dependant on various configuration parameters that are applied at the partition, disk, controller, SAN, RAID and device driver levels.
Replace the ******* with the serial number of your CmStick. This path should now have taken over by the command line.Ĭmu32 -s******** -set-config-disk RemovableDisk