![]() See this guide Windows File Systems for FlashArray for more details But it is still worth checking to ensure it’s configured properly. Block Alignment - Partitions have been volume aligned by default since Windows 2008.Volume format - format all SQL Server volumes with 64KB NTFS Allocation Units.Lock pages in memory - Configure Local Security Policy to “Lock Pages In Memory” for the SQL Server Service account.Instant file initialization - Configure Local Security Policy to “Perform Volume Management” for the SQL Server Service account.Windows Updates - before installation of SQL Server, ensure all updates are applied.Page file size - configure as a fixed 8GB allocation.When using snapshots with database files across multiple volumes, ensure that you’re using Protection Groups to perform the snapshot for a consistent snapshot across all volumes. When designing your database file layout to volumes, consider if you’re going to use snapshots, isolating database files onto volumes that are snapshot and then presented to other Instances of SQL Server. Granularity of snapshots and recovery - FlashArray provides snapshot capabilities that enable nearly instantaneous data copying between volumes. So all that space that you used to keep as headroom on each volume doesn’t consume space on the array. You can worry less about empty space management - Since FlashArray is data reducing, you can worry less about how much free space is available in each volume and if you’re wasting that space. So the more volumes, the more reader threads, which can lead to higher backup throughput. SQL Server allocates a reader thread per volume the database files are on. Second is backup and restore performance.First is recovery separating data and log files gives you the ability to perform tail of the log backup in the event of a disaster.There are other SQL Server-specific reasons you will want to separate data and log files onto separate volumes. So literally, you could put all your databases and files on a single volume and the system will perform well without conflicting with each other. You don’t have to have dedicated volumes or RAID groups based on performance profile - Each one of your volumes will get the full performance of the array. Validate Windows Server with the Test-WindowsBestPractices cmdlet - PowerShell cmdlet that tests for Windows best practices configurationįlashArray is a data-reducing array, which can have some interesting implications on how you layout your volumes.iSCSI Best Practices for Windows Server and FlashArray - iSCSI best practice recommendations for Windows Server and the Pure Storage FlashArray.SAN Guidelines to Maximize Pure Storage Performance - guidelines to achieve the best possible performance.Configuring Multipath-IO for Windows Server - instructions for configuring MPIO timers.MPIO Installing and Configuration - installing and configuring MPIO and attaching disks.This guide tells you important information based on your connectivity method. ![]() Disable all processor C-states (C1E halt state)ĭisk Configuration Connecting a Physical Server to your FlashArrayįor general best practices for connecting Windows hosts with Pure Storage, please see the Pure Storage Support page’s Microsoft Platform Guide.Power Management set to OS Controlled or High Performance.Here are my thoughts on general guidance around CPU configuration and power management. Physical Host ConfigurationĬheck with your hardware vendor to see if they publish a guide for SQL Server-specific configurations for their server platforms. ![]() The target audience for this blog post is for SQL Server DBAs introducing them to the most impactful configurations and settings for running SQL Server on physical machines on Pure Storage. The intent of this post is a quick reference guide based on the recommendations made on Pure Storage Support page in the Microsoft Platform Guide. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |