AWS prescriptive-guidance documentation change
Summary
Updated navigation links, corrected grammar/punctuation (curly quotes to straight quotes), standardized terminology for Aurora PostgreSQL, updated image reference path, and added specificity to section headers by including 'for SQL Server'.
Security assessment
Changes are primarily cosmetic, grammatical, and navigational. No security vulnerabilities, configurations, or best practices are mentioned. Updates include punctuation corrections, branding consistency ('AWS cloud-native'), and image path changes without security implications.
Diff
diff --git a/prescriptive-guidance/latest/migration-sql-server/heterogeneous-migration-tools.md b/prescriptive-guidance/latest/migration-sql-server/heterogeneous-migration-tools.md index 7d996b98f..fd8f9ce19 100644 --- a//prescriptive-guidance/latest/migration-sql-server/heterogeneous-migration-tools.md +++ b//prescriptive-guidance/latest/migration-sql-server/heterogeneous-migration-tools.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating Microsoft SQL Server databases to the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating Microsoft SQL Server databases to the AWS Cloud](introduction.html) @@ -13 +13 @@ The following chart provides a list of tools that you can use to migrate from SQ -Migration tool | Target database support | Used for +**Migration tool**| **Target database support**| **Used for** @@ -23 +23 @@ The following subsections provide more information about each tool. -[AWS Schema Conversion Tool (AWS SCT)](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Welcome.html) converts your existing commercial database schemas to an open-source engine or to an AWS Cloud-native database. AWS SCT makes heterogeneous database migrations predictable by automatically converting the source database schema and a majority of the database code objects, including views, stored procedures, and functions, to a format that’s compatible with the target database. +[AWS Schema Conversion Tool (AWS SCT)](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Welcome.html) converts your existing commercial database schemas to an open-source engine or to an AWS cloud-native database. AWS SCT makes heterogeneous database migrations predictable by automatically converting the source database schema and a majority of the database code objects, including views, stored procedures, and functions, to a format that's compatible with the target database. @@ -25 +25 @@ The following subsections provide more information about each tool. -When you convert your database schema from one engine to another, you also need to update the SQL code in your applications to interact with the new database engine instead of the old one. AWS SCT also converts the SQL code in C++, C#, Java or other application code. Any objects that can’t be automatically converted are clearly marked for manual conversion. AWS SCT can also scan your application source code for embedded SQL statements and convert them as part of a database schema conversion project. For more information, see [Using Microsoft SQL Server as a source for AWS SCT](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.SQLServer.html) in the AWS documentation. +When you convert your database schema from one engine to another, you also need to update the SQL code in your applications to interact with the new database engine instead of the old one. AWS SCT also converts the SQL code in C++, C#, Java or other application code. Any objects that can't be automatically converted are clearly marked for manual conversion. AWS SCT can also scan your application source code for embedded SQL statements and convert them as part of a database schema conversion project. For more information, see [Using Microsoft SQL Server as a source for AWS SCT](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.SQLServer.html) in the AWS documentation. @@ -33 +33 @@ When you convert your database schema from one engine to another, you also need -Babelfish is a built-in capability of Amazon Aurora. Babelfish for Aurora PostgreSQL enables your Aurora PostgreSQL-Compatible Edition databases to understand commands from applications that were written for Microsoft SQL Server. Modifying SQL Server applications that have SQL Server database code written in Transact-SQL (T-SQL), SQL Server’s proprietary SQL dialect, takes effort and is time-consuming. [Babelfish for Aurora PostgreSQL](https://aws.amazon.com/rds/aurora/babelfish/) makes this process simpler and easier. Using Babelfish, you do not have to make changes to your application code. Instead, you can use Babelfish for Aurora PostgreSQL to migrate an SQL Server database to an Aurora PostgreSQL-Compatible DB cluster. +Babelfish is a built-in capability of Amazon Aurora. Babelfish for Aurora PostgreSQL enables your Aurora PostgreSQL-Compatible Edition databases to understand commands from applications that were written for Microsoft SQL Server. Modifying SQL Server applications that have SQL Server database code written in Transact-SQL (T-SQL), SQL Server's proprietary SQL dialect, takes effort and is time-consuming. [Babelfish for Aurora PostgreSQL](https://aws.amazon.com/rds/aurora/babelfish/) makes this process simpler and easier. Using Babelfish, you do not have to make changes to your application code. Instead, you can use Babelfish for Aurora PostgreSQL to migrate a SQL Server database to an Aurora PostgreSQL DB cluster. @@ -35 +35 @@ Babelfish is a built-in capability of Amazon Aurora. Babelfish for Aurora Postgr -With Babelfish, Aurora PostgreSQL understands T-SQL and supports the same communications protocol, so you don't have to switch database drivers or rewrite your application queries. Your applications that were originally written for SQL Server can now work with Aurora with fewer code changes. This reduces the effort required to modify and move applications running on SQL Server or newer to Aurora, leading to faster, lower-risk, and more cost-effective migrations. +With Babelfish, Aurora PostgreSQL-Compatible understands T-SQL and supports the same communications protocol, so you don't have to switch database drivers or rewrite your application queries. Your applications that were originally written for SQL Server can now work with Aurora with fewer code changes. This reduces the effort required to modify and move applications running on SQL Server or newer to Aurora, leading to faster, lower-risk, and more cost-effective migrations. @@ -37 +37 @@ With Babelfish, Aurora PostgreSQL understands T-SQL and supports the same commun -If you’re migrating from legacy SQL Server databases, you can use Babelfish to run SQL Server code side by side with new functionality you built by using native PostgreSQL APIs. Babelfish enables Aurora PostgreSQL to work with commonly used SQL Server tools, commands, and drivers. +If you're migrating from legacy SQL Server databases, you can use Babelfish to run SQL Server code side by side with new functionality you built by using native PostgreSQL APIs. Babelfish enables Aurora PostgreSQL-Compatible to work with commonly used SQL Server tools, commands, and drivers. @@ -50 +50 @@ Babelfish enables your legacy SQL Server applications to communicate with Aurora - + @@ -79 +79 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Heterogeneous database migration +Heterogeneous database migration for SQL Server @@ -81 +81 @@ Heterogeneous database migration -Hybrid migration scenarios +Hybrid migration scenarios for SQL Server