Updating documentation to remove references to Oracle and SQLServer (G…

…oogleCloudPlatform#919)

docs/cli/flags.md

@@ -45,7 +45,7 @@ such as `avro` etc.
 * **`password`**: Specifies the password for the source database.
 
 * **`streamingCfg`**: Optional flag. Specifies the file path for streaming config.
-Please note that streaming migration is only supported for MySQL, Oracle and PostgreSQL databases currently.
+Please note that streaming migration is only supported for MySQL and PostgreSQL databases currently.
 Here is an example of a [streamingCfg JSON](./config-json.md#streamingcfg-for-non-sharded-minimal-downtime-migrations) and [how to use it in the CLI](./schema-and-data.md#examples).
 
 ## Target Profile

docs/data-types/schema.md

@@ -9,6 +9,6 @@ permalink: /data-types-conv
 # Data type conversions using schema migrations
 {: .no_toc }
 
-SMT currently supports performing schema migrations for MySQL, PostgreSQL, SQLServer and Oracle. Certain features of relational databases, especially those that don't map directly to Spanner features, are ignored, e.g. stored functions and procedures, and sequences. Types such as integers, floats, char/text, bools, timestamps, and (some) array types, map fairly directly to Spanner, but many other types do not and instead are mapped to Spanner's `STRING(MAX)`.
+SMT currently supports performing schema migrations for MySQL and PostgreSQL. Certain features of relational databases, especially those that don't map directly to Spanner features, are ignored, e.g. stored functions and procedures, and sequences. Types such as integers, floats, char/text, bools, timestamps, and (some) array types, map fairly directly to Spanner, but many other types do not and instead are mapped to Spanner's `STRING(MAX)`.
 
 SMT supports converting to both GoogleSQL and PostgreSQL [dialects](https://cloud.google.com/spanner/docs) of Spanner.

docs/index.md

@@ -21,7 +21,7 @@ Spanner migration tool (SMT) is a stand-alone open source tool for Cloud Spanner
 We have changed architecture of the minimal downtime migration and added Pub/Sub notifications component. There are changes on required permissions to run the migrations because of the new component. Please go through [Permissions page](./permissions.md) and [design page](./minimal/minimal.md) of the documentation.
 
 Spanner migration tool is a stand-alone open source tool for Cloud Spanner evaluation and
-migration, using data from an existing PostgreSQL, MySQL, SQL Server, Oracle or DynamoDB database.
+migration, using data from an existing PostgreSQL or MySQL database.
 The tool ingests schema and data from either a pg_dump/mysqldump file or directly
 from the source database, and supports both schema and data migration.
 
@@ -54,8 +54,8 @@ To find out how to configure custom transformations, refer [here](./transformati
 
 ## Supported Sources and Targets
 
-- **Schema Migrations**: SMT supports schema migrations for MySQL, PostgreSQL, SQLServer and Oracle.
-- **Data Migrations**: SMT supports minimal downtime migrations for MySQL, PostgreSQL and Oracle, and POC migration for MySQL, PostgreSQL, SQLServer and Oracle.
+- **Schema Migrations**: SMT supports schema migrations for MySQL and PostgreSQL.
+- **Data Migrations**: SMT supports minimal downtime migrations and POC migration for MySQL and PostgreSQL databases.
 
 ## About the project
 

docs/limitations.md

@@ -22,7 +22,6 @@ Please refer to the [issues section](https://github.com/GoogleCloudPlatform/span
 
 ### Schema Conversion
 
-- Loading dump files from SQL Server, Oracle and DynamoDB is not supported
 - Schema Only Mode does not create foreign keys
 - Foreign key actions such as [ON DELETE CASCADE](https://cloud.google.com/spanner/docs/reference/standard-sql/data-definition-language#create_table) are not supported. If you do not specify a foreign key action, Spanner infers NO ACTION as the default action
 - Migration of check constraints, functions and views is not supported

docs/minimal/minimal.md

@@ -10,7 +10,7 @@ permalink: /minimal
 {: .no_toc }
 
 {: .note }
-Minimal downtime migrations are only supported for MySQL, Postgres and Oracle source databases.
+Minimal downtime migrations are only supported for MySQL and Postgres source databases.
 
 A minimal downtime migration consists of two components, migration of existing data from the database and the stream of changes (writes and updates) that are made to the source database during migration, referred to as change database capture (CDC). The process of migration involves Datastream reading data from the source database and writing to a GCS bucket, then GCS publishing a notification to Pub/Sub topic on each new file, then a Dataflow job when notified by the Pub/Sub subscription about the new file, reading the data from GCS bucket and writing to spanner database. With Spanner migration tool, this entire process can be orchestrated using a unified interface. Performing schema changes on the source database during the migration is not supported. This is the suggested mode of migration for most databases.
 

docs/minimal/postgres.md

@@ -64,7 +64,7 @@ Follow the steps below to configure a minimal downtime migration are PostgreSQL:
 
 1. [Connect to source database](../ui/connect-source.md).
 2. [Connect to spanner instance](../ui/connect-spanner.md).
-3. [Convert PostgreSQL schema to Spanner schema using the schema conversion workspace](../ui/schema-conv/schema-conv.md). Follow the documentation in the schema conversion workspace section of the documentation for different schema modifications that are supported by SMT. For guidance on specific data type conversion for Oracle, look at the [data conversion](../data-types/postgres.md) for Postgres documentation.
+3. [Convert PostgreSQL schema to Spanner schema using the schema conversion workspace](../ui/schema-conv/schema-conv.md). Follow the documentation in the schema conversion workspace section of the documentation for different schema modifications that are supported by SMT. For guidance on specific data type conversion for Postgres, look at the [data conversion](../data-types/postgres.md) documentation.
 4. [Configure datastream and dataflow details](../ui/prepare-migration/prepare.md).
 5. Wait for the migration to be orchestrated by SMT.
 6. Look at the list of [generated resources](../ui/prepare-migration/monitor.md/#generated-resources) for links to the Datastream stream and the Dataflow job crearted.

docs/permissions.md

@@ -81,7 +81,6 @@ before using SMT.
 
 - [MySQL](https://cloud.google.com/datastream/docs/configure-your-source-mysql-database)
 - [Postgres](https://cloud.google.com/datastream/docs/configure-your-source-postgresql-database)
-- [Oracle](https://cloud.google.com/datastream/docs/configure-your-source-oracle-database)
 
 ### Configuring connectivity for Dataflow