Home > Workload Solutions > SQL Server > Guides > Implementation Guide—SQL Server 2019 Best Practices on PowerStore > Datastore configuration
The PowerStore has the volume group feature, which enables the administrator to create a configuration that facilitates ease of management, efficient snapshots, and replication. For the baseline storage configuration, all six virtualized databases used the same design. Table 8 shows the configuration detail for the first virtualized SQL Server database.
Volume Group | Volume Name | Number of LUNs | VMware Datastore | Volume size (GB) | Notes |
sql_vm1_os | sql-vm1-os | 1 | sql-vm1-os-ds | 300 | Operating System |
sql_vm1_db1 | sql-vm1-db1-data1 | 1 | sql-vm1-db1-data1-ds | 512 | Data |
sql-vm1-db1-log1 | 1 | sql-vm1-db1-log1-ds | 256 | Log | |
sql_vm1_db1_temp | sql-vm1-db1-temp-data1 | 1 | sql-vm1-db1-temp-data1-ds | 256 | TempData |
sql-vm1-db1-temp-log1 | 1 | sql-vm1-db1-temp-log1-ds | 128 | TempLog | |
sql_vm1_db1_backup | sql-vm1-db1-backup1 | 1 | sql-vm1-backup1-ds | 1000 | Backup |
A naming convention using VMn and DBn allowed the database administrators to increment the value to create volume groups for all the databases. For example, the second copy of the database had a volume group name of SQL_VM2_DB2. Using this naming convention allowed the administration team to repurpose copies to the database quickly. Note that each LUN was configured as a VMware datastore.
For detailed PowerStore best practices and features, see Dell PowerStore: Microsoft SQL Server Best Practices.
Use the following steps to install Red Hat Enterprise Linux: