AWS prescriptive-guidance documentation change
Summary
Corrected typo in 'calculations' to 'calcuations', added bold formatting to table line numbers, updated image paths, and fixed apostrophe formatting
Security assessment
Changes involve typo corrections, formatting improvements, and image path updates. No security-related content was added or modified. The modifications focus on documentation clarity and maintenance rather than addressing security vulnerabilities or describing security features.
Diff
diff --git a/prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/data-files.md b/prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/data-files.md index 06a4b9dbc..71ee83cd4 100644 --- a//prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/data-files.md +++ b//prescriptive-guidance/latest/sql-server-optimization-for-enterpriseone/data-files.md @@ -7 +7 @@ -Complete file size calculationsCreate new filesTemporarily empty the MDF fileResize the MDF fileClean upValidate results +Complete file sizing calcuationsCreate new filesTemporarily empty the MDF fileResize the MDF fileClean upValidate results @@ -28 +28 @@ The SQL Server databases provided with EnterpriseOne can often benefit from addi -## Complete file size calculations +## Complete file sizing calcuations @@ -43,7 +43,7 @@ Line | Name | Example | Your value | Description -1 | Current size of the row | 1 TB | | The results from the previous query. -2 | Planned growth | 20% | | Expected growth over the next number of months, including a safety margin. -3 | Required size | 1.2 TB | | Line 1 multiplied by line 2. -4 | Number of files | 8 | | The number of files targeted. -5 | Size per file | 150 GB | | Line 3 divided by line 4. -6 | Autogrowth percentage | 10% | | The size for automatic growth. For minimum fragmentation, 10% is a good target. -7 | Autogrowth size | 15 GB | | Line 5 multiplied by line 6. +**1**| Current size of the row| 1 TB| | The results from the previous query. +**2**| Planned growth| 20%| | Expected growth over the next number of months, including a safety margin. +**3**| Required size| 1.2 TB| | Line 1 multiplied by line 2. +**4**| Number of files| 8| | The number of files targeted. +**5**| Size per file| 150 GB| | Line 3 divided by line 4. +**6**| Autogrowth percentage| 10%| | The size for automatic growth. For minimum fragmentation, 10% is a good target. +**7**| Autogrowth size| 15 GB| | Line 5 multiplied by line 6. @@ -97 +97 @@ When the files have been created, migrate the data from the MDF to the NDF files -The `EMPTYFILE` command generates an error because some content can’t be moved to an NDF file. You can ignore this error message. +The `EMPTYFILE `command generates an error because some content can't be moved to an NDF file. You can ignore this error message. @@ -99 +99 @@ The `EMPTYFILE` command generates an error because some content can’t be moved - + @@ -109 +109 @@ To reduce the size of the MDF file to the target size, run the following command -Occasionally, the `SHRINKFILE` command will fail because of the placement of content that couldn’t be moved to an NDF file. In this case, you might need to run the `DBCC DBREINDEX` command, rerun the process to empty the file, and try the `SHRINKFILE` operation again. +Occasionally, the `SHRINKFILE` command will fail because of the placement of content that couldn't be moved to an NDF file. In this case, you might need to run the `DBCC DBREINDEX` command, rerun the process to empty the file, and try the `SHRINKFILE` operation again. @@ -145 +145 @@ The output should be similar to the following. The files will seldom be perfectl - +