![]() This configuration needs custom monitoring and action to ensure the local ephemeral SSD (default D:\) drive is available all the time as any failures of this drive won't trigger action from FCI. If the FCI workload is heavily dependent on tempdb disk performance, then as an advanced configuration place tempdb on the local ephemeral SSD (default D:\) drive, which isn't part of FCI storage.For FCI place tempdb on the shared storage.For more information, see Data file caching policies. If the capacity of the local drive isn't enough for tempdb, consider sizing up the VM.Place tempdb on the temporary disk (the temporary disk is ephemeral, and defaults to D:\) for most SQL Server workloads that aren't part of a failover cluster instance (FCI) after choosing the optimal VM size.For M-series virtual machine deployments, consider write accelerator over using Azure ultra disks.If submillisecond storage latency is required, use either Premium SSD v2 or Azure ultra disks for the transaction log.For the log drive plan for capacity and test performance versus cost while evaluating either Premium SSD v2 or Premium SSD P30 - P80 disks.When using the Ebdsv5 VM series, use Premium SSD v2 which provides better price-performance for workloads that require high IOPS and I/O throughput. For the data drive, use premium P30 and P40 or smaller disks to ensure the availability of cache support.Place data, log, and tempdb files on separate drives.Azure Elastic SAN is currently in preview. Consider using Azure Elastic SAN for SQL Server workloads for better cost-efficiency due to storage consolidation, shared dynamic performance and the ability to drive higher storage throughput without needing to upgrade a VM.To optimize storage performance, plan for highest uncached IOPS available and use data caching as a performance feature for data reads while avoiding virtual machine and disks capping. ![]() The SQL IaaS Agent extension handles the folder and permissions needed upon re-provisioning. If available, configure the tempdb data and log files on the D: local SSD volume.Monitor the application and determine storage bandwidth and latency requirements for SQL Server data, log, and tempdb files before choosing the disk type.Review the following checklist for a brief overview of the storage best practices that the rest of the article covers in greater detail: To learn more, see the other articles in this series: Checklist, VM size, Security, HADR configuration, and Collect baseline. Consider your performance needs, costs, and workload patterns as you evaluate these recommendations. If your workload is less demanding, you might not require every recommended optimization. This performance best practices series is focused on getting the best performance for SQL Server on Azure VMs. There's typically a trade-off between optimizing for costs and optimizing for performance. This article provides storage best practices and guidelines to optimize performance for your SQL Server on Azure Virtual Machines (VM).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |