AWS prescriptive-guidance documentation change
Summary
Minor formatting and punctuation fixes: corrected apostrophes, adjusted markdown syntax for links, and removed backticks from non-code terms like 'gp3' and 'tempdb'.
Security assessment
Changes involve typo corrections and markdown formatting adjustments. No security vulnerabilities, configurations, or features are mentioned or modified. Storage recommendations remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/storage.md b/prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/storage.md index 9ca290afe..ef503d7af 100644 --- a//prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/storage.md +++ b//prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/storage.md @@ -13 +13 @@ When you use SQL Server database files with EnterpriseOne, they exhibit characte - * MDF and NDF data files should be placed on one or more [General Purpose SSD (`gp3`) volumes](https://aws.amazon.com/ebs/general-purpose/). These files tend to be read IOPS heavy but aren’t very latency sensitive when they’re used with a large buffer cache. You can use multiple MDF and NDF file for each database to stripe your database across multiple disks to achieve the desired performance level. + * MDF and NDF data files should be placed on one or more [General Purpose SSD (gp3) volumes](https://aws.amazon.com/ebs/general-purpose/). These files tend to be read IOPS heavy but aren't very latency sensitive when they're used with a large buffer cache. You can use multiple MDF and NDF file for each database to stripe your database across multiple disks to achieve the desired performance level. @@ -15 +15 @@ When you use SQL Server database files with EnterpriseOne, they exhibit characte - * LDF files should be placed on a single `gp3`, or [Provisioned IOPS SSD](https://aws.amazon.com/ebs/provisioned-iops/) `io2` or `io2` Block Express volume based on requirements. Many JD Edwards processes perform operations that create chatty write I/O, which is latency sensitive. For many users, `gp3` latency is sufficient to meet requirements. However, if you have a runtime-sensitive process, `io2` or `io2` Block Express might be required to meet your performance requirements for the workload. You might also consider enabling delayed durability in the SQL Server database to mitigate the performance impact of chatty write I/O. When delayed durability is enabled, you can use `gp3` storage without being concerned about write I/O latency. + * LDF files should be placed on a single `gp3`, or****[ Provisioned IOPS SSD](https://aws.amazon.com/ebs/provisioned-iops/)****`io2` or `io2` Block Express volume based on requirements. Many JD Edwards processes perform operations that create chatty write I/O, which is latency sensitive. For many users, `gp3` latency is sufficient to meet requirements. However, if you have a runtime-sensitive process, `io2` or `io2` Block Express might be required to meet your performance requirements for the workload. You might also consider enabling delayed durability in the SQL Server database to mitigate the performance impact of chatty write I/O. When delayed durability is enabled, you can use gp3 storage without being concerned about write I/O latency. @@ -17 +17 @@ When you use SQL Server database files with EnterpriseOne, they exhibit characte - * Backup files should be placed on high-throughput, low-cost storage such as [Throughput Optimized HDD](https://aws.amazon.com/ebs/throughput-optimized/) (`st1`) or in an [Amazon Simple Storage Service (Amazon S3)](https://aws.amazon.com/s3/) bucket. Additionally, because EnterpriseOne data tends to be repetitive and sparse, we recommend that you use SQL Server backup compression for backups you make through the database. + * Backup files should be placed on high-throughput, low-cost storage such as [Throughput Optimized HDD](https://aws.amazon.com/ebs/throughput-optimized/) (`st1`) or in an****[ Amazon Simple Storage Service (Amazon S3](https://aws.amazon.com/s3/)) bucket. Additionally, because EnterpriseOne data tends to be repetitive and sparse, we recommend that you use SQL Server backup compression for backups you make through the database. @@ -19 +19 @@ When you use SQL Server database files with EnterpriseOne, they exhibit characte - * Buffer pool extensions (BPEs) can provide value when you use an instance with substantial NVMe instance storage. However, when you use X2iedn instances, the benefit of BPE is substantially mitigated by the large amount of available memory, and it’s better to use the available NVMe storage for `tempdb`. + * Buffer pool extensions (BPEs) can provide value when you use an instance with substantial NVMe instance storage. However, when you use X2iedn instances, the benefit of BPE is substantially mitigated by the large amount of available memory, and it's better to use the available NVMe storage for tempdb.