Home > Storage > PowerStore > Databases and Data Analytics > Dell PowerStore: Microsoft SQL Server Best Practices > Volume groups
Block volumes can be combined into a volume group. A volume group identifies volumes that should be treated as a set. This is important for applications such as SQL Server where a single database is comprised of multiple files which are commonly stored on multiple volumes. When a database spans multiple block volumes, Dell Technologies recommends placing all block volumes for a SQL Server database into a volume group.
Depending on the use case, volumes for multiple databases might be combined into a single volume group as well. For example, a SQL Server application that consists of multiple interdependent databases that need to be consistent. A single volume group of interdependent databases could contain system databases as well.
Understanding volume group features will help you understand the best way to organize SQL Server database volume into volume groups.
SQL Server volume groups should always use the write-order consistency option. This ensures that writes across multiple volume are applied in a consistent order. This will assist SQL Server crash recovery in the event of a failure by ensuring that database and transaction log entries are maintained in order.
Volume groups can identify all SQL Server database related volumes so they can be provisioned as a set. This makes it easier for administrators who may not be familiar with the SQL Server architecture to ensure all related volumes are provisioned together.
When volume groups are created for SQL Server volumes, policy-based management features such as QoS, snapshots, replication, remote snapshots, and Metro Volume should all be applied at the volume group level. This ensures that the policy is being applied to the entire database and related volumes. All files and volumes for a single SQL Server database need to be protected and managed consistently.
Note: Applying performance or protection policies to an individual database volume of a multi-volume database should be avoided.
Volume statistics assist in troubleshooting individual volume issues. However, from a SQL Server perspective the overall database performance is typically the first concern. Volume groups are an excellent way to see performance statistics for an entire database. Volume groups also provide another perspective in addition to the volume and the host level statistics.