AWS prescriptive-guidance documentation change
Summary
Updated quotation marks from curly to straight quotes in two places
Security assessment
Changes are typographical corrections without security implications
Diff
diff --git a/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/consolidate-instances.md b/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/consolidate-instances.md index 8b31b7a17..5ba190868 100644 --- a//prescriptive-guidance/latest/optimize-costs-microsoft-workloads/consolidate-instances.md +++ b//prescriptive-guidance/latest/optimize-costs-microsoft-workloads/consolidate-instances.md @@ -15 +15 @@ Creating an instance is part of the process for installing the SQL Server Databa -It's typical to use only a single SQL Server instance per server in production environments so that a “busy” instance doesn't overuse the shared hardware resources. Giving each SQL Server instance its own operating system, with its own resources, is a better boundary than relying on resource governance. This is especially true for high performance SQL Server workloads that require large amounts of RAM and CPU resources. +It's typical to use only a single SQL Server instance per server in production environments so that a "busy" instance doesn't overuse the shared hardware resources. Giving each SQL Server instance its own operating system, with its own resources, is a better boundary than relying on resource governance. This is especially true for high performance SQL Server workloads that require large amounts of RAM and CPU resources. @@ -70 +70 @@ If you wish to move forward with a plan to combine SQL Server instances, see the - * Each additional instance installed on the same server is a “named” database instance. + * Each additional instance installed on the same server is a "named" database instance.