AWS AmazonRDS documentation change
Summary
Added comparison table of Oracle import methods with characteristics
Security assessment
Operational guidance about data migration methods without security implications or security feature documentation.
Diff
diff --git a/AmazonRDS/latest/UserGuide/Oracle.Procedural.Importing.md b/AmazonRDS/latest/UserGuide/Oracle.Procedural.Importing.md index ae6708865..a98b67a6c 100644 --- a//AmazonRDS/latest/UserGuide/Oracle.Procedural.Importing.md +++ b//AmazonRDS/latest/UserGuide/Oracle.Procedural.Importing.md @@ -34,0 +35,11 @@ Before you use the preceding migration techniques, we recommend that you back up +The following table compares the import methods available for RDS for Oracle DB instances. + +Choosing an import method for Oracle on Amazon RDS Method | Best for | Downtime impact | Complexity | Limitations +---|---|---|---|--- +Oracle SQL Developer | Simple schemas under 100 MB | High | Low | Not suitable for large or complex databases +Data Pump via Amazon S3 | 100 MB to 5 TB without a network link to the source | Medium | Medium | 5 TB maximum per dump file +Data Pump via database link | Any size with network connectivity to the source | Medium | Medium | Requires VPC or VPN connectivity to the source database +Transportable tablespaces | Multi-TB migrations requiring minimum downtime | Low | High | Enterprise Edition only +SQL*Loader | Flat file loads and ETL workflows | Varies | Medium | Manual DDL required; data must be in flat file format +Materialized views | Ongoing synchronization before cutover | Very low | Medium | Requires a database link to the source database +