AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation link from 'welcome.html' to 'introduction.html', escaped hyphens in bullet points for markdown consistency, and clarified section heading 'Compare features' to 'Compare SQL Server Enterprise and Standard edition features'.
Security assessment
Changes are purely navigational, formatting, and descriptive improvements. No security vulnerabilities, features, or configurations are mentioned. Content remains focused on edition downgrade best practices without security implications.
Diff
diff --git a/prescriptive-guidance/latest/evaluate-downgrading-sql-server-edition/best-practices.md b/prescriptive-guidance/latest/evaluate-downgrading-sql-server-edition/best-practices.md index b02f49257..f84663743 100644 --- a//prescriptive-guidance/latest/evaluate-downgrading-sql-server-edition/best-practices.md +++ b//prescriptive-guidance/latest/evaluate-downgrading-sql-server-edition/best-practices.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Evaluate downgrading Microsoft SQL Server from Enterprise edition to Standard edition on AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Evaluate downgrading Microsoft SQL Server from Enterprise edition to Standard edition on AWS](introduction.html) @@ -15 +15 @@ The following best practices are recommended for assessing and downgrading your - * **Validate vendor support for SQL Server Standard edition** – Ensure that your application is certified to run on SQL Server Standard edition. Check directly with the software vendor or their documentation. Downgrading to Standard edition without vendor confirmation might invalidate support for the application. + * **Validate vendor support for SQL Server Standard edition** \- Ensure that your application is certified to run on SQL Server Standard edition. Check directly with the software vendor or their documentation. Downgrading to Standard edition without vendor confirmation might invalidate support for the application. @@ -17 +17 @@ The following best practices are recommended for assessing and downgrading your - * **Identify the use of Enterprise edition features for administration activities** – Database administrators or application administrators sometimes rely on Enterprise edition features to improve operational processes. Some examples are online maintenance activities (such as online index create and rebuild). Identify usage of such features and make an informed decision. You can modify your operations or apply workarounds where possible to mitigate the loss of Enterprise edition features. + * **Identify the use of Enterprise edition features for administration activities** \- Database administrators or application administrators sometimes rely on Enterprise edition features to improve operational processes. Some examples are online maintenance activities (such as online index create and rebuild). Identify usage of such features and make an informed decision. You can modify your operations or apply workarounds where possible to mitigate the loss of Enterprise edition features. @@ -19 +19 @@ The following best practices are recommended for assessing and downgrading your - * **Assess workload patterns of SQL Server Enterprise edition** – SQL Server Standard edition automatically restricts usage to a maximum of 24 CPU cores or 4 sockets at any time. For a list of instance types that are available for SQL Server Standard edition, see the [Amazon RDS for SQL Server documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_SQLServer.html#SQLServer.Concepts.General.InstanceClasses). Analyze your database workload pattern to determine whether the maximum limit of 24 CPU cores will negatively impact service levels when you downgrade to Standard edition. + * **Assess workload patterns of SQL Server Enterprise edition** \- SQL Server Standard edition automatically restricts usage to a maximum of 24 CPU cores or 4 sockets at any time. For a list of instance types that are available for SQL Server Standard edition, see the [Amazon RDS for SQL Server documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_SQLServer.html#SQLServer.Concepts.General.InstanceClasses). Analyze your database workload pattern to determine whether the maximum limit of 24 CPU cores will negatively impact service levels when you downgrade to Standard edition. @@ -21 +21 @@ The following best practices are recommended for assessing and downgrading your - * **Test your workload against SQL Server Standard edition** – Run multiple tests using representative workload to determine whether the 24-core limit imposed by Standard edition will have a negative impact on your workload. Monitor results and tune the database as required. + * **Test your workload against SQL Server Standard edition** \- Run multiple tests using representative workload to determine whether the 24-core limit imposed by Standard edition will have a negative impact on your workload. Monitor results and tune the database as required. @@ -23 +23 @@ The following best practices are recommended for assessing and downgrading your - * **Test database administration activities** – Monitoring, performance assessments, tuning, and maintenance tasks to build comfort levels around new ways of working in the Standard edition environment. + * **Test database administration activities** \- Monitoring, performance assessments, tuning, and maintenance tasks to build comfort levels around new ways of working in the Standard edition environment. @@ -25 +25 @@ The following best practices are recommended for assessing and downgrading your - * **Test the migration process** – Run comprehensive migration tests to build operator confidence, fine-tune the approach, and document every issue with resolution. + * **Test the migration process** \- Run comprehensive migration tests to build operator confidence, fine-tune the approach, and document every issue with resolution. @@ -40 +40 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Compare features +Compare SQL Server Enterprise and Standard edition features