AWS dms documentation change
Summary
Added documentation for converting unsupported built-in objects to stub objects, including schema isolation options and re-conversion behavior
Security assessment
The addition documents a migration workflow feature for handling unsupported objects, but does not explicitly address security vulnerabilities or describe security controls. While schema isolation could have security implications, the documentation focuses on functional behavior rather than security guidance.
Diff
diff --git a/dms/latest/userguide/schema-conversion-sql-server-postgresql.md b/dms/latest/userguide/schema-conversion-sql-server-postgresql.md index aecd94fea..8d4c3a7e6 100644 --- a//dms/latest/userguide/schema-conversion-sql-server-postgresql.md +++ b//dms/latest/userguide/schema-conversion-sql-server-postgresql.md @@ -25 +25 @@ SQL Server to PostgreSQL conversion settings in DMS Schema Conversion include th - * You can keep the letter case of your source object names. To avoid conversion of object names to lowercase, select **Keep object names in the same case**. This option applies only when you turn on the case sensitivity option in your target database. + * You can keep the letter case in the names of source operands. To avoid conversion of operand names to lowercase, select **Avoid casting to lowercase for case-sensitive operations**. This option is applicable only if the case-sensitivity feature is enabled in the source database. @@ -33,0 +34,12 @@ SQL Server to PostgreSQL conversion settings in DMS Schema Conversion include th +To convert unsupported built-in objects to stub objects, enable the **Convert unsupported built-in objects to stub objects** setting. When enabled, DMS SC replaces unsupported built-in objects with corresponding stub objects in the target database. This feature converts code sections that would normally be enclosed by migration issue 7811 or 7904. It creates stub objects based on the type of the source built-in objects `PROCEDURE` for procedures, `VIEW` for views or tables. + +Conversion of a source database object with a call of an unsupported object results in a call of a stub object and migration issue 7822. + +You can choose to create stub objects in a separate schema by enabling the **Create stub objects in a separate schema** option. When selected, stub objects are created in a special schema named `aws_sqlserver_stub` in the target database. If not selected, they are created in the same schema as the calling objects. + +Stub routines are named based on the fully qualified name of the original built-in. For stub views, the naming convention includes the system schema name `system_schema_name$builtin_view_name`. + +During re-conversion, DMS SC checks for existing stub routines in the target database. If a routine with the same name and input parameters already exists, it is not overwritten. + +After conversion, review and implement custom code for stub routines as needed. +