AWS Schema Conversion Tool. User Guide Version 1.0

Transcription

1 AWS Schema Conversion Tool User Guide

2 AWS Schema Conversion Tool: User Guide Copyright 2016 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon.

3 Table of Contents What Is the AWS Schema Conversion Tool?... 1 Converting Your Schema... 2 AWS Schema Conversion Tool Project Window... 3 Related Topics... 4 Installing and Updating... 5 Installing the AWS Schema Conversion Tool on Windows... 6 Installing the AWS Schema Conversion Tool on Mac OS X... 6 Installing the AWS Schema Conversion Tool on Ubuntu Linux... 6 Installing the AWS Schema Conversion Tool on Fedora Linux... 7 Updating the AWS Schema Conversion Tool... 7 Required Database Drivers... 7 Installing JDBC Drivers on Linux... 7 Updating Global Settings... 8 Related Topics... 9 Getting Started Before You Begin Step 1: Create an AWS Schema Conversion Tool Project Step 2: View the Schema from Your Source Database Step 3: Create the Schema Step 4: Clear the Schema Step 5: Update Your Source Schema Step 6: Overwrite the Schema Step 7: Create the Database Migration Assessment Report Step 8: Apply the Schema to the DB Instance Related Topics Converting Schema Create a Project Microsoft SQL Server as the Source MySQL as the Source Oracle as the Source PostgreSQL as the Source Related Topics Creating and Using the Assessment Report Creating a Database Migration Assessment Report Related Topics Converting Your Schema Editing Schema Clearing a Schema Related Topics Updating and Refreshing Your Schema Related Topics Saving and Applying Your Schema Saving Your Schema to a File Applying Your Schema Related Topics Related Topics Best Practices Memory Management and Performance Related Topics Reference Related Topics Oracle to MySQL Supported Schema Conversion Statements Procedures Flow Control iii

4 Packages Functions Operators Data Types Data Definition Language (DDL) Cursors Hints Exceptions Related Topics Microsoft SQL Server to PostgreSQL Supported Schema Conversion Data Definition Language (DDL) Data Manipulation Language (DML) Data Types Database Mail Functions Operators Other Service Broker SQL Server Agent SQL Server Backup T-SQL Microsoft SQL Server to PostgreSQL Conversion Issue Reference SQL Server to MySQL Supported Schema Conversion Statements Procedures Flow Control Functions Operators Transactions Data Types Data Definition Language (DDL) Cursors Related Topics Keyboard Shortcuts Related Topics Troubleshooting Cannot load objects from an Oracle source database Related Topics Document History iv

5 What Is the AWS Schema Conversion Tool? The AWS Schema Conversion Tool helps you convert your existing database schema to a schema suitable for an Amazon Relational Database Service (Amazon RDS) MySQL DB instance, an Amazon Aurora DB cluster, or an Amazon RDS PostgreSQL DB instance. The AWS Schema Conversion Tool supports the following conversions. Source Database Microsoft SQL Server MySQL Oracle PostgreSQL Target Database on Amazon RDS Amazon Aurora, MySQL, PostgreSQL PostgreSQL Amazon Aurora, MySQL, PostgreSQL Amazon Aurora, MySQL te You can migrate data from MySQL to an Amazon Aurora DB cluster without the AWS Schema Conversion Tool. For more information, see Migrating Data to an Amazon Aurora DB Cluster. 1

6 Converting Your Schema Converting Your Schema The AWS Schema Conversion Tool provides a project-based user interface to automatically convert the database schema of your source database into a format compatible with your target Amazon RDS instance. If schema from your source database cannot be automatically converted, the AWS Schema Conversion Tool provides guidance on how you can create equivalent schema in your target Amazon RDS database. For information about how to install the AWS Schema Conversion Tool, see Installing and Updating the AWS Schema Conversion Tool (p. 5). The following is a general outline of the steps to convert your database schema to Amazon RDS: 1. Create your target DB instance. 2. Create a new AWS Schema Conversion Tool project. 3. Connect the AWS Schema Conversion Tool to your source and target. 4. Create a database migration assessment report. 5. Convert your schema. 2

7 AWS Schema Conversion Tool Project Window 6. Apply the converted schema to Amazon RDS. 7. Create any schema elements that couldn't be automatically converted. For more details about each step, see Converting a Database Schema to Amazon RDS Using the AWS Schema Conversion Tool (p. 31). For an example that walks you through how to use the AWS Schema Conversion Tool, see Getting Started with the AWS Schema Conversion Tool (p. 10). AWS Schema Conversion Tool Project Window The following is what you see in the AWS Schema Conversion Tool when you create a schema migration project. 1. In the left panel, the schema from your source database is presented in a tree view. Your database schema is "lazy loaded." In other words, when you select an item from the tree view, the AWS Schema Conversion Tool gets and displays the current schema from your source database. 3

8 Related Topics 2. In the top middle panel, action items appear for schema elements from the source database engine that couldn't be automatically converted to the target database engine. 3. In the right panel, the schema from your target DB instance is presented in a tree view.your database schema is "lazy loaded." That is, at the point when you select an item from the tree view, the AWS Schema Conversion Tool gets and displays the current schema from your target database. 4. In the lower left panel, when you choose a schema element, properties describing the source schema element and the SQL command to create that element in the source database are displayed. 5. In the lower right panel, when you choose a schema element, properties describing the target schema element and the SQL command to create that element in the target database are displayed. You can edit this SQL command and save the updated command with your project. Related Topics Best Practices for the AWS Schema Conversion Tool (p. 60) 4

9 Installing and Updating the AWS Schema Conversion Tool The AWS Schema Conversion Tool is available for the following operating systems: Microsoft Windows (download) Mac OS X (download) Ubuntu Linux (download) Fedora Linux (download) te The AWS Schema Conversion Tool is supported only on 64-bit operating systems. The AWS Schema Conversion Tool also installs the Java Runtime Environment (JRE) version 8u45. Topics Important After you install the AWS Schema Conversion Tool, you must also install the required Java Database Connectivity (JDBC) drivers to connect to your source database and target Amazon Relational Database Service (Amazon RDS) DB instance. For details, see Required Database Drivers (p. 7). Installing the AWS Schema Conversion Tool on Windows (p. 6) Installing the AWS Schema Conversion Tool on Mac OS X (p. 6) Installing the AWS Schema Conversion Tool on Ubuntu Linux (p. 6) Installing the AWS Schema Conversion Tool on Fedora Linux (p. 7) Updating the AWS Schema Conversion Tool (p. 7) Required Database Drivers (p. 7) Related Topics (p. 9) 5

10 Installing the AWS Schema Conversion Tool on Windows Installing the AWS Schema Conversion Tool on Windows To install the AWS Schema Conversion Tool on Microsoft Windows 1. Download aws-schema-conversion-tool-1.0.latest.zip for Windows, and then extract AWS Schema Conversion Tool-1.0.msi. 2. Run the AWS Schema Conversion Tool-1.0.msi installer. By default, the AWS Schema Conversion Tool is installed in the c:\program Files\AWS Schema Conversion Tool folder. 3. When the installation is complete, you can run the AWS Schema Conversion Tool application. Install the required JDBC drivers for your source database engine and target DB instance database engine, if needed, and set the paths to the JDBC drivers in the global settings of the AWS Schema Conversion Tool. For details, see Required Database Drivers (p. 7). Installing the AWS Schema Conversion Tool on Mac OS X To install the AWS Schema Conversion Tool on Mac OS X 1. Download aws-schema-conversion-tool-1.0.latest.zip for Mac OS X, and then extract AWS Schema Conversion Tool-1.0.dmg. 2. In Finder, open AWS Schema Conversion Tool-1.0.dmg. 3. Drag AWS Schema Conversion Tool-1.0.dmg to the Applications folder. 4. When the installation is complete, you can run the AWS Schema Conversion Tool application. Install the required JDBC drivers for your source database engine and target DB instance database engine, if needed, and set the paths to the JDBC drivers in the global settings of the AWS Schema Conversion Tool. For details, see Required Database Drivers (p. 7). Installing the AWS Schema Conversion Tool on Ubuntu Linux Important The AWS Schema conversion tool is supported on Ubuntu Linux version (64-bit). To install the AWS Schema Conversion Tool on Ubuntu Linux 1. Download aws-schema-conversion-tool-1.0.latest.zip for Ubuntu, and then extract aws-schema-conversion-tool-1.0.deb. 2. Run the following command, where file-path is the folder that you downloaded the file to: sudo dpkg -i file-path/aws-schema-conversion-tool-1.0.deb 3. When the installation is complete, you can run the AWS Schema Conversion Tool application. Install the required JDBC drivers for your source database engine and target DB instance database engine, if needed, and set the paths to the JDBC drivers in the global settings of the AWS Schema Conversion Tool. For details, see Required Database Drivers (p. 7). 6

11 Installing the AWS Schema Conversion Tool on Fedora Linux Installing the AWS Schema Conversion Tool on Fedora Linux Important The AWS Schema conversion tool is supported on Fedora Linux version 22 (64-bit). To install the AWS Schema Conversion Tool on Fedora Linux 1. Download aws-schema-conversion-tool-1.0.latest.zip for Fedora, and then extract aws-schema-conversion-tool x86_64.rpm. 2. Run the following command, where file-path is the folder that you downloaded the file to: sudo yum install file-path/aws-schema-conversion-tool x86_64.rpm 3. When the installation is complete, you can run the AWS Schema Conversion Tool application. Install the required JDBC drivers for your source database engine and target DB instance database engine, if needed, and set the paths to the JDBC drivers in the global settings of the AWS Schema Conversion Tool. For details, see Required Database Drivers (p. 7). Updating the AWS Schema Conversion Tool To check whether new version of the AWS Schema Conversion Tool is available, choose Help, and then choose Check for Updates. If there is a newer version of the AWS Schema Conversion Tool than the version that you have installed, you are prompted to download and install the updated version. Required Database Drivers You must have the required JDBC drivers installed for the AWS Schema Conversion Tool to connect to your source database or target RDS DB instance. You can download the latest database drivers from the following locations. Database Engine Amazon Aurora Microsoft SQL Server MySQL Oracle Download Driver versions 7 and later are supported. PostgreSQL Installing JDBC Drivers on Linux You can use the following steps to install the JDBC drivers on your Linux system for use with the AWS Schema Conversion Tool. 7

12 Updating Global Settings To install JDBC drivers on your Linux system 1. Create a directory to store the JDBC drivers in. PROMPT>sudo mkdir p /usr/local/jdbc-drivers 2. Install the JDBC driver for your database engine using the commands shown following. Database Engine Amazon Aurora Installation Commands PROMPT> cd /usr/local/jdbc-drivers PROMPT> sudo tar xzvf /tmp/mysql-connector-java- X.X.X.tar.gz Microsoft SQL Server PROMPT> cd /usr/local/jdbc-drivers PROMPT> sudo tar xzvf /tmp/sqljdbc_x.x.x_enu.tar.gz MySQL PROMPT> cd /usr/local/jdbc-drivers PROMPT> sudo tar xzvf /tmp/mysql-connector-java- X.X.X.tar.gz Oracle PROMPT> cd /usr/local/jdbc-drivers PROMPT> sudo mkdir oracle-jdbc PROMPT> cd oracle-jdbc PROMPT> sudo cp -a /tmp/ojdbc7.jar. PostgreSQL PROMPT> cd /usr/local/jdbc-drivers PROMPT> sudo cp -a /tmp/postgresql-x.x.x.jre7.tar. Updating Global Settings After you have downloaded and installed the required JDBC drivers, you must update the settings in the AWS Schema Conversion Tool with the driver file locations. To update the driver file locations 1. In the AWS Schema Conversion Tool, choose Settings, and then choose Global Settings. 8

13 Related Topics 2. For Global settings, choose Drivers. Add the file path to the JDBC driver for your source database engine and your target RDS DB instance database engine. 3. Choose OK to exit the Global settings window. Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Getting Started with the AWS Schema Conversion Tool (p. 10) 9

14 Before You Begin Getting Started with the AWS Schema Conversion Tool Following, we walk you through how to create an AWS Schema Conversion Tool project and convert the schema from your source database to your target Amazon Relational Database Service (Amazon RDS) DB instance. The AWS Schema Conversion Tool supports the following conversions. Source Database Microsoft SQL Server MySQL Oracle PostgreSQL Target Database on Amazon RDS Amazon Aurora, MySQL, PostgreSQL PostgreSQL Amazon Aurora, MySQL, PostgreSQL Amazon Aurora, MySQL Before You Begin Before you perform the tasks described in this topic, you must first complete the following tasks: Install the AWS Schema Conversion Tool. For more information, see Installing and Updating the AWS Schema Conversion Tool (p. 5). Identify the connection information for your source database. Create your target Amazon RDS DB instance, if needed, and identify the connection information for your target DB instance. For more information, see the following documentation. Database Engine Amazon Aurora Relevant Documentation Creating an Amazon Aurora DB Cluster Connecting to an Amazon Aurora DB Cluster MySQL Creating a DB Instance Running the MySQL Database Engine Connecting to a DB Instance Running the MySQL Database Engine 10

15 Step 1: Create an AWS Schema Conversion Tool Project Database Engine PostgreSQL Relevant Documentation Creating a DB Instance Running the PostgreSQL Database Engine Connecting to a DB Instance Running the PostgreSQL Database Engine Step 1: Create an AWS Schema Conversion Tool Project The first time that you open the AWS Schema Conversion Tool, you automatically begin creating a database migration project using the Create New Database Migration Project wizard. You can create additional projects using the Create New Database Migration Project wizard by choosing New Project Wizard from the File menu. Optionally, you can create a project without the Create New Database Migration Project wizard by choosing New Project from the File menu. For more information, see Creating an AWS Schema Conversion Tool Project (p. 33). To create a database migration project using the Create New Database Migration Project wizard 1. Choose File, and then choose New Project Wizard. The wizard opens and the page Step1: Select Source appears. 11

16 Step 1: Create an AWS Schema Conversion Tool Project 2. On the page Step1: Select Source, add your local project settings and database connection information. Use the instructions shown following in the table for your source database engine. Microsoft SQL Server Source Database For This Parameter Project Name Location Source DB Engine Server Name Server Port Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose SQL Server. Type the Domain Name Service (DNS) name or IP address of your source database server. Type the port used to connect to your source database server. 12

17 Step 1: Create an AWS Schema Conversion Tool Project For This Parameter Instance name Username and Password Use SSL Do This Type the instance name for the SQL Server database. To find the instance name, run the query SELECT on your SQL Server database. Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. Select this option if you want to use Secure Sockets Layer (SSL) to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: Trust Server Certificate: Select this option to trust the server certificate. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. Sql Server Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). MySQL Source Database For This Parameter Project Name Location Source DB Engine Server Name Server Port Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose MySQL. Type the DNS name or IP address of your source database server. Type the port used to connect to your source database server. 13

18 Step 1: Create an AWS Schema Conversion Tool Project For This Parameter Username and Password Use SSL Do This Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. Select this option if you want to use SSL to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: Require SSL: Select this option if you want to connect to the server only through SSL. te If you choose Require SSL, it means that if the server doesn't support SSL, you can't connect to the server. If you don't choose Require SSL and the server doesn't support SSL, you can still connect to the server without using SSL. For more information, see Using Secure Connections. Verify Server Certificate: Select this option to verify the server certificate using a trust store. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. MySql Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). Oracle Source Database For This Parameter Project Name Location Source DB Engine Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose Oracle. 14

19 Step 1: Create an AWS Schema Conversion Tool Project For This Parameter Type Do This Choose the connection type to your database. Depending on your type, provide the following additional information: SID Server Name: The DNS name or IP address of your source database server. Server Port: The port used to connect to your source database server. Oracle SID: The Oracle System ID (SID). To find the Oracle SID, submit the following query to your Oracle database: SELECT sys_context('userenv','instance_name') AS SID FROM dual; Service Name Server Name: The DNS name or IP address of your source database server. Server Port: The port used to connect to your source database server. Service Name: The name of the Oracle service to connect to. TNS Alias TNS file path: The path to the file that contains the Transparent Network Substrate (TNS) name connection information. TNS file path: The TNS alias from this file to use to connect to the source database. TNS Connect Identifier TNS identifier: The identifier for the registered TNS connection information. Username and Password Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. 15

20 Step 1: Create an AWS Schema Conversion Tool Project For This Parameter Use SSL Do This Select this option if you want to use SSL to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: SSL Authentication: Select this option to use SSL authentication for the connection. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. Key Store: The location of a key store containing a private key and certificates. This value is required if SSL Authentication is selected and is otherwise optional. Trust Store Password: The password for the key store. This value is required if SSL Authentication is selected and is otherwise optional. Oracle Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). PostgreSQL Source Database For This Parameter Project Name Location Source DB Engine Server Name Server Port Database Username and Password Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose PostgreSQL. Type the DNS name or IP address of your source database server. Type the port used to connect to your source database server. Type the name of the PostgreSQL database. Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. 16

21 Step 1: Create an AWS Schema Conversion Tool Project For This Parameter Use SSL Do This Select this option if you want to use SSL to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: Verify Server Certificate: Select this option to verify the server certificate using a trust store. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. PostgreSQL Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). 3. Choose Test Connection to verify that you can successfully connect to your source database. 4. After you have finished adding the project information, and can successfully connect to your source database, choose Next. 5. On the page Step 2: Select Schema, choose the schema from your source database that you want to convert to your target RDS DB instance. 6. Choose Next to continue. The database migration assessment runs automatically after you choose Next. 7. On the page Step 3: Run the Database Migration Assessment, review the database migration assessment report, shown following. The database migration assessment report provides important information about the conversion of the schema from your source database to your target RDS DB instance. The report summarizes all of the schema conversion tasks and details actions to be taken for schema that cannot be converted to the DB engine of your target DB instance. The report also includes estimates of the amount of effort that it will take to write the equivalent code in your target DB instance for the schema that cannot be automatically converted. For more information on the database migration assessment report, see Creating and Using the Assessment Report (p. 47). 17

22 Step 1: Create an AWS Schema Conversion Tool Project 8. Choose Save to CSV or Save to PDF to save a local copy of the database migration assessment report as either a comma-separated values (CSV) file or a PDF file. This step is optional. You can view the database migration assessment report and save a local copy of it at any time after you create your project. 9. Choose Next to continue. The page Step 4: Select Target appears. 18

23 Step 1: Create an AWS Schema Conversion Tool Project 10. On the page Step 4: Select Target, add the information to connect to your target Amazon RDS DB instance. Use the instructions shown in the table following. For This Parameter Target DB Engine Server Name Server Port Username and Password Do This Choose the database engine for your target DB instance; Amazon Aurora, MySQL, or PostgreSQL. Type the DNS name of your target DB instance. Type the port used to connect to your target DB instance. Type the user name and password to connect to your target DB instance. te The AWS Schema Conversion Tool uses the password to connect to your target database only when you create your project or choose the Connect to target option in a project, where target is your target database. To guard against exposing the password for your target database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your target database as needed. 11. Choose Test Connection to verify that you can successfully connect to your target database. 12. Choose Finish to create your project. 19

24 Step 2: View the Schema from Your Source Database Step 2: View the Schema from Your Source Database Your AWS Schema Conversion Tool project displays the schema from your source database in the left panel. The schema is presented in a tree-view format, and each node of the tree is "lazy loaded." In other words, when you choose a node in the tree view, the AWS Schema Conversion Tool requests the schema information from your source database at that time. Step 3: Create the Schema Use the following procedure to create the converted schema. To create the converted schema 1. To see the main view of your project, choose View, and then Main View. 2. In the left panel that displays the schema from your source database, choose a schema object to convert. Open the context (right-click) menu for the object, and then choose Convert schema. 20

25 Step 3: Create the Schema When the AWS Schema Conversion Tool finishes converting the schema, you can view the proposed schema in the panel on the right of your project. At this point, no schema is applied to your target RDS DB instance. The planned schema is only part of your project. If you select a converted schema item, you can see the planned schema command in the panel at lower center for your target RDS DB instance. You can edit the schema in this window. The edited schema is stored as part of your project and is written to the target DB instance when you choose to apply your converted schema. 21

26 Step 4: Clear the Schema Step 4: Clear the Schema Before the AWS Schema Conversion Tool applies the schema to your target RDS DB instance, you can clear the planned schema from your project by opening the context (right-click) menu for the tree-view node for your target DB instance, and then choosing Refresh from Database. Because no schema has been written to your target DB instance, refreshing from the database removes the planned schema elements in your schema conversion tool project, to match what exists in your target DB instance. 22

27 Step 5: Update Your Source Schema Step 5: Update Your Source Schema You can update your AWS Schema Conversion Tool project with the most recent schema from your source database by opening the context (right-click) menu for the schema item from your source database that you want to update, and then choosing Refresh from Database. Doing this enables you to update your schema conversion tool project if changes have been made to the schema of your source database. 23

28 Step 6: Overwrite the Schema Step 6: Overwrite the Schema After you have refreshed the schema from your source database in your project, you can overwrite the converted schema in your project with updated schema. If you have made changes to the converted schema in your project, you lose those changes when you refresh the schema. To overwrite a converted schema in your project with an updated schema 1. In the left panel that displays the schema from your source database, choose the schema object to update the converted schema for. 2. Open the context (right-click) menu for the object, and then choose Convert Schema, as shown following. 24

29 Step 7: Create the Database Migration Assessment Report 3. In the Objects already exist in the target database. Replace? dialog box, choose to confirm that you want to overwrite the local schema. Step 7: Create the Database Migration Assessment Report The New Project wizard includes a step to create the database migration assessment report, which summarizes all of the action items for schema that cannot be converted to the engine of your target RDS DB instance.the report also includes estimates of the amount of effort that it will take to write the equivalent code in your target DB instance that cannot be automatically converted. You can create an updated database migration assessment report at any time in your project by using the following procedure. To create and view the database migration assessment report 1. In the left panel that displays the schema from your source database, choose a schema object to create an assessment report for. Open the context (right-click) menu for the object, and then choose Create Report, as shown following. 25

30 Step 7: Create the Database Migration Assessment Report The assessment report view then opens. 2. To explore the report, choose the Action Items tab. The Action Items tab displays a list of items that describe the schema that cannot automatically be converted to the database engine of your target RDS DB instance. 3. Select one of the action items from the list. tice that the AWS Schema Conversion Tool highlights the item from your schema that the action item applies to, as shown following. 26

31 Step 7: Create the Database Migration Assessment Report 4. To view the assessment report summary, choose the Summary tab. The Summary tab displays the summary information from the database migration assessment report. It shows the number of items that were automatically converted and the number of items that cannot be automatically converted. The summary also includes an estimate of the time that it will take to create schema in your target DB instance that are equivalent to those in your source database. An example is shown following. 27

32 Step 7: Create the Database Migration Assessment Report 5. To save the database migration assessment report as a PDF file and store it locally on your computer, choose the Summary tab, and then choose Save to PDF. The PDF file contains both the summary and action item information. You can also choose Save to CSV to save the report as a comma-separated values (CSV) file. The CSV file contains only action item information. 28

33 Step 8: Apply the Schema to the DB Instance Step 8: Apply the Schema to the DB Instance When you are ready, you can apply the converted database schema to your target RDS DB instance. After the schema has been applied to your target DB instance, you can update it based on the action items identified in the database migration assessment report. To apply the converted database schema to your target RDS DB instance Caution If you have an existing schema in your DB instance that matches the schema being applied, then the AWS Schema Conversion Tool overwrites the existing schema. This functionality is useful to update the schema in your target DB instance. However, be careful not to overwrite 29

34 Related Topics schema unintentionally especially a schema that you have modified in your target DB instance based on a database migration assessment report. 1. To apply the schema to your target DB instance, choose the schema element in the right panel of your project that displays the planned schema for your target DB instance. 2. Open the context (right-click) menu for the schema element, and then choose Apply to database. Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Installing and Updating the AWS Schema Conversion Tool (p. 5) 30

35 Converting a Database Schema to Amazon RDS Using the AWS Schema Conversion Tool The AWS Schema Conversion Tool automates much of the process of converting your database schema to an Amazon Relational Database Service (Amazon RDS) MySQL DB instance, an Amazon Aurora DB cluster, or a PostgreSQL DB instance. The AWS Schema Conversion Tool supports the following conversions. Source Database Microsoft SQL Server MySQL Oracle PostgreSQL Target Database on Amazon RDS Amazon Aurora, MySQL, PostgreSQL PostgreSQL Amazon Aurora, MySQL, PostgreSQL Amazon Aurora, MySQL The source and target database engines contain many different features and capabilities, and the AWS Schema Conversion Tool attempts to create an equivalent schema in your RDS DB instance wherever possible. If no direct conversion is possible, the AWS Schema Conversion Tool provides a list of possible actions for you to take. The AWS Schema Conversion Tool creates a database migration assessment report that includes information on the schema elements that cannot be converted, along with guidance on how you can manually create equivalent schema from your source database in your target DB instance. 31

36 To convert your database schema to Amazon RDS, you take the high-level steps shown in the following table. Step Description Create your target DB instance. Create the Amazon RDS for MySQL DB instance, Amazon Aurora DB cluster, or PostgreSQL DB instance to host your converted schema and data. For a MySQL or PostgreSQL DB instance, be sure to allocate enough storage for your data once it is converted. Create a new AWS Schema Conversion Tool project, and connect to your source database. Connect your AWS Schema Conversion Tool project to your target DB instance. Create a database migration assessment report. The AWS Schema Conversion Tool creates a database migration assessment report that details the schema elements that cannot be converted automatically. You can use this report to identify where you need to create a schema in your RDS DB instance that is compatible with your source database. Relevant Documentation Creating an Amazon Aurora DB Cluster Creating a DB Instance Running the MySQL Database Engine Creating a DB Instance Running the PostgreSQL Database Engine Creating a Project with Microsoft SQL Server as the Source (p. 34) Creating a Project with MySQL as the Source (p. 37) Creating a Project with Oracle as the Source (p. 40) Creating a Project with PostgreSQL as the Source (p. 44) Connecting to an Amazon Aurora DB Cluster Connecting to a DB Instance Running the MySQL Database Engine Connecting to a DB Instance Running the PostgreSQL Database Engine Creating and Using the Assessment Report (p. 47) 32

37 Create a Project Step Description Convert your schema. The AWS Schema Conversion Tool creates a local version of the converted schema for you to review, but it doesn't apply it to your target DB instance until you are ready. Update and refresh the schema in your AWS Schema Conversion Tool project, if necessary. Apply the converted schema to Amazon RDS. When you are ready, have the AWS Schema Conversion Tool apply the converted schema in your local project to your RDS DB instance. Create any schema elements that cannot be automatically converted. If you have schema elements that cannot be automatically converted to your target database engine, create equivalent schema elements in your target RDS DB instance. Caution Once you manually add schema elements that cannot be automatically converted to your target DB instance, take care if you plan to rewrite the converted schema from the AWS Schema Conversion Tool to your target DB instance. Rewriting the converted schema overwrites the schema in your target DB instance, and any schema elements that you have manually added are lost. You might want to save your manual work before rewriting the converted schema, or you might want to avoid rewriting the converted schema and update the schema in your target DB instance using a different method. Relevant Documentation Converting Your Schema (p. 51) Updating and Refreshing Your Schema (p. 55) Applying Your Schema (p. 57) Creating an AWS Schema Conversion Tool Project The following procedures show you how to create a AWS Schema Conversion Tool project by choosing New Project from the File menu. You can also create a new AWS Schema Conversion Tool project by choosing New Project Wizard from the File menu, which starts the Create New Database Migration Project wizard. For an example of using the wizard, see Getting Started with the AWS Schema Conversion Tool (p. 10). Creating a Project with Microsoft SQL Server as the Source (p. 34) 33

38 Microsoft SQL Server as the Source Creating a Project with MySQL as the Source (p. 37) Creating a Project with Oracle as the Source (p. 40) Creating a Project with PostgreSQL as the Source (p. 44) Creating a Project with Microsoft SQL Server as the Source The following procedure creates a AWS Schema Conversion Tool project with Microsoft SQL Server as the source database. To create your project with Microsoft SQL Server as the source 1. Start the AWS Schema Conversion Tool, and choose New Project from the File menu. Add the following preliminary project information. For This Parameter Project Name Location Source DB Engine Target DB Engine Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose SQL Server. Choose the database engine for your target DB instance; Amazon Aurora, MySQL, or PostgreSQL. 2. Choose OK to create your AWS Schema Conversion Tool project. 3. Choose Connect to SQL Server. The Connect to SQL Server dialog box appears. 34

39 Microsoft SQL Server as the Source 4. Provide the Microsoft SQL Server source database connection information. Use the instructions in the following table. For This Parameter Project Name Location Source DB Engine Server name Server port Instance name Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose SQL Server. Type the Domain Name Service (DNS) name or IP address of your source database server. Type the port used to connect to your source database server. Type the instance name for the SQL Server database. To find the instance name, run the query on your SQL Server database. 35

40 Microsoft SQL Server as the Source For This Parameter User name and Password Use SSL Do This Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. Select this option if you want to use Secure Sockets Layer (SSL) to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: Trust Server Certificate: Select this option to trust the server certificate. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. Sql Server Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). 5. Choose Test Connection to verify that you can successfully connect to your source database. 6. Choose OK to connect to your source database. 7. Choose Connect to target, where target indicates the database engine for your target DB instance. 8. Add the following information to connect to your target RDS DB instance. For This Parameter Target DB Engine Server name Server port Do This Choose the database engine for your target DB instance; Amazon Aurora, MySQL, or PostgreSQL. Type the DNS name of your target DB instance. Type the port used to connect to your target DB instance. 36

41 MySQL as the Source For This Parameter User name and Password Do This Type the user name and password to connect to your target DB instance. te The AWS Schema Conversion Tool uses the password to connect to your target database only when you create your project or choose the Connect to target option in a project, where target is your target database. To guard against exposing the password for your target database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your target database as needed. 9. Choose OK to connect to your target DB instance. Creating a Project with MySQL as the Source The following procedure creates a AWS Schema Conversion Tool project with MySQL as the source database. To create your project with MySQL as the source 1. Start the AWS Schema Conversion Tool, and choose New Project from the File menu. Add the following preliminary project information. For This Parameter Project Name Location Source DB Engine Target DB Engine Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose MySQL. Choose the database engine for your target DB instance; Amazon Aurora or PostgreSQL. 2. Choose OK to create your AWS Schema Conversion Tool project. 3. Choose Connect to MySQL. The Connect to MySQL dialog box appears. 37

42 MySQL as the Source 4. Provide the MySQL source database connection information. Use the instructions in the following table. For This Parameter Project Name Location Source DB Engine Server name Server port Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose MySQL. Type the DNS name or IP address of your source database server. Type the port used to connect to your source database server. 38

43 MySQL as the Source For This Parameter User name and Password Use SSL Do This Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. Select this option if you want to use SSL to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: Require SSL: Select this option if you want to connect to the server only through SSL. te If you choose Require SSL, it means that if the server doesn't support SSL, you can't connect to the server. If you don't choose Require SSL and the server doesn't support SSL, you can still connect to the server without using SSL. For more information, see Using Secure Connections. Verify Server Certificate: Select this option to verify the server certificate using a trust store. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. MySql Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). 5. Choose Test Connection to verify that you can successfully connect to your source database. 6. Choose OK to connect to your source database. 7. Choose Connect to target, where target indicates the database engine for your target DB instance. 8. Add the following information to connect to your target RDS DB instance. For This Parameter Target DB Engine Server name Server port Do This Choose the database engine for your target DB instance; Amazon Aurora or PostgreSQL. Type the DNS name of your target DB instance. Type the port used to connect to your target DB instance. 39

44 Oracle as the Source For This Parameter User name and Password Do This Type the user name and password to connect to your target DB instance. te The AWS Schema Conversion Tool uses the password to connect to your target database only when you create your project or choose the Connect to target option in a project, where target is your target database. To guard against exposing the password for your target database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your target database as needed. 9. Choose OK to connect to your target DB instance. Creating a Project with Oracle as the Source The following procedure creates a AWS Schema Conversion Tool project with Oracle as the source database. To create your project with Oracle as the source 1. Start the AWS Schema Conversion Tool, and choose New Project from the File menu. Add the following preliminary project information. For This Parameter Project Name Location Source DB Engine Target DB Engine Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose Oracle. Choose the database engine for your target DB instance; Amazon Aurora, MySQL, or PostgreSQL. 2. Choose OK to create your AWS Schema Conversion Tool project. 3. Choose Connect to Oracle. The Connect to Oracle dialog box appears. 40

45 Oracle as the Source 4. Provide the Oracle source database connection information. Use the instructions in the following table. For This Parameter Project Name Location Source DB Engine Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose Oracle. 41

46 Oracle as the Source For This Parameter Type Do This Choose the connection type to your database. Depending on your type, provide the following additional information: SID Server name: The DNS name or IP address of your source database server. Server port: The port used to connect to your source database server. Oracle SID: The Oracle System ID (SID). To find the Oracle SID, submit the following query to your Oracle database: SELECT sys_context('userenv','instance_name') AS SID FROM dual; Service Name Server name: The DNS name or IP address of your source database server. Server port: The port used to connect to your source database server. Service Name: The name of the Oracle service to connect to. TNS Alias TNS file path: The path to the file that contains the Transparent Network Substrate (TNS) name connection information. TNS file path: The TNS alias from this file to use to connect to the source database. TNS Connect Identifier TNS identifier: The identifier for the registered TNS connection information. User name and Password Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. 42

47 Oracle as the Source For This Parameter Use SSL Do This Select this option if you want to use SSL to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: SSL Authentication: Select this option to use SSL authentication for the connection. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. Key Store: The location of a key store containing a private key and certificates. This value is required if SSL Authentication is selected and is otherwise optional. Trust Store Password: The password for the key store. This value is required if SSL Authentication is selected and is otherwise optional. Oracle Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). 5. Choose Test Connection to verify that you can successfully connect to your source database. 6. Choose OK to connect to your source database. 7. Choose Connect to target, where target indicates the database engine for your target DB instance. 8. Add the following information to connect to your target RDS DB instance. For This Parameter Target DB Engine Server name Server port User name and Password Do This Choose the database engine for your target DB instance; Amazon Aurora, MySQL, or PostgreSQL. Type the DNS name of your target DB instance. Type the port used to connect to your target DB instance. Type the user name and password to connect to your target DB instance. te The AWS Schema Conversion Tool uses the password to connect to your target database only when you create your project or choose the Connect to target option in a project, where target is your target database. To guard against exposing the password for your target database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your target database as needed. 9. Choose OK to connect to your target DB instance. 43

48 PostgreSQL as the Source Creating a Project with PostgreSQL as the Source The following procedure creates a AWS Schema Conversion Tool project with PostgreSQL as the source database. To create your project with PostgreSQL as the source 1. Start the AWS Schema Conversion Tool, and choose New Project from the File menu. Add the following preliminary project information. For This Parameter Project Name Location Source DB Engine Target DB Engine Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose PostgreSQL. Choose the database engine for your target DB instance; Amazon Aurora or MySQL. 2. Choose OK to create your AWS Schema Conversion Tool project. 3. Choose Connect to PostgreSQL. The Connect to PostgreSQL dialog box appears. 44

49 PostgreSQL as the Source 4. Provide the PostgreSQL source database connection information. Use the instructions in the following table. For This Parameter Project Name Location Source DB Engine Server name Server port Database Do This Type a name for your project, which is stored locally on your computer. Type the location for your local project file. Choose PostgreSQL. Type the DNS name or IP address of your source database server. Type the port used to connect to your source database server. Type the name of the PostgreSQL database. 45

50 PostgreSQL as the Source For This Parameter User name and Password Use SSL Do This Type the user name and password to connect to your source database server. te The AWS Schema Conversion Tool uses the password to connect to your source database only when you create your project or choose the Connect to source option in a project, where source is your source database. To guard against exposing the password for your source database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your source database as needed. Select this option if you want to use SSL to connect to your database. Provide the following additional information, as appropriate, on the SSL tab: Verify Server Certificate: Select this option to verify the server certificate using a trust store. Trust Store: The location of a trust store containing certificates. Trust Store Password: The password for the trust store. PostgreSQL Driver Path Type the path to the driver to use to connect to the source database. For more information, see Required Database Drivers (p. 7). 5. Choose Test Connection to verify that you can successfully connect to your source database. 6. Choose OK to connect to your source database. 7. Choose Connect to target, where target indicates the database engine for your target DB instance. 8. Add the following information to connect to your target RDS DB instance. For This Parameter Target DB Engine Server name Server port Do This Choose the database engine for your target DB instance; Amazon Aurora or MySQL. Type the DNS name of your target DB instance. Type the port used to connect to your target DB instance. 46

51 Related Topics For This Parameter User name and Password Do This Type the user name and password to connect to your target DB instance. te The AWS Schema Conversion Tool uses the password to connect to your target database only when you create your project or choose the Connect to target option in a project, where target is your target database. To guard against exposing the password for your target database, the AWS Schema Conversion Tool doesn't store the password. If you close your AWS Schema Conversion Tool project and reopen it, you are prompted for the password to connect to your target database as needed. 9. Choose OK to connect to your target DB instance. Related Topics Converting a Database Schema to Amazon RDS Using the AWS Schema Conversion Tool (p. 31) Creating and Using the Assessment Report The database migration assessment report provides important information regarding the conversion of the schema from your source database to your target RDS DB instance. The report summarizes all of the schema conversion tasks and details the action items for schema that cannot be converted to the DB engine of your target DB instance. The report also includes estimates of the amount of effort that it will take to write the equivalent code in your target DB instance that cannot be automatically converted. In some cases when the schema from your source database cannot be automatically converted, you can modify those schema in your source database to a format that can be automatically converted to the database engine for your target DB instance. After you have modified the schema from your source database and verified that it is compatible with your application, refresh the metadata in your AWS Schema Conversion Tool project with the updated schema information, and then convert the schema again and create a new database migration assessment report. You can respond to the action items in the assessment report in different ways: Add equivalent schema manually You can write all of the schema that can be automatically converted to your target DB instance by choosing Apply to database in the right panel of your project. However, the schema that are written to your target DB instance won't contain the items that cannot be automatically converted. Those items are listed in your database migration assessment report. After applying the schema to your target DB instance, you can then manually create schema in your target DB instance that are equivalent to those in the source database. In some cases, you cannot create equivalent schema in your target DB instance. You might need to rearchitect a portion of your application and database to use the functionality that is available from the DB engine for your target DB instance. In other cases, you can simply ignore the schema that can't be automatically converted. Caution If you manually create schema in your target DB instance, don't choose the Apply to database option until after you have saved a copy of any manual work that you have done that is, any commands to create schema in your target RDS DB instance that were not automatically created by the AWS Schema Conversion Tool. Applying the schema from your project to your 47

52 Creating a Database Migration Assessment Report target DB instance overwrites schema of the same name in the target DB instance, and you lose any updates that you added manually. Modify your source database schema and refresh the schema in your project For some items, you might be best served to modify the database schema in your source database to schema that are both compatible with your application architecture, and can also be automatically converted to the DB engine of your target DB instance. After updating the schema in your source database and verifying that the updates are compatible with your application, choose Refresh from Database in the left panel of your project to update the schema from your source database. You can then convert your updated schema and generate the database migration assessment report again, and the action item for your updated schema will no longer appear. The advantage to this process is that your updated schema will always be available when you refresh from your source database. Creating a Database Migration Assessment Report Use the following procedure to create a database migration assessment report. To create a database migration assessment report 1. In the left panel that displays the schema from your source database, choose a schema object to create an assessment report for. 2. Open the context (right-click) menu for the object, and then choose Create Report. 48

53 Creating a Database Migration Assessment Report After you create an assessment report, the assessment report view opens, showing the Summary tab. The Summary tab displays the summary information from the database migration assessment report. It shows items that were automatically converted and items that cannot be automatically converted. For schema items that cannot be automatically converted to the target database engine, the summary includes an estimate of the effort that it will take to create schema in your target DB instance that are equivalent to those in your source database. The report categorizes the estimated time to convert these schema items as follows: Simple Actions that can be completed in less than 1 hour. Medium Actions that are more complex and can be completed in 1 to 4 hours. Significant Actions that are very complex and will take more than 4 hours to complete. You can save a local copy of the database migration assessment report as either a PDF file or a comma-separated values (CSV) file. The CSV file contains only action item information. The PDF file contains both the summary and action item information, as shown in the following example. 49

54 Creating a Database Migration Assessment Report The assessment report view also includes an Action Items tab. On this tab, the AWS Schema Conversion Tool displays a list of items that describe schema that cannot automatically be converted to the database engine of your target RDS DB instance. If you select an action item from the list, the AWS Schema Conversion Tool highlights the item from your schema that the action item applies to. 50

55 Related Topics Related Topics Converting a Database Schema to Amazon RDS Using the AWS Schema Conversion Tool (p. 31) Converting Your Schema After you have connected your project to both your source database and your target RDS DB instance, your AWS Schema Conversion Tool project displays the schema from your source database in the left panel. The schema is presented in a tree-view format, as shown following, and each node of the tree is "lazy loaded." In other words, when you choose a node in the tree view, the AWS Schema Conversion Tool requests the schema information from your source database at that time. You can choose schema items from your source database and then convert the schema to equivalent schema for the DB engine of your target DB instance.you can choose any schema item from your source database to convert. If the schema item that you chose is dependent on a parent item, then the AWS Schema Conversion Tool also generates the schema for the parent item. For example, if you choose a column from a table to convert, then the AWS Schema Conversion Tool generates the schema for the column, the table that the column is in, and the database that the table is in. When the AWS Schema Conversion Tool generates a converted schema, it doesn't immediately apply it to the target DB instance. Instead, the converted schema is stored locally until you are ready to apply it to the target DB instance. For more information, see Applying Your Schema (p. 57). To convert schema from your source database, choose a schema object to convert from the left panel of your project. Open the context (right-click) menu for the object, and then choose Convert schema, as shown following. 51

56 Converting Your Schema You can create a database migration assessment report that contains a summary of all of the action items displayed in the Action Items tab and save it as a PDF. The assessment report is useful for identifying and resolving schema items that cannot be automatically converted. For more information, see Creating and Using the Assessment Report (p. 47). After you have converted the schema from your source database, you can choose schema items from the left panel of your project and view the converted schema in the center panels of your project. The lower-center panel displays the properties of and the SQL command to create the converted schema, as shown following. 52

57 Editing Schema After you have converted your schema for the first time or created a database migration assessment report, you can save your project. The schema information from your source database will be saved with your project. This functionality means that you can work offline without being connected to your source database. The AWS Schema Conversion Tool will still connect to your source database to update the schema in your project if you choose Refresh from Database for your source database. For more information, see Updating and Refreshing Your Schema (p. 55). Editing Schema You can edit the converted schema and save the changes as part of your project. To edit converted schema 1. In the left panel that displays the schema from your source database, choose the schema item that you want to edit the converted schema for. 2. In the lower-center panel that displays the converted schema for the selected item, choose the SQL tab. 3. In the text displayed for the SQL tab, change the schema as needed. The schema is automatically saved with your project as you update it. 53

58 Clearing a Schema The changes that you make to converted schema are stored with your project as you make updates. If you newly convert a schema item from your source database, and you have made updates to previously converted schema for that item, those existing updates are replaced by the newly converted schema item based on your source database. Clearing a Schema Until you apply the schema to your target DB instance, the AWS Schema Conversion Tool only stores the converted schema locally in your project. You can clear the planned schema from your project by choosing the tree-view node for your target DB instance, and then choosing Refresh from Database. Because no schema has been written to your target DB instance, refreshing from the database removes the planned schema elements in your schema conversion tool project to match what exists in your target DB instance. 54

59 Related Topics Related Topics Converting a Database Schema to Amazon RDS Using the AWS Schema Conversion Tool (p. 31) Updating and Refreshing Your Schema You can update both the source schema and the target schema in your AWS Schema Conversion Tool project. Source If you update the schema for your source database, the AWS Schema Conversion Tool replaces the schema in your project with the latest schema from your source database. Using this functionality, you can update your project if changes have been made to the schema of your source database. Target If you update the schema for your target RDS DB instance, the AWS Schema Conversion Tool replaces the schema in your project with the latest schema from your target DB instance. If you haven't applied any schema to your target DB instance, the AWS Schema Conversion Tool clears the 55

60 Related Topics converted schema from your project. You can then convert the schema from your source database for a clean target DB instance. You update the schema in your AWS Schema Conversion Tool project by choosing Refresh from Database, as shown following. Related Topics Converting a Database Schema to Amazon RDS Using the AWS Schema Conversion Tool (p. 31) Saving and Applying Your Schema When the AWS Schema Conversion Tool generates converted schema (as shown in Converting Your Schema (p. 51)), it doesn't immediately apply the converted schema to the target DB instance. Instead, converted schema are stored locally in your project until you are ready to apply them to the target DB instance. Using this functionality, you can work with schema items that cannot be automatically converted to your target DB engine. For more information on items that cannot be automatically converted, see Creating and Using the Assessment Report (p. 47). You can optionally have the tool save your converted schema to a file as a SQL script prior to applying the schema to your target DB instance. You can also have the tool apply the converted schema directly to your target DB instance. 56

61 Saving Your Schema to a File Saving Your Schema to a File You can save your converted schema as SQL scripts in a text file. By using this approach, you can modify the generated SQL scripts from the AWS Schema Conversion Tool to address items that the tool cannot automatically convert. You can then run your updated scripts on your target DB instance to apply your converted schema to your target database. To save your converted schema as SQL scripts, open the context (right-click) menu for the schema element, and choose Save as SQL, as shown following. Applying Your Schema When you are ready to apply your converted schema to your target RDS DB instance, choose the schema element from the right panel of your project. Open the context (right-click) menu for the schema element, and then choose Apply to database, as shown following. 57

62 Related Topics Important The first time that you apply your converted schema to your target DB instance, the AWS Schema Conversion Tool adds a temporary work schema to your target DB instance. This schema implements system functions of the source database that are required when writing your converted schema to your target DB instance. Do not modify this schema, or you might encounter unexpected results in the converted schema that is written to your target DB instance. When your schema is fully migrated to your target DB instance, and you no longer need the AWS Schema Conversion Tool, you can delete the temporary work schema. The temporary work schema is named according to your source database as follows: Microsoft SQL Server: AWS_SQLSERVER_EXT MySQL: AWS_MYSQL_EXT Oracle: AWS_ORACLE_EXT PostgreSQL: AWS_POSTGRESQL_EXT Related Topics Converting a Database Schema to Amazon RDS Using the AWS Schema Conversion Tool (p. 31) Related Topics What Is the AWS Schema Conversion Tool? (p. 1) 58

63 Related Topics Installing and Updating the AWS Schema Conversion Tool (p. 5) Getting Started with the AWS Schema Conversion Tool (p. 10) 59

64 Memory Management and Performance Best Practices for the AWS Schema Conversion Tool Following, you can find information on best practices and options for using the AWS Schema Conversion Tool. Topics Memory Management and Performance (p. 60) Related Topics (p. 60) Memory Management and Performance You can configure the AWS Schema Conversion Tool with different memory performance settings. Increasing memory speeds up the performance of your conversion but uses more memory resources on your desktop. To set your memory management option, choose Global Settings from the Settings menu, and choose the Performance and Memory tab. Choose one of the following options: Fast conversion, but large memory consumption This option optimizes for speed of the conversion, but might require more memory for the object reference cache. Low memory consumption, but slower conversion This option minimizes the amount of memory used, but results in a slower conversion. Use this option if your desktop has a limited amount of memory. Balance speed with memory consumption This option optimizes provides a balance between memory use and conversion speed. Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Getting Started with the AWS Schema Conversion Tool (p. 10) Installing and Updating the AWS Schema Conversion Tool (p. 5) 60

65 Related Topics AWS Schema Conversion Tool Reference Following, you can find reference material for the AWS Schema Conversion Tool: Oracle to MySQL Supported Schema Conversion (p. 61) SQL Server to MySQL Supported Schema Conversion (p. 147) Keyboard Shortcuts (p. 167) Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Getting Started with the AWS Schema Conversion Tool (p. 10) Installing and Updating the AWS Schema Conversion Tool (p. 5) Oracle to MySQL Supported Schema Conversion The following sections list the schema elements from an Oracle database and whether they are supported for automatic conversion to MySQL using the AWS Schema Conversion Tool. Topics Statements (p. 62) Procedures (p. 66) Flow Control (p. 67) Packages (p. 67) Functions (p. 67) Operators (p. 77) Data Types (p. 81) Data Definition Language (DDL) (p. 83) Cursors (p. 86) Hints (p. 87) 61

66 Statements Exceptions (p. 89) Related Topics (p. 90) Statements Topics SELECT (p. 62) INSERT (p. 63) UPDATE (p. 64) DELETE (p. 65) MERGE (p. 66) TRUNCATE (p. 66) LOCK TABLE (p. 66) SELECT WITH AS SELECT DISTINCT UNIQUE ALL select_list BULK COLLECT INTO INTO record_name materialized view TABLE (collection_expression) MODEL START WITH CONNECT BY PIVOT Use a stored procedure to prepare data, or rewrite your query to avoid the WITH clause. You can try to include all of the fields from your table in an INTO clause. MySQL doesn't support the MODEL statement. MySQL doesn't support hierarchical queries. Use a stored procedure to prepare data. MySQL doesn't support hierarchical queries. Use a stored procedure to prepare data. 62

67 Statements XML UNPIVOT WHERE GROUP BY CUBE GROUPING SETS HAVING ORDER BY SIBLINGS NULLS FIRST NULLS LAST FOR UPDATE OF NOWAIT WAIT SKIP LOCKED UNION INTERSECT MINUS] Use a stored procedure to prepare data. Use a stored procedure to prepare data. MySQL doesn't support NULLS FIRST and NULLS LAST. In MySQL NULL sorting, NULL values go first for an ascending order and last for a descending order. Try rewriting the ORDER BY clause with CASE. Try using FOR UPDATE instead of FOR UPDATE OF. MySQL doesn't support WAIT and NOWAIT clauses. Try using FOR UPDATE without NOWAIT. Try using FOR UPDATE without SKIP LOCKED. INSERT INTO table PARTITION PARTITION FOR SUBPARTITION VIEW MATERIALIZED VIEW Either insert data into the overlying partition, or perform a manual conversion using the INSERT statement. Target a table with the INSERT statement instead of a VIEW. If the target view has an INSTEAD OF trigger, parse and execute the INSTEAD OF trigger code. Perform a manual conversion. 63

68 Statements subquery WITH table_collection_expression column VALUES subquery RETURNING INTO LOG ERRORS Perform this operation on the underlying tables instead. To perform this operation, divide the INSERT statement with the RETURNING clause into an INSERT statement with following SELECT statements and use the same key conditions in each SELECT.You can also use the last value that was generated by AUTO_INCREMENT column in the key condition. You can add error records by inserting them into the log in the exception block. Iterate through the errors in the exception block, add them to the log, and use the EXIT command when finished. UPDATE UPDATE [hint] table PARTITION PARTITION FOR SUBPARTITION VIEW MATERIALIZED VIEW subquery WITH table_collection_expression SET VALUE WHERE condition Either insert data into the overlying partition, or perform a manual transformation using the UPDATE statement. Perform an update on the underlying tables instead. Perform this operation on the underlying tables instead. 64

69 Statements RETURNING... INTO LOG ERRORS To perform this operation, divide the UPDATE statement with the RETURNING clause into an UPDATE statement with following INSERT statements that have the specified key conditions in the SELECT part. You can add error records by inserting them into the log in the exception block. Iterate through the errors in the exception block, add them to the log, and use the EXIT command when finished. te MySQL doesn't support FILESTREAM DATA. Perform a manual conversion to update the data in the file system file. DELETE DELETE FROM PARTITION PARTITION FOR SUBPARTITION VIEW MATERIALIZED VIEW subquery WITH table_collection_expression WHERE condition RETURNING INTO LOG ERRORS Either insert data into the overlying partition, or perform a manual transformation using the DELETE statement. Perform a manual conversion. Perform a manual conversion. Perform this operation on the underlying tables instead. To perform this operation, divide the DELETE statement with the RETURNING clause into a DELETE statement with following INSERT statements and use the same key conditions in each SELECT. You can add error records by inserting them into the log in the exception block. Iterate through the errors in the exception block, add them to the log, and use the EXIT command when finished. 65

70 Procedures MERGE Statement MERGE To achieve the effect of a MERGE statement, use separate INSERT, DELETE, and UPDATE statements. TRUNCATE TRUNCATE TABLE PRESERVE MATERIAL- IZED VIEW LOG PURGE MATERIALIZED VIEW LOG DROP STORAGE REUSE STORAGE LOCK TABLE PARTITION SUBPARTITION NOWAIT Procedures Item LOCK TABLE dbms_output.put_line dbms_output.put MySQL doesn't support the LOCK TABLE statement inside a stored procedure. Try using INSERT in the log table. To do this, you must add code into AWS_ORACLE_EXT.PUT_LINE. Try using INSERT in the log table. To do this, you must add code into AWS_ORACLE_EXT.PUT. 66

71 Flow Control Flow Control GOTO FORALL EXECUTE IMMEDIATE BULK COLLECT RETURNING BULK COL- LECT INTO LABEL Try using a WHILE DO statement. Try rewriting variables without using labels. Packages Item Initialization block, BEGIN END User type Global cursor Global user exception MySQL doesn't support EXCEPTION BLOCK in initialization blocks in packages. Try using CONTINUE HANDLER. Functions Topics Aggregate Functions (p. 68) Date and Time Functions (p. 69) Mathematical Functions (p. 71) Character (String) Functions (p. 72) Conversion Functions (p. 73) General Comparison Functions (p. 74) Encoding and Decoding Functions (p. 75) (p. 75) HTTP (p. 75) SMS (p. 75) NULL Functions (p. 75) User-defined Functions (p. 75) Large object Functions (p. 77) Hierarchical Functions (p. 77) 67

72 Functions Analytic Functions (p. 77) This section lists the Microsoft SQL Server built-in functions and indicates whether AWS Schema Conversion Tool performs an automatic conversion. Where MySQL doesn't support a function, consider creating a user-defined function. Aggregate Functions Function AVG COLLECT CORR CORR_* COUNT COVAR_POP COVAR_SAMP CUME_DIST DENSE_RANK FIRST GROUP_ID GROUPING GROUPING_ID LAST MAX MEDIAN MIN PERCENTILE_CONT PERCENTILE_DISC PERCENT_RANK RANK REGR_ (Linear Regression) Functions STATS_BINOMIAL_TEST STATS_CROSSTAB STATS_F_TEST 68

73 Functions Function STATS_KS_TEST STATS_MODE STATS_MW_TEST STATS_ONE_WAY_AN- OVA STATS_T_TEST_* STATS_WSR_TEST STDDEV STDDEV_POP STDDEV_SAMP SUM TRUNC VAR_POP VAR_SAMP VARIANCE Converts to: TRUNCATE() Date and Time Functions Function ADD_MONTHS(date, num) CURRENT_DATE CURRENT_TIMESTAMP DBTIMEZONE EXTRACT(YEAR FROM date) EXTRACT(MONTH FROM date) EXTRACT(DAY FROM date) EXTRACT(HOUR FROM time) EXTRACT(MINUTE FROM time) Converts to: TIMESTAMPADD(MONTH, num, date) Converts to: NOW() Converts to: NOW() Converts to: YEAR(date) Converts to: MONTH(date) Converts to: DAY(date) Converts to: HOUR(time) Converts to: MINUTE(time) 69

74 Functions Function EXTRACT(SECOND FROM time) FROM_TZ LAST_DAY(date) LOCALTIMESTAMP LOCALTIMESTAMP(prec) MONTHS_BETWEEN(date1, date2) NEW_TIME NEXT_DAY NUMTODSINTERVAL NUMTOYMINTERVAL ROUND (date) SESSIONTIMEZONE SYS_EXTRACT_UTC SYSDATE SYSTIMESTAMP TO_CHAR (datetime, format) TO_TIMESTAMP(exp) TO_TIMESTAMP_TZ TO_DSINTERVAL TO_YMINTERVAL TRUNC (datetime) TZ_OFFSET Converts to: SECOND(time) The maximum precision for the MySQL LOCALTIMESTAMP function is 6. If you need greater precision, create a userdefined function. Converts to: SYSDATE() Converts to: CURRENT_TIMESTAMP Converts to: DATE_FORMAT() te that the TO_CHAR and DATE_FORMAT format strings are different. Converts to: DATE(datetime) 70

75 Functions Mathematical Functions Function ABS(num) ACOS(num) ASIN(num) ATAN(num) ATAN2(x,y) BITAND(exp1, exp2) CEIL(num) COS(num) COSH(num) EXP(n) FLOOR(num) LN(num) LOG(num1, num2) MOD(dividend, divisor) NANVL(n2, n1) POWER(value, n) REMAINDER(n1, n2) ROUND (num, integer) SIGN(exp) SIN(num) SINH(num) SQRT(num) TAN(num) TANH(num) TRUNC (number) TRUNC(num, num2) VALUE(variable) WIDTH_BUCKET Converts to: (exp1 & exp2) Converts to: (EXP(num) + EXP(-num)) / 2 Converts to: (n1 - n2*round(n1/n2)) Converts to: TRUNCATE(num, 0) 71

76 Functions Character (String) Functions Function ASCII(str) CHR(num) CONCAT(char1, char2) INITCAP(string) INSTR(str, substr) INSTR(str, substr, pos) INSTR(str, substr, pos, num) LENGTH(string) LOWER(string) LPAD(string, len) LPAD(string, len, pad) LTRIM(string) LTRIM(string, set) NLS_INITCAP NLS_LOWER NLS_UPPER NLSSORT REGEXP_INSTR REGEXP_REPLACE REGEXP_SUBSTR REPLACE(str, search) REPLACE(str, search, replace) RPAD(string, len) RPAD(string, len, pad) RTRIM(string) RTRIM(string, set) Converts to: CHAR(num USING ASCII) Converts to: LOCATE (substr, str, pos) This is the same as the two-argument form of INSTR(), except that the order of the arguments is reversed. Converts to: LENGTH (string) Converts to: LPAD(string, len, ' ') Converts to: TRIM(LEADING set FROM string) Converts to: REPLACE(str, search, '') Converts to: RPAD(string, len, ' ') Converts to: TRIM(TRAILING set FROM string) 72

77 Functions Function SOUNDEX(string) SUBSTR(string, pos, len) TRANSLATE(string, from, to) TREAT TRIM([type trim FROM] string) UPPER(string) Conversion Functions Function ASCIISTR(string) BIN_TO_NUM(bit1, bit2, ) CAST CHARTOROWID COMPOSE CONVERT(string, charset) DECOMPOSE HEXTORAW NUMTODSINTERVAL NUMTOYMINTERVAL RAWTOHEX RAWTONHEX ROWIDTOCHAR ROWIDTONCHAR SCN_TO_TIMESTAMP TIMESTAMP_TO_SCN TO_BINARY_DOUBLE TO_BINARY_FLOAT TO_CHAR (character) Converts to: CONVERT(string USING charset) 73

78 Functions Function TO_CHAR (datetime, format) TO_CHAR (number, format) TO_CLOB TO_DATE TO_DSINTERVAL TO_LOB TO_MULTI_BYTE TO_NCHAR (character) TO_NCHAR (datetime) TO_NCHAR (number) TO_NCLOB TO_NUMBER TO_DSINTERVAL TO_SINGLE_BYTE TO_TIMESTAMP TO_TIMESTAMP_TZ TO_YMINTERVAL TRANSLATE... USING UNISTR Converts to: DATE_FORMAT(datetime, format) te that the TO_CHAR and DATE_FORMAT format strings are different. Converts to: FORMAT(number, decimal_digits) In MySQL, you can use FORMAT function as well as other string functions and expressions. Converts to: STR_TO_DATE(string, format) te that the TO_DATE and STR_TO_DATE format strings are different. Converts to: CHAR(string USING UCS2) General Comparison Functions Function GREATEST(exp, exp2, ) LEAST(exp, exp2, ) 74

79 Functions Encoding and Decoding Functions Function DECODE(exp, when, then,...) DUMP ORA_HASH VSIZE Converts to: CASE expression MySQL doesn t support sending . To send , use Amazon Simple Service (Amazon SES). HTTP MySQL doesn't support sending messages to HTTP endpoints. To send messages to HTTP and HTTPS endpoints, you can use the Amazon Simple tification Service (Amazon SNS). SMS MySQL doesn't support sending notifications by using SMS. To send and receive SMS notifications, you can use the Amazon Simple tification Service (Amazon SNS). NULL Functions Function COALESCE(exp1, exp2, ) LNNVL NULLIF(exp1, exp2) NVL(exp, replacement) NVL2(exp1, exp2, exp3) Converts to: NULLIF(exp1, exp2) Converts to: IFNULL(exp, replacement) Converts to: CASE expression User-defined Functions Return In MySQL, you can use statements that return a result set within a stored procedure but not within a stored function. 75

80 Functions Statement RETURN resultset RETURN record-type TYPE.. IS TABLE OF.. INDEX BY TYPE.. IS TABLE OF TYPE.. IS VARRAY(..) OF RETURN.. PIPELINED TYPE... IS REF CURSOR object-type Try changing the function to a stored procedure and use a table to store the results. Try changing the function to a stored procedure and change record-type items to separate parameters. Try changing the function to a stored procedure and use a table to store the results. Try changing the function to a stored procedure and use a table to store the results. Try changing the function to a stored procedure and use a table to store the results. Try changing the function to a stored procedure and use a table to store the results. Try changing the function to a stored procedure and use a table to store the results. Collections Item TYPE.. IS TABLE OF := collection_type(...) MySQL doesn't support table type variables. Try using a table. MySQL doesn't support table type collection methods. Try using a table. MySQL doesn't support the constructor for the collection type. Try using a table. Arguments Item UDT record-type UDT collection-type UDT object-type collection_name.first, collection_name.last, collection_name.count, collection_name.next 76

81 Operators Large object Functions Function BFILENAME EMPTY_BLOB EMPTY_CLOB Converts to an empty string. Converts to an empty string. Hierarchical Functions Function SYS_CON- NECT_BY_PATH Try creating a user-defined function. Analytic Functions MySQL doesn't support analytic functions. Try creating a user-defined function. Operators Topics Arithmetic Operators (p. 77) Assignment Operator (p. 78) Comparison Operators (p. 78) Logical Operators (p. 78) String Concatenation Operator (p. 79) Date and time format specifiers (p. 79) Arithmetic Operators * / MySQL handles date and time arithmetic differently. Verify that the converted schema is accurate. 77

82 Operators Assignment Operator = Comparison Operators > < >= <= <>!=!<!> Logical Operators IN NOT IN ANY SOME ALL BETWEEN x EXISTS LIKE IS NULL NOT AND 78

83 Operators OR String Concatenation Operator Date and time format specifiers YEAR YYYY YYY YY Y IYY IY I IYYY RRRR Q MM MON MONTH RM WW W IW D Default Conversion %Y %y %y %Y %m %b %M %V %V %w 79

84 Operators Day of the week (1=Sunday, 7=Saturday) DAY DD DDD DY J HH HH12 HH24 MI SS SSSSS FF AM, PM A.M., P.M. AD or A.D BC or B.C. TZD TZH TZM TZR Default Conversion Day of the week (0=Sunday, 6=Saturday) %W %e %j %a %h %h %H %i %S %p 80

85 Data Types Data Types Data type Default Conversion BFILE VARCHAR(255) Contains the file path to the BFILE. MySQL does not support the BFILE. Because BFILE data is made up of the path to a file, you can either store a filename and create a routine that gets the file from the file system, or store the file contents as a LONGBLOB. BINARY_FLOAT FLOAT BINARY_DOUBLE DOUBLE BLOB LONGBLOB CHAR TEXT CHAR(n), CHARACTER(n) CHAR(n), CHARACTER(n) CHAR(n), CHARACTER(n) VARCHAR(n) CLOB LONGTEXT DATE DATETIME DECIMAL, DEC DOUBLE DECIMAL(p,s), DEC(p,s) DECIMAL(p,s), DEC(p,s) DOUBLE PRECISION DOUBLE PRECISION FLOAT DOUBLE FLOAT(p) DOUBLE INTEGER, INT DECIMAL(38) INTERVAL YEAR TO MONTH DOUBLE INTERVAL YEAR(p) TO MONTH VARCHAR(30) INTERVAL DAY TO SECOND VARCHAR(30) INTERVAL DAY(p) TO SECOND(s) VARCHAR(30) LONG LONGTEXT LONG RAW LONGBLOB NCHAR TEXT 81

86 Data Types Data type Default Conversion NCHAR(n) NCHAR(n) NCHAR(n) NVARCHAR(n) NCHAR VARYING TEXT NCHAR VARYING(n) NCHAR VARYING(n) NCLOB LONGTEXT NUMBER(p,0), NUM- BER(p) DECIMAL(p,0), DECIM- AL(p) NUMBER(p,s) DECIMAL(p,s) NUMBER, NUMBER(*),NU- MERIC DOUBLE NUMERIC(p,s) NUMERIC(p,s) NVARCHAR2 TEXT NVARCHAR2(n) NVARCHAR(n) RAW VARBINARY(2000) RAW(n) BINARY(n) RAW(n) VARBINARY(n) REAL DOUBLE ROWID CHAR(10) SMALLINT DECIMAL(38) TIMESTAMP DATETIME TIMESTAMP(p) DATETIME(p) TIMESTAMP(p) MySQL expands fractional seconds support for TIME, DATETIME, and TIMESTAMP values, with up to microseconds (6 digits) precision. TIMESTAMP(p) WITH TIME ZONE DATETIME There is no a data type in MySQL that can store time zone information. DATE- TIME data type stores timestamps in the MySQL server time zone. UROWID TEXT UROWID(n) VARCHAR(n) VARCHAR TEXT 82

87 Data Definition Language (DDL) Data type Default Conversion VARCHAR(n) VARCHAR(n) VARCHAR2 TEXT VARCHAR2(n) VARCHAR(n) XMLTYPE LONGTEXT Data Definition Language (DDL) Topics CREATE TABLE (p. 83) CREATE INDEX (p. 84) CREATE TRIGGER (p. 84) CREATE VIEW (p. 85) CREATE CONSTRAINT (p. 86) CREATE SEQUENCE (p. 86) CREATE TABLE CREATE TABLE statements are converted automatically except for the following: OBJECT TABLE CLUSTERED TABLE EXTERNAL TABLE GLOBAL TEMPORARY TABLE Partitioned tables Virtual columns Functions as default values NESTED TABLE columns converted MySQL doesn't support OBJECT TABLE. Revise your code to avoid OBJECT TABLE. MySQL doesn't support CLUSTERED TABLE. Try using a table with triggers. MySQL doesn't support EXTERNAL TABLE. Try using a table. MySQL doesn't support GLOBAL TEMPORARY TABLE. Try using a temporary table. MySQL doesn't support all partition types. Perform a manual conversion for the partition types that aren't supported. MySQL doesn't support virtual columns. Represent virtual columns using a view. MySQL doesn't support functions as default values. Try using a trigger. MySQL doesn't support tables with NESTED TABLE columns. Revise any tables with NESTED TABLE columns to avoid these columns. 83

88 Data Definition Language (DDL) COLUMN(TABLE) converted MySQL doesn't support the objects column. Create a userdefined function. CREATE INDEX CREATE INDEX statements are converted automatically except that MySQL does not support bitmap, function-based, or domain indexes. CREATE TRIGGER CREATE TRIGGER statements are converted automatically except for the following: COMPOUND INSTEAD OF INSERTING UPDATING DELETING without FOR EACH ROW FOLLOWS PRECEDES UPDATE OF REFERENCING NEW AS OLD AS WHEN(condition) ON NESTED TABLE trigger-status=disabled create-date modify-date status converted MySQL doesn't support compound triggers. Create a single trigger for each part of the compound trigger. MySQL doesn't support INSTEAD OF. Try using a BEFORE trigger. MySQL doesn t support conditional predicates. MySQL doesn't support statement triggers. Try including FOR EACH ROW. MySQL doesn't support the FOLLOWS PRECEDES clause. Try using a FOR EACH ROW trigger. MySQL doesn't support the UPDATE OF clause. Try using a FOR EACH ROW trigger. MySQL doesn't support the REFERENCING clauses. Modify references to pseudorows to use OLD and NEW instead. MySQL doesn't support WHEN(condition) triggers. Apply the condition for WHEN in the trigger body. MySQL doesn't support the DISABLED clause. Drop the trigger instead. MySQL doesn't support create-date for triggers. Try using a FOR EACH ROW trigger. MySQL doesn't support modify-date for triggers. Try using a FOR EACH ROW trigger. MySQL doesn't support trigger status values. Try using a FOR EACH ROW trigger. 84

89 Data Definition Language (DDL) description converted MySQL doesn't support descriptions for triggers. In MySQL, you can get a trigger description using INFORM- ATION_SCHEMA.TRIGGERS. MySQL doesn't support the REFERENCING clause. The following are the corresponding values between Oracle(USER_TRIGGERS) and MySQL(INFORMATION_SCHEMA.TRIGGERS): TABLE_OWNER -> TRIGGER_SCHEMA TRIGGER_NAME -> TRIGGER_NAME TRIGGER_TYPE -> ACTION_TIMING TRIGGERING_EVENT -> EVENT_MANIPULATION TABLE_NAME -> EVENT_OBJECT_TABLE REFERENCING_NAMES -> ACTION_REFER- ENCE_NEW_ROW(always is NEW), ACTION_REFER- ENCE_OLD_ROW(always is OLD) triggering-event=ddl_events base-object-type=view base-object-type=schema triggering-event=database_events base-object-type=data- BASE action-type=call or PL/SQL crossedition=for- WARD/REVERSE fire-once=yes apply-server-only=yes referencing-names=par- ENT CREATE VIEW CREATE VIEW statements are converted automatically except for the following: FORCE converted 85

90 Cursors NOFORCE WITH READ ONLY create-date modify-date status oid-text view-type-owner view-type superview-name editioning-view encrypted-view CAST NOFORCE is the default behavior for MySQL. You don't need to specify this option. MySQL doesn t support views with nested table columns. CREATE CONSTRAINT CREATE CONSTRAINT statements are converted automatically except for the following: DISABLE, status=dis- ABLED Foreign keys of different types constraint-type converted converted My SQL doesn't support constraints with the status DIS- ABLE. Drop the constraint. MySQL doesn't support foreign keys with different types of columns and referenced columns. Modify the column types using an equivalent of the column data types in the original database. MySQL doesn't support the constraint check option on a view. Try using a trigger. CREATE SEQUENCE MySQL doesn't support sequences. Try developing a system for sequences in your application. Cursors Cursors are converted automatically except for the following: 86

91 Hints SQLAttribute REF CURSOR SYS_REFCURSOR CURSOR REF_CURSOR variable MySQL doesn't support the cursor attribute SQL%ISOPEN MySQL doesn't support the cursor attribute SQL%BULK_ROWCOUNT. To calculate processed rows, use a variable. MySQL doesn't support the REF CURSOR object. Perform a manual conversion. MySQL doesn't support a variable of SYS_REFCURSOR type. Perform a manual conversion. The AWS Schema Conversion Tool cannot automatically transform the SELECT statement for an implicit cursor. Try rewriting the SELECT statement. The SELECT statement for the REF_CURSOR variable cannot be transformed.try rewriting the SELECT statement. Hints MySQL doesn't support hints. Try using MySQL performance tuning methods or perform a manual conversion. /*+ ALL_ROWS */ /*+ AND_EQUAL(table index...) */ /*+ APPEND */ /*+ CACHE(table) */ /*+ CHOOSE */ /*+ CLUSTER(table) */ /*+ CURSOR_SHAR- ING_EXACT */ /*+ DRIVING_SITE(table) */ /*+ DYNAMIC_SAMPLING */ /*+ EX- PAND_GSET_TO_UNION */ /*+ FACT(table) */ converted converted 87

92 Hints /*+ FIRST_ROWS(n) */ /*+ FULL(table) */ /*+ HASH */ /*+ HASH_SJ */ /*+ INDEX(table index) */ /*+ INDEX_ASC(table index) */ /*+ INDEX_COMBINE(table index) */ /*+ INDEX_DESC(table index) */ /*+ INDEX_FFS(table index) */ /*+ LEADING(table) */ /*+ MERGE(table) */ /*+ MERGE_SJ */ /*+ NL_SJ */ /*+ NO_EXPAND */ /*+ NO_INDEX(table index) */ /*+ NO_MERGE(table) */ /*+ NO_PARALLEL(table) */ /*+ NO_PARALLEL_IN- DEX(table index) */ /*+ NO_PUSH_PRED(subquery) */ /*+ NO_PUSH_SUBQ(subquery) */ /*+ NO_REWRITE */ /*+ NO_UNNEST */ /*+ NOAPPEND */ /*+ NOCACHE(table) */ /*+ NOFACT(table) */ converted 88

93 Exceptions /*+ ORDERED */ /*+ ORDERED_PREDIC- ATES */ /*+ PARALLEL(table server_num) */ /*+ PARALLEL_IN- DEX(table index server_num) */ /*+ PQ_DISTRIBUTE(table out_distr in_distr) */ /*+ PUSH_PRED(subquery) */ /*+ PUSH_SUBQ(subquery) */ /*+ REWRITE */ /*+ ROWID(table) */ /*+ RULE */ /*+ STAR */ /*+ STAR_TRANSFORMA- TION */ /*+ UNNEST */ /*+ USE_CONCAT */ /*+ USE_HASH(table1 table2) */ /*+ USE_MERGE(table1 table2) */ converted Exceptions Item RAISE %s converted MySQL doesn't support the RAISE command. Review the exception, and if possible convert it to an exception using the SIGNAL or RESIGNAL statement. MySQL doesn't support the %s exception. Review the exception, and if possible convert it to an exception using the SIGNAL or RESIGNAL statement. 89

94 Related Topics Item EXCEPTION PRAGMA EXCEP- TION_INIT PROC_RAISE_APPLICA- TION_ERROR converted MySQL doesn't support the EXCEPTION declaration. Use the DECLARE... CONDITION statement. MySQL doesn't support the PRAGMA EXCEPTION_INIT declaration. Use the DECLARE... CONDITION statement. MySQL doesn't support the PROC_RAISE_APPLICA- TION_ERROR statement. Use the DECLARE... CONDI- TION statement. Try using the SIGNAL or RESIGNAL statement. Built-in exceptions Exception INVALID_NUMBER converted TIMEOUT_ON_RE- SOURCE TRANSAC- TION_BACKED_OUT INVALID_CURSOR NOT_LOGGED_ON LOGIN_DENIED STORAGE_ERROR PROGRAM_ERROR Try creating a user exception. Try creating a user exception. Try creating a user exception. You can use one of several handlers for invalid cursors. Choose the correct handler based on the issue. Try creating a user exception. Try creating a user exception. You can use one of several handlers for invalid cursors. Choose the correct handler based on the issue. Try using the handler " Internal Error." Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Getting Started with the AWS Schema Conversion Tool (p. 10) Installing and Updating the AWS Schema Conversion Tool (p. 5) 90

95 Microsoft SQL Server to PostgreSQL Supported Schema Conversion Data Definition Language (DDL) Naming objects AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Supported Schema Conversion Schemas Tables, Columns Statements ALTER INDEX ALTER PROCEDURE ALTER TRIGGER ALTER VIEW CREATE FUNCTION CREATE PROCEDURE CREATE SEQUENCE IDENTITY (x,y) TRUNCATE TABLE UPDATE STATISTICS Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Automatic migration of inline functions is not supported. Default parameters specified for any function are skipped. Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) 91

96 Data Definition Language (DDL) ALTER TABLE ADD ALTER COLUMN DROP COLUMN DROP CONSTRAINT ENABLE/DISABLE TRIG- GER Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) CREATE INDEX CLUSTER option COLUMNSTORE index INCLUDE clause Other INDEX options SPATIAL index UNIQUE option XML index Issue 7679: PostgreSQL doesn't support computed columns (p. 137) Issue 7781: PostgreSQL doesn't support the PAD_INDEX option in indexes (p. 136) Issue 7682: PostgreSQL doesn't support the INCLUDE option in indexes (p. 136) Issue 7781: PostgreSQL doesn't support the PAD_INDEX option in indexes (p. 136) Issue 7781: PostgreSQL doesn't support the PAD_INDEX option in indexes (p. 136) Issue 7781: PostgreSQL doesn't support the PAD_INDEX option in indexes (p. 136) CREATE TABLE Partitioned tables Regular tables 92

97 Data Definition Language (DDL) Temporary tables Wide tables Issue 7680: PostgreSQL doesn't support global temporary tables (p. 137) CREATE TRIGGER FOR EACH STATEMENT Triggers INSTEAD OF Triggers Trigger event (INSERT/UP- DATE/DELETE ) Trigger time (BE- GORE/AFTER) Issue 7809: In PostgreSQL there are no analogues of the tables 'inserted' and 'deleted' (p. 143) Issue 7809: In PostgreSQL there are no analogues of the tables 'inserted' and 'deleted' (p. 143) Issue 7809: In PostgreSQL there are no analogues of the tables 'inserted' and 'deleted' (p. 143) Issue 7809: In PostgreSQL there are no analogues of the tables 'inserted' and 'deleted' (p. 143) CREATE VIEW CREATE VIEW Updateable Views VIEW DROP Statements DROP TABLE DROP VIEW Other types of objects 93

98 Data Manipulation Language (DML) Data Manipulation Language (DML) for statements Join Hints Query Hints Table Hint WHERE Joins Cross Joins Cross join Cross join with condition Inner Joins Inner Joins Outer Joins Full join Full outer join Left join Left outer join Right join Right outer join 94

99 Data Manipulation Language (DML) Predicates for statements Boolean conditions Exists conditions In conditions Null conditions Pattern matching conditions Range conditions Comparison conditions =, <>, <, <=, >, >= ANY, SOME, ALL Issue 7805: PostgreSQL doesn't support operator [t less than] (p. 140) Statements DELETE CURRENT OF FROM OUTPUT TOP VALUES WITH Issue 7659: The scope table-variables and temporary tables is different. You must apply manual conversion, if you are using recursion (p. 135) Issue 7797: PostgreSQL doesn't have analog for option "OUTPUT" with using the implicit table "deleted" in the operator for UPDATE (p. 145) Issue 7798: PostgreSQL doesn't support TOP option in the operator DELETE (p. 138) 95

100 Data Manipulation Language (DML) INSERT DEFAULT DEFAULT VALUES FROM INTO OUTPUT TOP VALUES WITH Issue 7797: PostgreSQL doesn't have analog for option "OUTPUT" with using the implicit table "deleted" in the operator for UPDATE (p. 145) Issue 7798: PostgreSQL doesn't support TOP option in the operator DELETE (p. 138) SELECT GROUP BY clause with an expression GROUP BY clause with multiple tables GROUP BY CUBE Group By Grouping Sets GROUP BY ROLLUP Limiting the number of rows returned Select all columns (using the * and aliases) Select all columns (using the *) Select subset of the columns Issue 7654: PostgreSQL doesn't support the option GROUP BY CUBE. Automatic conversion can't be performed (p. 141) Issue 7655: PostgreSQL doesn't support the option GROUP BY GROUPING SETS. Automatic conversion can't be performed (p. 141) Issue 7653: PostgreSQL doesn't support the option GROUP BY ROLLUP. Automatic conversion can't be performed (p. 141) 96

101 Data Manipulation Language (DML) Select with calculations Select with column heading Select with constants Specifying a ascending order Specifying a collation Specifying a conditional order Specifying a descending order Specifying a percentage Specifying a percentage (argument 100 percent) Specifying an alias as the sort column Specifying an expression as the sort column Specifying both ascending and descending order TOP with a variable Using ORDER BY and OFFSET command Using ORDER BY in a ranking function Using ORDER BY with UNION Using WITH TIES WHERE with BETWEEN WHERE with combination of predicates WHERE with CONTAINS WHERE with EXISTS subquery WHERE with FREETEXT WHERE with IN custom list Issue 7605: PostgreSQL doesn't support the WITH TIES option (p. 141) 97

102 Data Manipulation Language (DML) WHERE with IN subquery WHERE with LIKE WHERE with negates a Boolean input WHERE with NULL Issue 7795: PostgreSQL is case sensitive. Check the string comparison (p. 141) DISTINCT DISTINCT FROM FROM GROUP BY GROUP BY HAVING HAVING 98

103 Data Manipulation Language (DML) ORDER BY ORDER BY TOP TOP WHERE WHERE UPDATE CURRENT OF DEFAULT FILESTREAM Data FROM OUTPUT TOP VALUES WITH Issue 7797: PostgreSQL doesn't have analog for option "OUTPUT" with using the implicit table "deleted" in the operator for UPDATE (p. 145) Issue 7796: PostgreSQL doesn't support TOP option in the operator UPDATE (p. 144) 99

104 Data Types Data Types BIGINT BINARY BIT CHAR, CHARACTER DATETIME DATETIMEOFFSET DEC, DECIMAL DOUBLE PRECISION FLOAT GEOGRAPHY GEOMETRY HIERARCHYID IDENTITY INT, INTEGER MONEY NCHAR NTEXT NUMERIC NVARCHAR REAL ROWVERSION SMALL MONEY SMALLDATETIME SMALLINT SQL_VARIANT SYSNAME TABLE TEXT TIMESTAMP 100

105 Database Mail TINYINT UNIQUEIDENTIFIER VARBINARY VARCHAR XML to UUID if the PostgreSQL instance has the uuidossp module installed. The uuid-ossp module provides functions to generate universally unique identifiers (UUIDs) using one of several standard algorithms. Database Mail Accounts and Profiles Database Mail Configuration Objects Database Mail Messaging Objects Database Mail Settings Security sp_send_dbmail sysmail_add_account_sp sysmail_add_profile_sp sysmail_allitems sysmail_configure_sp sysmail_delete_account_sp sysmail_delete_log_sp sysmail_add_principalprofile_sp sysmail_add_profileaccount_sp sysmail_delete_mailitems_sp sysmail_delete_principalprofile_sp 101

106 Database Mail sysmail_delete_profile_sp sysmail_event_log sysmail_faileditems sysmail_help_account_sp sysmail_help_configure_sp sysmail_help_profile_sp sysmail_help_queue_sp sysmail_help_status_sp sysmail_help_status_sp sysmail_mailattachments sysmail_sentitems sysmail_start_sp sysmail_start_sp sysmail_stop_sp sysmail_stop_sp sysmail_unsentitems sysmail_update_profile_sp sysmail_delete_profileaccount_sp sysmail_help_principalprofile_sp sysmail_help_profileaccount_sp sysmail_update_account_sp sysmail_update_principalprofile_sp sysmail_update_principalprofile_sp sysmail_update_profileaccount_sp System State 102

107 Functions Functions

108 Functions Aggregate AVG CHECKSUM_AGG COUNT COUNT_BIG GROUPING GROUPING_ID MAX MIN STDEV STDEVP SUM VAR VARP Built-in Functions Aggregate Functions Cursor Functions Metadata Functions Security Functions 104

109 Functions System Functions Text and Image Functions Conversion CAST CONVERT PARSE TRY_CAST TRY_CONVERT TRY_PARSE Date and Time CURRENT_TIMESTAMP DATEADD DATEDIFF DATEFROMPARTS DATENAME DATEPART DATETIME2FROMPARTS DATETIMEFROMPARTS DATETIMEOFFSET- FROMPARTS DAY EOMONTH System Statistical Functions 105

110 Functions GETDATE GETUTCDATE ISDATE MONTH SMALLDATETIME- FROMPARTS SWITCHOFFSET SYSDATETIME SYSDATETIMEOFFSET SYSUTCDATETIME TIMEFROMPARTS TODATETIMEOFFSET YEAR Mathematical ABS() ACOS() ASIN() ATAN() ATN2 () CEILING() COS() COT() DEGREES() EXP() FLOOR() LOG() LOG10() 106

111 Functions PI() POWER() RADIANS() RAND() RAND(seed) ROUND() ROUND() SIGN() SIN() SQRT() SQUARE() TAN() Ranking Functions DENSE_RANK NTILE RANK ROW_NUMBER Rowset Functions CONTAINSTABLE FREETEXTTABLE OPENDATASOURCE OPENQUERY OPENROWSET OPENXML 107

112 Functions Scalar Functions ABS() ACOS() ASCII ASIN() ATAN() ATN2 () AVG CEILING() CHAR CHARINDEX CHECKSUM CHECKSUM_AGG CHOOSE CONCAT COS() COT() COUNT COUNT_BIG CURRENT_TIMESTAMP CURRENT_USER DATABASE_PRINCIP- AL_ID DATEADD DATEDIFF DATEFROMPARTS DATENAME DATEPART DATETIME2FROMPARTS DATETIMEFROMPARTS 108

113 Functions DATETIMEOFFSET- FROMPARTS DAY DEGREES() DIFFERENCE EOMONTH ERROR_LINE ERROR_MESSAGE ERROR_NUMBER ERROR_PROCEDURE ERROR_SEVERITY ERROR_STATE EXP() FLOOR() FORMAT FORMATMESSAGE GETDATE GETUTCDATE GROUPING GROUPING_ID HOST_ID HOST_NAME IIF ISDATE ISNULL ISNUMERIC LEFT LEN LOG() LOG10() Implemented in Extension Library 109

114 LOWER LTRIM MAX MIN MONTH NCHAR ORIGINAL_LOGIN PARSENAME PATINDEX PI() POWER() PRINT QUOTENAME RADIANS() RAND() REPLACE REPLICATE REVERSE RIGHT ROUND() RTRIM SCHEMA_NAME SESSION_USER SIGN() SIN() SMALLDATETIME- FROMPARTS SOUNDEX SPACE SQRT() SQUARE() 110 AWS Schema Conversion Tool User Guide Functions

115 Functions STDEV STDEVP STR STUFF SUBSTRING SUM SWITCHOFFSET SYSDATETIME SYSDATETIMEOFFSET SYSUTCDATETIME TAN() TIMEFROMPARTS TODATETIMEOFFSET UNICODE UPPER VAR VARP YEAR String ASCII CHAR CHARINDEX CONCAT DIFFERENCE FORMAT LEFT LEN 111

116 Operators LOWER LTRIM NCHAR PATINDEX QUOTENAME REPLACE REPLICATE REVERSE RIGHT RTRIM SOUNDEX SPACE STR STUFF SUBSTRING UNICODE UPPER Operators Arithmetic operators - (Subtract) % (Modulo) * (Multiply) Issue 7774: Unable to perform an automated migration of the arithmetic operations with mixed types of operands (p. 131) Issue 7774: Unable to perform an automated migration of the arithmetic operations with mixed types of operands (p. 131) Issue 7774: Unable to perform an automated migration of the arithmetic operations with mixed types of operands (p. 131) 112

117 Operators / (Divide) + (Add) Issue 7774: Unable to perform an automated migration of the arithmetic operations with mixed types of operands (p. 131) Issue 7774: Unable to perform an automated migration of the arithmetic operations with mixed types of operands (p. 131) Assignment Operator = Bitwise Operators & (Bitwise AND) ^ (Bitwise Exclusive OR) (Bitwise OR) Issue 7804: PostgreSQL doesn't support operator [Bitwise exclusive OR] (p. 140) Comparison Operators Comparison Operators Issue 7805: PostgreSQL doesn't support operator [t less than] (p. 140) Logical Operators Logical Operators 113

118 Other Set operators EXCEPT INTERSECT UNION UNION ALL String Concatenation Operator Unary Operators Unary Operators Other CHECKSUM CHOOSE CURRENT_USER DATABASE_PRINCIP- AL_ID ERROR_LINE ERROR_MESSAGE ERROR_NUMBER ERROR_PROCEDURE String Concatenation Operator 114

119 Service Broker ERROR_SEVERITY ERROR_STATE FORMATMESSAGE HOST_ID HOST_NAME IIF ISNULL ISNUMERIC Logical Functions NEWID ORIGINAL_LOGIN Other PRINT SCHEMA_NAME Security Functions SESSION_USER System Functions Service Broker ALTER QUEUE ALTER SERVICE BEGIN CONVERSATION TIMER BEGIN DIALOG CONVER- SATION CREATE QUEUE CREATE SERVICE DROP QUEUE DROP SERVICE 115

120 Service Broker END CONVERSATION GET CONVERSATION GROUP GET TRANSMIS- SION_STATUS MOVE CONVERSATION Queue management RECEIVE SEND Service Broker Catalog Views Service Broker Related Dynamic Management Views Service Broker Statements Service management sys.conversation_endpoints sys.conversation_groups sys.conversation_priorities sys.dm_broker_connections sys.routes sys.dm_broker_activated_tasks sys.dm_broker_forwarded_messages sys.dm_broker_queue_monitors sys.message_type_xml_schema_collection_usages sys.remote_service_bindings sys.service_contract_message_usages sys.service_contract_usages sys.service_contracts 116

121 SQL Server Agent sys.service_queue_usages sys.service_queues sys.services sys.transmission_queue SQL Server Agent sp_add_alert sp_add_category sp_add_job sp_add_jobschedule sp_add_jobserver sp_add_jobstep sp_add_notification sp_add_operator sp_add_proxy sp_add_schedule sp_add_targetservergroup sp_add_targetsvrgrp_member sp_apply_job_to_targets sp_attach_schedule sp_cycle_agent_errorlog sp_cycle_errorlog sp_delete_alert sp_delete_category sp_delete_job sp_delete_jobschedule sys.service_message_types 117

122 SQL Server Agent sp_delete_jobserver sp_delete_jobstep sp_delete_jobsteplog sp_delete_notification sp_delete_operator sp_delete_proxy sp_delete_schedule sp_delete_targetserver sp_detach_schedule sp_enum_login_for_proxy sp_grant_login_to_proxy sp_delete_targetservergroup sp_delete_targetsvrgrp_member sp_enum_proxy_for_subsystem sp_enum_sqlagent_subsystems sp_grant_proxy_to_subsystem sp_help_alert sp_help_category sp_help_downloadlist sp_help_job sp_help_jobactivity sp_help_jobcount sp_help_jobhistory sp_help_jobs_in_schedule sp_help_jobschedule sp_help_jobserver sp_help_jobstep sp_help_jobsteplog 118

123 SQL Server Agent sp_help_notification sp_help_operator sp_help_proxy sp_help_schedule sp_help_targetserver sp_help_targetservergroup sp_manage_jobs_by_login sp_msx_defect sp_msx_enlist sp_msx_get_account sp_msx_set_account sp_notify_operator sp_post_msx_operation sp_purge_jobhistory sp_resync_targetserver sp_remove_job_from_targetss sp_revoke_login_from_proxy sp_revoke_proxy_from_subsystem sp_start_job sp_stop_job sp_update_alert sp_update_category sp_update_job sp_update_jobschedule sp_update_jobstep sp_update_notification sp_update_operator sp_update_proxy sp_update_schedule 119

124 SQL Server Backup SQL Server Backup BACKUP BACKUP CERTIFICATE BACKUP MASTER KEY BACKUP SERVICE MAS- TER KEY RESTORE RESTORE FILELISTONLY RESTORE HEADERONLY RESTORE LABELONLY RESTORE MASTER KEY RESTORE REWINDONLY RESTORE SERVICE MASTER KEY RESTORE VERIFYONLY sp_update_targetservergroup T-SQL BACKUP and RESTORE BACKUP and RESTORE Statements Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) 120

125 T-SQL Collation Collation Issue 7646: PostgreSQL doesn't support the COLLATE option in the ORDER BY clause. Automatic conversion can't be performed (p. 141) Control-of-Flow Language BEGIN...END BREAK CONTINUE GOTO IF...ELSE RETURN THROW TRY...CATCH WAITFOR WHILE Issue 7628: PostgreSQL doesn't support the GOTO option. Automatic conversion can't be performed (p. 132) Issue 7691: PostgreSQL doesn't support WAITFOR TIME feature (p. 133) Cursors DECLARE CURSOR DECLARE CURSOR CURSOR with option GLOBAL CURSOR with options FORWARD_ONLY or SCROLL Issue 7637: PostgreSQL doesn't support GLOBAL CURS- ORS. Requires manual Conversion (p. 133) 121

126 Microsoft SQL Server to PostgreSQL Conversion Issue Reference FETCH FETCH OPEN OPEN DUMP and LOAD Statements DUMP and LOAD Statements Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Microsoft SQL Server to PostgreSQL Conversion Issue Reference Use the following sections to get information on the types of issues you might encounter during a Microsoft SQL Server to PostgreSQL conversion. Click on the link in the Issue column to get more detailed resolution information about the issue if it is available. Arithmetic operators Item Arithmetic operators Arithmetic operators & date types Arithmetic operators & mixed types Issue Issue 7775: Check the data type conversion for possible loss of accuracy (p. 130) Issue 7773: Unable to perform an automated migration of arithmetic operations with dates (p. 131) Issue 7774: Unable to perform an automated migration of the arithmetic operations with mixed types of operands (p. 131) Resolution Cast values as the intended type. Cast values as the intended type. Cast values as the intended type. 122

127 Microsoft SQL Server to PostgreSQL Conversion Issue Reference BUILT-IN SERVICES Item Database Mail Service Broker SQL Server Agent SQL Server Backup Issue Issue 7900: PostgreSQL does not have functionality similar to SQL Server Database Mail (p. 131) Issue 7901: PostgreSQL does not have functionality similar to SQL Server Service Broker (p. 131) Issue 7902: PostgreSQL does not have functionality similar to SQL Server Agent (p. 131) Issue 7903: PostgreSQL does not have functionality similar to SQL Server Backup (p. 132) Resolution Try using the Amazon Simple tification Service (SNS). Try using the Amazon Simple Queue Service (SQS). Try using the AWS Lambda Service with Scheduled Events. Try using the Amazon Glacier storage service. BUILT-IN SQL FUNCTIONS Item SOUNDEX Issue Issue 7811: PostgreSQL doesn't support the SOUNDEX function (p. 132) Resolution Create a user-defined function. CONTROL FLOW Item Cursors DECLARE / DE- FAULT VALUE GOTO Procedures Result sets WAITFOR DELAY WAITFOR TIME Issue Issue 7801: The table can be locked open cursor (p. 132) Issue 7826: Check the default value for a DateTime variable (p. 132) Issue 7628: PostgreSQL doesn't support the GOTO option. Automatic conversion can't be performed (p. 132) Issue 7802: A table that is created within the procedure, must be deleted before the end of the procedure (p. 132) Issue 7800: PostgreSQL doesn't support result sets in the style of MSSQL (p. 132) Issue 7821: Automatic conversion operator WAITFOR with a variable is not supported (p. 133) Issue 7691: PostgreSQL doesn't support WAITFOR TIME feature (p. 133) Resolution Review your transformed code and modify it if necessary. Check the default value for a DateTime variable. Revise your code to eliminate GOTO operators, using BE- GIN...END blocks in combination with EXIT, REPEAT, UN- TIL, and WHILE operators. Review your transformed code and modify it if necessary. Review your transformed code and modify it if necessary. Perform a manual conversion. Perform a manual conversion. 123

128 Microsoft SQL Server to PostgreSQL Conversion Issue Reference CREATE Item Encrypted Objects Issue Issue 7696: Unable convert object due to %s not created (p. 133) Issue 7813: Encrypted Objects (p. 133) Resolution Please review the %s object. Decrypt the object before conversion. CURSORS Item CURSOR with option GLOBAL CURSOR with options STATIC or KEYSET or DYNAMIC or FAST_FORWARD FAST_FORWARD option FOR UPDATE KEYSET option OPTIMISTIC option READ_ONLY option TYPE_WARNING option Issue Issue 7637: PostgreSQL doesn't support GLOBAL CURSORS. Requires manual Conversion (p. 133) Issue 7639: PostgreSQL doesn't support DY- NAMIC cursors (p. 133) Issue 7701: Setting this option corresponds to the typical behavior of cursors in PostgreSQL, so this option is skipped (p. 133) Issue 7803: PostgreSQL doesn't support the option FOR UPDATE, so this option is skipped (p. 134) Issue 7700: The membership and order of rows never changes for cursors in PostgreSQL, so this option is skipped (p. 134) Issue 7704: PostgreSQL doesn't support the option OPTIMISTIC, so this option is skipped (p. 134) Issue 7702: All PostgreSQL cursors are readonly, so this option is skipped (p. 134) Issue 7705: PostgreSQL doesn't support the option TYPE_WARNING, so this option is skipped (p. 134) Resolution Change the global cursor to a local cursor, or revise your code so it doesn't require global cursors. Revise your code to eliminate dynamic cursors. Use cursors without this option. Review your transformed code and modify it if necessary. Use cursors without this option. Use cursors without this option. Use cursors without this option. Use cursors without this option. DATATYPES Item BYTEA Issue Issue 7818: PostgreSQL doesn't support arithmetic operations with binary data types (p. 134) Resolution Perform a manual conversion. 124

129 Microsoft SQL Server to PostgreSQL Conversion Issue Reference Item geography geometry hierarchyid rowversion sql_variant table UDT XML XML Issue Issue 7662: PostgreSQL doesn't support this type. A manual conversion is required (p. 134) Issue 7664: PostgreSQL doesn't support this type. A manual conversion is required (p. 134) Issue 7657: PostgreSQL doesn't support this type. A manual conversion is required (p. 135) Issue 7706: PostgreSQL doesn't support this type (p. 135) Issue 7658: PostgreSQL doesn't support this type. A manual conversion is required (p. 135) Issue 7659: The scope table-variables and temporary tables is different. You must apply manual conversion, if you are using recursion (p. 135) Issue 7690: PostgreSQL doesn't support table types (p. 135) Issue 7816: PostgreSQL doesn't support any methods for data type XML (p. 135) Issue 7817: PostgreSQL doesn't support option [for xml path] in the SQL-queries (p. 135) Resolution To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. Perform a manual conversion. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. Perform a manual conversion. Perform a manual conversion. Perform a manual conversion. Perform a manual conversion. DDL Item CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX Issue Issue 7675: PostgreSQL doesn't support sorting options (ASC DESC) for constraints (p. 136) Issue 7681: PostgreSQL doesn't support clustered indexes (p. 136) Issue 7682: PostgreSQL doesn't support the INCLUDE option in indexes (p. 136) Issue 7781: PostgreSQL doesn't support the PAD_INDEX option in indexes (p. 136) Issue 7782: PostgreSQL doesn't support the SORT_IN_TEMPDB option in indexes (p. 136) Resolution Use indexes without this option. Use non-clustered indexes. Use index without this option. Use index without this option. Use index without this option. 125

130 Microsoft SQL Server to PostgreSQL Conversion Issue Reference Item CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX CREATE INDEX CREATE TABLE CREATE TABLE CREATE TABLE CREATE TABLE Inline Function Issue Issue 7783: PostgreSQL doesn't support the IGNORE_DUP_KEY option in indexes (p. 136) Issue 7784: PostgreSQL doesn't support the STATISTICS_NORECOMPUTE option in indexes (p. 136) Issue 7785: PostgreSQL doesn't support the STATISTICS_INCREMENTAL option in indexes (p. 136) Issue 7786: PostgreSQL doesn't support the DROP_EXISTING option in indexes (p. 136) Issue 7787: PostgreSQL doesn't support the ONLINE option in indexes (p. 136) Issue 7788: PostgreSQL doesn't support the ALLOW_ROW_LOCKS option in indexes (p. 137) Issue 7789: PostgreSQL doesn't support the ALLOW_PAGE_LOCKS option in indexes (p. 137) Issue 7790: PostgreSQL doesn't support the MAXDOP option in indexes (p. 137) Issue 7791: PostgreSQL doesn't support the DATA_COMPRESSION option in indexes (p. 137) Issue 7679: PostgreSQL doesn't support computed columns (p. 137) Issue 7680: PostgreSQL doesn't support global temporary tables (p. 137) Issue 7812: Temporary table must be removed before the end of the function (p. 137) Issue 7825: The default value for a DateTime column removed (p. 137) Issue 7776: Automatic migration of inline functions not supported (p. 137) Resolution Use index without this option. Use index without this option. Use index without this option. Use index without this option. Use index without this option. Use index without this option. Use index without this option. Use index without this option. Use index without this option. Try using a trigger. Use local temporary or regular tables. Review your transformed code and modify it if necessary. Please review generated code and modify it if necessary. Perform a manual conversion. DELETE Item DELETE with Table Hint Limited Issue Issue 7623: PostgreSQL doesn't support hints in DELETE statements. The conversion skips options in the format WITH(Table_Hint_Limited) (p. 137) Resolution Use PostgreSQL methods for performance tuning. 126

131 Microsoft SQL Server to PostgreSQL Conversion Issue Reference Item TOP Issue Issue 7798: PostgreSQL doesn't support TOP option in the operator DELETE (p. 138) Resolution Perform a manual conversion. DML, FROM Item Table Hints Issue Issue 7823: PostgreSQL doesn't support table hints in DML statements (p. 138) Resolution Use PostgreSQL methods of performance tuning. EXECUTE Item EXECUTE a character string Execute a passthrough command against a linked server EXECUTE with execute options [RE- COMPILE] EXECUTE with execute options [RES- ULT SETS (<result_sets_definition>)] EXECUTE with execute options [RES- ULT SETS NONE] EXECUTE with execute options [RES- ULT SETS UN- DEFINED] Issue Issue 7695: PostgreSQL doesn't support the execution of a procedure as a variable (p. 138) Issue 7672: Automatic conversion of this command is not supported (p. 138) Issue 7645: PostgreSQL doesn't support executing a pass-through command on a linked server (p. 139) Issue 7640: The EXECUTE with RECOMPILE option is ignored (p. 139) Issue 7643: The EXECUTE with RESULT SETS <result set definition> option is ignored (p. 139) Issue 7642: The EXECUTE with RESULT SETS NONE option is ignored (p. 139) Issue 7641: The EXECUTE with RESULT SETS UNDEFINED option is ignored (p. 139) Resolution Perform a manual conversion using dynamic SQL. Perform a manual conversion. Use other methods to execute statements on a remote server. Use EXECUTE command without this option. Use EXECUTE command without this option. Use EXECUTE command without this option. Use EXECUTE command without this option. INSERT Item EXECUTE TOP Issue Issue 7819: PostgreSQL doesn't support IN- SERT...EXECUTE statements (p. 139) Issue 7799: PostgreSQL doesn't support TOP option in the operator INSERT (p. 139) Resolution Perform a manual conversion. Perform a manual conversion. 127

132 Operators AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Item Bitwise Operators Comparison Operators Comparison Operators Issue Issue 7804: PostgreSQL doesn't support operator [Bitwise exclusive OR] (p. 140) Issue 7805: PostgreSQL doesn't support operator [t less than] (p. 140) Issue 7806: PostgreSQL doesn't support operator [t greater than] (p. 140) Resolution Perform a manual conversion. Perform a manual conversion. Perform a manual conversion. Parser Error Item Parser Error Issue Issue 7663: Unable to resolve the object (p. 140) Resolution Verify if object <object name> is present in the database. If it isn't, check the object name or add the object. If the object is present, transform the code manually. SELECT Item GROUP BY CUBE GROUP BY CUBE Group By Grouping Sets ORDER BY Specifying a collation search condition search condition search condition TOP WITH TIES Issue Issue 7653: PostgreSQL doesn't support the option GROUP BY ROLLUP. Automatic conversion can't be performed (p. 141) Issue 7654: PostgreSQL doesn't support the option GROUP BY CUBE. Automatic conversion can't be performed (p. 141) Issue 7655: PostgreSQL doesn't support the option GROUP BY GROUPING SETS. Automatic conversion can't be performed (p. 141) Issue 7646: PostgreSQL doesn't support the COLLATE option in the ORDER BY clause. Automatic conversion can't be performed (p. 141) Issue 7687: PostgreSQL doesn't support the CONTAINS predicate (p. 141) Issue 7688: PostgreSQL doesn't support the FREETEXT predicate (p. 141) Issue 7795: PostgreSQL is case sensitive. Check the string comparison (p. 141) Issue 7605: PostgreSQL doesn't support the WITH TIES option (p. 141) Resolution Try creating a stored procedure to replace the query. Try creating a stored procedure to replace the query. Try creating a stored procedure to replace the query. You must use the COLLATION settings that were assigned when the database was created. Perform a manual conversion. Perform a manual conversion. Check the string comparison. Perform a manual conversion. 128

133 SEQUENCE AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Item Specific data type Issue Issue 7793: PostgreSQL doesn't support changing data type in sequences (p. 142) Resolution Review your transformed code and modify it if necessary. SYNONYMS Item CREATE Issue Issue 7792: PostgreSQL doesn't support synonyms (p. 142) Resolution Replace a synonym with original database object. If original object is table or view you can try to create a view in one database that relies on a table or view in another database. SYS objects Item SYS objects Issue Issue 7904: Unable to convert system object <object name> (p. 142) Resolution Perform a manual conversion. TRANSACTION Item Transaction Issue Issue 7807: Transactions in functions PostgreSQL doesn't support (p. 142) Resolution Perform a manual conversion. TRIGGERS Item Triggers Issue Issue 7809: In PostgreSQL there are no analogues of the tables 'inserted' and 'deleted' (p. 143) Resolution Perform a manual conversion. Unknown Item Issue Issue 7627: This syntactic element conversion is not supported yet (p. 144) Resolution Perform a manual conversion. 129

134 Microsoft SQL Server to PostgreSQL Conversion Issue Reference Item Unknown Unparsed SQL Issue Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported (p. 144) Issue 7808: Unparsed SQL (p. 144) Resolution Perform a manual conversion. Perform a manual conversion. UPDATE Item TOP UPDATE Variable assignment Issue Issue 7796: PostgreSQL doesn't support TOP option in the operator UPDATE (p. 144) Issue 7797: PostgreSQL doesn't have analog for option "OUTPUT" with using the implicit table "deleted" in the operator for UP- DATE (p. 145) Issue 7829: Unable to convert variable assignment by UPDATE statement (p. 146) Resolution Perform a manual conversion. This case requires manual conversion. Perform a manual conversion. User types Item User-Defined Data Types Issue Issue 7794: PostgreSQL doesn't support userdefined data types (p. 146) Resolution Perform a manual conversion. Conversion Issues with Arithmetic operators Issue 7775: Check the data type conversion for possible loss of accuracy To avoid loss of accuracy for types in arithmetic operations, cast values as the intended type, for example: BEGIN SELECT 5.1E+1::REAL INTO lbinaryfloat; SELECT - 5.2E-1::DOUBLE PRECISION INTO lbinarydouble; var1 := (var_varchar1 var_varchar2)::integer; var2 := (var_varchar1 var_varchar3)::numeric; var3 := var_varchar1::numeric + var_numeric2; var4 := var_timestamp2 + (var_numeric1::numeric 'day')::interval; END; 130

135 Microsoft SQL Server to PostgreSQL Conversion Issue Reference Issue 7773: Unable to perform an automated migration of arithmetic operations with dates The Schema Conversion Tool cannot automatically migrate arithmetic operations that use date types. Cast values as the intended type, for example: BEGIN var3 := var_varchar1::numeric + var_numeric2; var4 := var_timestamp2 + (var_numeric1::numeric 'day')::interval; END; Issue 7774: Unable to perform an automated migration of the arithmetic operations with mixed types of operands The Schema Conversion Tool cannot automatically migrate arithmetic operations that mix types. For example, multiplying a variable of type FLOAT with a variable of type INT. Cast values as the intended type before performing any arithmetic operations, for example: BEGIN var1 := (var_varchar1 var_varchar2)::integer; var2 := (var_varchar1 var_varchar3)::numeric; END; Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with BUILT-IN SERVICES Issue 7900: PostgreSQL does not have functionality similar to SQL Server Database Mail Try using the Amazon Simple tification Service (SNS). For more information, see Getting Started with Amazon Simple tification Service. Issue 7901: PostgreSQL does not have functionality similar to SQL Server Service Broker Try using the Amazon Simple Queue Service (SQS). For more information, see Introduction to Amazon SQS. Issue 7902: PostgreSQL does not have functionality similar to SQL Server Agent Try using the AWS Lambda Service with Scheduled Events. For more information, see What Is AWS Lambda?. 131

136 Issue 7903: PostgreSQL does not have functionality similar to SQL Server Backup Try using the Amazon Glacier storage service. For more information, see What Is Amazon Glacier?. Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with BUILT-IN SQL FUNCTIONS Issue 7811: PostgreSQL doesn't support the SOUNDEX function Create a user-defined function. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with CONTROL FLOW Issue 7800: PostgreSQL doesn't support result sets in the style of MSSQL Review your transformed code and modify it if necessary. Issue 7801: The table can be locked open cursor In Microsoft SQL Server, a local temporary table created in a stored procedure is dropped automatically when the stored procedure completes. Temporary tables in PostgreSQL are automatically dropped at the end of a session. The conversion uses the DROP TABLE IF EXISTS statement to emulate this behavior and remove the temporary table before the end of the function that created it. In some cases though, this statement might fail because the temporary table is locked due to an open cursor. In this case, the DROP TABLE statement must be commented out. Review your transformed code and modify it if necessary. Issue 7802: A table that is created within the procedure, must be deleted before the end of the procedure Review your transformed code and modify it if necessary. Issue 7826: Check the default value for a DateTime variable Check the default value for a DateTime variable. Issue 7628: PostgreSQL doesn't support the GOTO option. Automatic conversion can't be performed Revise your code to eliminate GOTO operators, using BEGIN...END blocks in combination with EXIT, REPEAT, UNTIL, and WHILE operators. 132

137 Issue 7821: Automatic conversion operator WAITFOR with a variable is not supported You must perform a manual conversion in cases where you have a WAITFOR DELAY statement that uses a variable, for example WAITFOR instead of a literal value, for example WAITFOR DELAY '00:00:05';. Issue 7691: PostgreSQL doesn't support WAITFOR TIME feature Perform a manual conversion. Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with CREATE Issue 7696: Unable convert object due to %s not created Review the <object name> object. Issue 7813: Encrypted Objects Decrypt the object before conversion. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with CURSORS Issue 7637: PostgreSQL doesn't support GLOBAL CURSORS. Requires manual Conversion Change the global cursor to a local cursor, or revise your code so it doesn't require global cursors. Issue 7639: PostgreSQL doesn't support DYNAMIC cursors Revise your code to remove the DYNAMIC option from any cursors. Issue 7701: Setting this option corresponds to the typical behavior of cursors in PostgreSQL, so this option is skipped The FAST_FORWARD option is skipped during conversion, because PostgreSQL cursors provide the same behavior as the FAST_FORWARD option by default. Review your transformed code and modify it if necessary. 133

138 Issue 7803: PostgreSQL doesn't support the option FOR UPDATE, so this option is skipped The FOR_UPDATE option is skipped during conversion because PostgreSQL doesn't support it. Review your transformed code and modify it if necessary. Issue 7700: The membership and order of rows never changes for cursors in PostgreSQL, so this option is skipped Use cursors without this option. Issue 7704: PostgreSQL doesn't support the option OPTIMISTIC, so this option is skipped Use cursors without this option. Issue 7702: All PostgreSQL cursors are read-only, so this option is skipped Use cursors without this option. Issue 7705: PostgreSQL doesn't support the option TYPE_WARNING, so this option is skipped Use cursors without this option. Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with DATATYPES Issue 7818: PostgreSQL doesn't support arithmetic operations with binary data types Perform a manual conversion. Issue 7662: PostgreSQL doesn't support this type. A manual conversion is required PostgreSQL doesn't support the geography data type. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. Issue 7664: PostgreSQL doesn't support this type. A manual conversion is required PostgreSQL doesn't support the geometry data type. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. 134

139 Issue 7657: PostgreSQL doesn't support this type. A manual conversion is required PostgreSQL doesn't support the hierarchyid data type. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. Issue 7706: PostgreSQL doesn't support this type PostgreSQL doesn't support the rowversion data type. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type. Issue 7658: PostgreSQL doesn't support this type. A manual conversion is required PostgreSQL doesn't support the sql_variant data type. To store data of this type in PostgreSQL, use a PostgreSQL-compatible type or use a composite type. Issue 7659: The scope table-variables and temporary tables is different. You must apply manual conversion, if you are using recursion Perform a manual conversion. AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Issue 7690: PostgreSQL doesn't support table types PostgreSQL doesn t support table parameters in CREATE PROCEDURE statements, for example: CREATE TYPE Employee2Client AS TABLE( EmployeeID int, EmployeeName varchar(160), ClientID int, ClientName varchar(160) ) go CREATE PROCEDURE Employee2Client READONLY AS BEGIN select * where upper(clientname) like concat('%', upper('bank'), '%') ; Convert to temporary tables or row variables (for example, name table_name%rowtype;). Issue 7816: PostgreSQL doesn't support any methods for data type XML Microsoft SQL Server provides methods for the xml data type that you can use to read and manipulate XML data, but PostgreSQL's xml data type does not offer parallel functionality. Perform a manual conversion to use PostgreSQL XML handling functionality instead. Issue 7817: PostgreSQL doesn't support option [for xml path] in the SQL-queries PostgreSQL doesn't support using the FOR XML clause in PATH mode for DML statements. Perform a manual conversion to use PostgreSQL XML handling functionality instead. 135

140 Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with DDL Issue 7675: PostgreSQL doesn't support sorting options (ASC DESC) for constraints Remove these options from indexes and constraints. Issue 7681: PostgreSQL doesn't support clustered indexes Use non-clustered indexes. Issue 7682: PostgreSQL doesn't support the INCLUDE option in indexes Use the index without this option. Issue 7781: PostgreSQL doesn't support the PAD_INDEX option in indexes Use the index without this option. Issue 7782: PostgreSQL doesn't support the SORT_IN_TEMPDB option in indexes Use the index without this option. Issue 7783: PostgreSQL doesn't support the IGNORE_DUP_KEY option in indexes Use the index without this option. Issue 7784: PostgreSQL doesn't support the STATISTICS_NORECOMPUTE option in indexes Use the index without this option. Issue 7785: PostgreSQL doesn't support the STATISTICS_INCREMENTAL option in indexes Use the index without this option. Issue 7786: PostgreSQL doesn't support the DROP_EXISTING option in indexes Use the index without this option. Issue 7787: PostgreSQL doesn't support the ONLINE option in indexes Use the index without this option. 136

141 Issue 7788: PostgreSQL doesn't support the ALLOW_ROW_LOCKS option in indexes Use index without this option. Issue 7789: PostgreSQL doesn't support the ALLOW_PAGE_LOCKS option in indexes Use index without this option. Issue 7790: PostgreSQL doesn't support the MAXDOP option in indexes Use index without this option. Issue 7791: PostgreSQL doesn't support the DATA_COMPRESSION option in indexes Use index without this option. Issue 7679: PostgreSQL doesn't support computed columns Try using a trigger instead. Issue 7680: PostgreSQL doesn't support global temporary tables Use local temporary or regular tables. Issue 7812:Temporary table must be removed before the end of the function Review your transformed code and modify it if necessary. Issue 7825: The default value for a DateTime column removed Please review generated code and modify it if necessary. Issue 7776: Automatic migration of inline functions not supported Perform a manual conversion. Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with DELETE Issue 7623: PostgreSQL doesn't support hints in DELETE statements. The conversion skips options in the format WITH(Table_Hint_Limited) PostgreSQL doesn't support usings hints (for example, WITH FORCESCAN) to override the default behavior of the query optimizer when executing Data Manipulation Language (DML) statements. Use PostgreSQL methods for performance tuning instead. 137

142 Microsoft SQL Server to PostgreSQL Conversion Issue Reference Issue 7798: PostgreSQL doesn't support TOP option in the operator DELETE Perform a manual conversion for any DELETE statements that contain a TOP argument, for example: delete top (<expression >)[PERCENT] from <table-name>; In PostgreSQL, you can use a subquery in the WHERE clause to identify the rows you want to delete. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with DML, FROM Issue 7823: PostgreSQL doesn't support table hints in DML statements PostgreSQL doesn't support usings hints (for example, WITH FORCESCAN) to override the default behavior of the query optimizer when executing Data Manipulation Language (DML) statements. Use PostgreSQL methods of performance tuning instead. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with EXECUTE Issue 7695: PostgreSQL doesn't support the execution of a procedure as a variable Perform a manual conversion (one possibility is to use dynamic SQL). This issue occurs when you pass in the name of a procedure to an EXECUTE statement by using a variable, for example: ALTER PROCEDURE [dbo].[proc_execute_009] AS SET NOCOUNT ON BEGIN int; varchar(20) = output Issue 7672: Automatic conversion of this command is not supported This issue is often caused by an EXECUTE statement that executes a string or variable, for example EXEC('select * from Customer'); or EXEC(@variable);. Convert each of these statements to a pair of PREPARE and EXECUTE statements in PostgreSQL. 138

143 Issue 7645: PostgreSQL doesn't support executing a pass-through command on a linked server Use other methods to execute statements on a remote server. Issue 7640: The EXECUTE with RECOMPILE option is ignored Use the EXECUTE command without this option. Issue 7643:The EXECUTE with RESULT SETS <result set definition> option is ignored Use the EXECUTE command without this option. Issue 7642: The EXECUTE with RESULT SETS NONE option is ignored Use the EXECUTE command without this option. Issue 7641:The EXECUTE with RESULT SETS UNDEFINED option is ignored Use the EXECUTE command without this option. Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with INSERT Issue 7819: PostgreSQL doesn't support INSERT...EXECUTE statements Perform a manual conversion. PostgreSQL doesn't support using EXECUTE within an INSERT statement to insert the results of a stored procedure into a table. Issue 7799: PostgreSQL doesn't support TOP option in the operator INSERT Perform a manual conversion for any INSERT statements that contain a TOP argument, for example: insert TOP(2) percent into Customer( id,sname,name,typeid,taxcode,stateid,opendate,closedate )select id+1000,name,name,4,61+id,1 139

144 Microsoft SQL Server to PostgreSQL Conversion Issue Reference,getdate(),null from employees e where name not in(select name from Customer) and exists(select 1 from Employees where ManagerId = e.id) In PostgreSQL, you can use the row_number() window function in the FROM clause or a subquery in the WHERE clause of the SELECT statement you use to select the data to be inserted to identify the rows you want to insert. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with Operators Issue 7804: PostgreSQL doesn't support operator [Bitwise exclusive OR] Perform a manual conversion. Issue 7805: PostgreSQL doesn't support operator [t less than] Perform a manual conversion. Issue 7806: PostgreSQL doesn't support operator [t greater than] Perform a manual conversion. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with Parser Error Issue 7663: Unable to resolve the object Verify if object <object name> is present in the database. If it isn't, check the object name or add the object. If the object is present, transform the code manually. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) 140

145 Conversion Issues with SELECT Issue 7653: PostgreSQL doesn't support the option GROUP BY ROLLUP. Automatic conversion can't be performed Try creating a stored procedure to replace the query. Issue 7654: PostgreSQL doesn't support the option GROUP BY CUBE. Automatic conversion can't be performed Try creating a stored procedure to replace the query. Issue 7655: PostgreSQL doesn't support the option GROUP BY GROUPING SETS. Automatic conversion can't be performed Try creating a stored procedure to replace the query. Issue 7646: PostgreSQL doesn't support the COLLATE option in the ORDER BY clause. Automatic conversion can't be performed You must use the collation settings that were assigned when the database was created. Issue 7687: PostgreSQL doesn't support the CONTAINS predicate Perform a manual conversion by re-writing the SELECT statement to use PostgreSQL full-text search functionality instead. For more information about full-text search in PostgreSQL, see Tables and Indexes in the PostgreSQL documentation. Issue 7688: PostgreSQL doesn't support the FREETEXT predicate Perform a manual conversion by re-writing the SELECT statement to use PostgreSQL full-text search functionality instead. For more information about full-text search in PostgreSQL, see Tables and Indexes in the PostgreSQL documentation. Issue 7795: PostgreSQL is case sensitive. Check the string comparison Check string comparisons in the WHERE clauses of statements, for example WHERE [Name] LIKE '%BLOCKED%';. All strings used in comparisons must be lowercase. Issue 7605: PostgreSQL doesn't support the WITH TIES option Perform a manual conversion of any TOP statements that use the WITH TIES clause. You can use the rank() window function in PostgreSQL to provide similar results. Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) 141

146 Conversion Issues with SEQUENCE Issue 7793: PostgreSQL doesn't support changing data type in sequences PostgreSQL doesn't support setting a sequence's data type by using the AS clause of the CREATE SEQUENCE statement. Review your transformed code and modify it if necessary. Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with SYNONYMS Issue 7792: PostgreSQL doesn't support synonyms PostgreSQL doesn't support the CREATE SYNONYM statement. To convert, replace the synonym in any statement with the original database object. If the original object is a table or view, you can try to create a view in one database that relies on a table or view in another database. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with SYS objects Issue 7904: Unable to convert system object <object name> Perform a manual conversion. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with TRANSACTION Issue 7807: Transactions in functions PostgreSQL doesn't support Perform a manual conversion to correct this issue. PostgreSQL supports local transactions within a given client session.you must manually convert Microsoft SQL Server transactions to use the PostgreSQL transaction management statements instead. PostgreSQL doesn't support named or distributed transactions, marking transactions, or transaction management within functions. For more information about using transactions in PostgreSQL, see TRANSACTIONS in the PostgreSQL documentation. 142

147 Related Topics AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with TRIGGERS Issue 7809: In PostgreSQL there are no analogues of the tables 'inserted' and 'deleted' PostgreSQL doesn't support the inserted or deleted virtual tables. To manually convert a trigger that uses these tables from Microsoft SQL Server to PostgreSQL, perform the following steps: 1. Create a trigger function. The trigger function must be declared as a function taking no arguments and returning type trigger. The returned value must be NEW, OLD or NULL, depending on the type of a trigger. The function s body must be PostgreSQL-supported SQL to replace the body of the Microsoft SQL Server trigger without using the virtual tables. The name of the function should be formed as schema_name.fn_<%trigger_name%>(). 2. Create a trigger with CREATE TRIGGER that executes the trigger function. For example, the following Microsoft SQL Server trigger: CREATE TRIGGER [dbo].[tr_customerstateext_aiu] ON [dbo].[customerstateext] AFTER INSERT, UPDATE AS BEGIN IF EXISTS (SELECT * FROM inserted WHERE LEN(Name) < 5) BEGIN RAISERROR ('The name must be longer than five characters.', 16, 1); ROLLBACK TRANSACTION; RETURN END; END GO Would be converted into the following PostgreSQL trigger: CREATE OR REPLACE FUNCTION mydb_dbo.fn_tr_customerstateext_aiu() RETURNS trigger AS $BODY$ BEGIN <SQL to write around use of the inserted and deleted virtual tables> END; $BODY$ LANGUAGE plpgsql; CREATE TRIGGER tr_customerstateext_aiu AFTER INSERT OR UPDATE 143

148 Microsoft SQL Server to PostgreSQL Conversion Issue Reference ON mydb_dbo.customerstateext FOR EACH STATEMENT EXECUTE PROCEDURE mydb_dbo.fn_tr_customerstateext_aiu(); Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with Unknown Issue 7627: This syntactic element conversion is not supported yet Perform a manual conversion. Issue 7674: Automatic conversion of <clause name> clause of <statement name> statement is not supported Perform a manual conversion to correct this issue. A common cause of this issue is SET statements in Microsoft SQL Server that affect current session handling (a complete list of these SET statements is available at SET Statements (Transact-SQL)). These statements are not supported in PostgreSQL, so you need to perform a manual conversion to a PostgreSQL SET statement. For more information about using a SET statement in PostgreSQL, see SET in the PostgreSQL documentation. Issue 7808: Unparsed SQL Perform a manual conversion. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with UPDATE Issue 7796: PostgreSQL doesn't support TOP option in the operator UPDATE Perform a manual conversion for any UPDATE statements that contain a TOP argument, for example: update top(10) Account set AccountBalance = AccountBalance - 1 where AccountBalance > ; or: 144

149 Microsoft SQL Server to PostgreSQL Conversion Issue Reference update top(5) percent Account set AccountBalance = AccountBalance - 1 where AccountBalance > ; In PostgreSQL, you can use the row_number() window function in the FROM clause or a subquery in the WHERE clause of the UPDATE statement to identify the rows you want to modify. Issue 7797: PostgreSQL doesn't have analog for option "OUTPUT" with using the implicit table "deleted" in the operator for UPDATE Perform a manual conversion for any UPDATE statements that uses the OUTPUT clause and references the deleted virtual table, for example: update Customer set name = 'Mister ' + name output deleted.id, deleted.name, inserted.id, inserted.name where TypeID = 4 In PostgreSQL, use a subquery in the RETURNING clause to return the information about the deleted table. This approach requires the table to have a primary key field. update mydb_dbo.customer c set name = 'Mister ' name where TypeID = 4 returning (select id from mydb_dbo.customer where id = c.id),(select name from mydb_dbo.customer where id = c.id),id,name If the primary key is composed of multiple fields, you must reference all of those fields in the subquery. For example, given the following statement in SQL Server where id1 and id2 are the primary key fields for the TestMultiPK table: UPDATE [TestMultiPK] SET [Description] = 'Test' output deleted.id1, deleted.id2, deleted.description, inserted.id1, inserted.id2, inserted.description where ID = 0 145

150 The PostgreSQL conversion is: AWS Schema Conversion Tool User Guide Microsoft SQL Server to PostgreSQL Conversion Issue Reference UPDATE [TestMultiPK] t SET [Description] = 'Test' WHERE ID = 0 returning select (id1 from TestMultiPK where id1 = t.id1 and id2 = t.id2), select (id2 from TestMultiPK where id1 = t.id1 and id2 = t.id2), select (Description from TestMultiPK where id1 = t.id1 and id2 = t.id2), id1, id2, Description Issue 7829: Unable to convert variable assignment by UPDATE statement Perform a manual conversion. This issue occurs when you use an UPDATE statement to change the value of a variable, for example: CREATE PROCEDURE [dbo].[proc_dml_update_from_3] AS BEGIN FLOAT = 400; UPDATE bank = 500 FROM bank WHERE id = 50005; END Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Conversion Issues with User types Issue 7794: PostgreSQL doesn't support user-defined data types To correct this issue, perform a manual conversion of each sp_ addtype or CREATE TYPE statement in Microsoft SQL Server to a CREATE TYPE statement in PostgreSQL. For more information about creating a user-defined data type in PostgreSQL, see CREATE TYPE in the PostgreSQL documentation. Related Topics Microsoft SQL Server to PostgreSQL Conversion Issue Reference (p. 122) AWS Schema Conversion Tool Reference (p. 61) What Is the AWS Schema Conversion Tool? (p. 1) Related Topics AWS Schema Conversion Tool Reference (p. 61) 146

151 SQL Server to MySQL Supported Schema Conversion What Is the AWS Schema Conversion Tool? (p. 1) SQL Server to MySQL Supported Schema Conversion The following sections list the schema elements from Microsoft SQL Server and whether they are supported for automatic conversion to MySQL using the AWS Schema Conversion Tool. Topics Statements (p. 147) Procedures (p. 150) Flow Control (p. 151) Functions (p. 152) Operators (p. 159) Transactions (p. 162) Data Types (p. 163) Data Definition Language (DDL) (p. 165) Cursors (p. 166) Related Topics (p. 167) Statements Topics SELECT (p. 147) INSERT (p. 148) UPDATE (p. 149) DELETE (p. 150) SELECT WITH UNION EXCEPT INTERSECT ALL DISTINCT TOP <select_list> Try converting the WITH(query) expression to a subquery and use it in a SELECT query. MySQL doesn't support TOP with the PERCENT or WITH TIES options. Try using the LIMIT option or perform a manual conversion. 147

152 Statements INTO FROM WHERE GROUP BY HAVING ORDER BY FOR OPTION MySQL doesn't support the CONTAINS and FREETEXT predicates in the FROM clause search condition. MySQL doesn't support ORDER BY with the ROLLUP, CUBE, and GROUPING SETS options.try creating a stored procedure to replace the query. MySQL doesn't support ORDER BY with the OFFSET or FETCH options. Try creating a stored procedure to replace the query. MySQL doesn't support ORDER BY with the COLLATE option. You must use the collation settings that were assigned when the database was created. INSERT WITH INSERT TOP INTO table_name WITH (<Table_Hint_Limited>) OUTPUT VALUES Try to convert the WITH query to a subquery, and then use the subquery in the INSERT query. Get a count of all rows, and then use the following expression, where count_of_all_rows is your row count: percent_expression * count_of_all_rows / 100 Use MySQL methods of performance tuning. Create a trigger for INSERT statements for the table, and then save the inserted rows in a temporary table. After the INSERT operation, you can make use of the rows saved in the temporary table. This logic can be placed in a stored procedure. 148

153 Statements derived_table execute_statement <dml_table_source> DEFAULT VALUES Create a temporary table, fill it with the data to insert, and use the temporary table in the query. UPDATE WITH TOP WITH (<Table_Hint_Limited>) SET OUTPUT FROM WHERE CURRENT OF GLOBAL OPTION Try to convert the WITH query to a subquery, and then use the subquery in the UPDATE query. MySQL doesn't support UPDATE with the PERCENT option. Get a count of all rows, and then use the following expression, where count_of_all_rows is your row count: percent_expression * count_of_all_rows / 100 Use MySQL methods of performance tuning. Create a trigger for UPDATE statements for the table, and then save the changed rows in a temporary table. After the UPDATE operation, you can make use of the rows saved in the temporary table. This logic can be placed in a stored procedure. MySQL doesn't support a FROM clause. AWS Schema Conversion Tool moves <table-source> to the UPDATE clause. Replace the CURRENT OF clause with an expression that consists of conditions that use unique key fields of the table. te MySQL doesn't support FILESTREAM DATA. Perform a manual conversion to update the data in the file system file. 149

154 Procedures DELETE WITH TOP FROM table_or_view_name rowset_function_limited WITH OUTPUT WHERE CURRENT OF GLOBAL OPTION Try to convert the WITH query to a subquery, and then use the subquery in the DELETE query. MySQL doesn't support the PERCENT option. A manual conversion is required. Get a count of all rows, and then use the following expression, where count_of_all_rows is your row count: percent_expression * count_of_all_rows / 100 MySQL doesn't support hints in DELETE statements, so the AWS Schema Conversion Tool skips options in the format WITH(Table_Hint_Limited). Use MySQL methods of performance tuning. Create a trigger for DELETE statements for the table, and then save the deleted rows in a temporary table. After the DELETE operation, you can make use of the rows saved in the temporary table. This logic can be placed in a stored procedure. Replace the CURRENT OF clause with an expression that consists of conditions that use unique key fields of the table. Procedures Topics CREATE PROCEDURE (p. 150) CREATE MySQL doesn't support procedure arguments of the CURSOR data type. Change the business logic to eliminate the need to send cursors through arguments to a stored procedure. 150

155 Flow Control VARYING OUT OUTPUT READONLY WITH FOR REPLICATION AS BEGIN END ENCRYPTION RECOMPILE EXECUTE AS Flow Control TRY CATCH THROW WAITFOR DECLARE GOTO BREAK CONTINUE IF ELSE RETURN WHILE CASE COALESCE NULLIF Try using the DECLARE HANDLER for the CATCH emulation block and the SIGNAL SQLSTATE operator to emulate the THROW operator. Perform a manual conversion. Perform a manual conversion. Revise your code to eliminate GOTO operators, using BE- GIN...END blocks in combination with LEAVE, REPEAT, UNTIL, and WHILE operators. MySQL does not support returning a value from a procedure using the RETURN statement. To return a value, use the OUT parameter or a result set. 151

156 Functions Functions Topics Aggregate Functions (p. 152) Date and Time Functions (p. 153) Mathematical Functions (p. 153) String Functions (p. 154) Configuration Functions (p. 155) Conversion Functions (p. 156) Security Functions (p. 156) System Functions (p. 157) Logical Functions (p. 158) CREATE FUNCTION (p. 158) EXECUTE (p. 159) This sections lists the Microsoft SQL Server built-in functions and indicates whether AWS Schema Conversion Tool performs an automatic conversion. Where MySQL doesn't support a function, consider creating a user-defined function. Aggregate Functions Function AVG COUNT COUNT_BIG MIN MAX SUM CHECKSUM_AGG STDEV STDEVP GROUPING GROUPING_ID VAR VARP MySQL doesn't support the STDEV function with the DIS- TINCT clause. MySQL doesn't support the STDEVP function with the DISTINCT clause. MySQL doesn't support the VAR function with the DISTINCT clause. MySQL doesn't support the VARP function with the DIS- TINCT clause. 152

157 Functions Date and Time Functions Function DATEADD DATEDIFF DATENAME DATEPART DAY GETDATE GETDATE + 1 GETUTCDATE MONTH YEAR DATETIMEOFFSET- FROMPARTS ISDATE SWITCHOFFSET SYSDATETIMEOFFSET TODATETIMEOFFSET MySQL doesn't support the DATEADD function with the nanosecond datepart. MySQL doesn't support the DATEDIFF function with the week, millisecond, or nanosecond datepart. MySQL doesn't support the DATENAME function with the millisecond, nanosecond, or TZoffset datepart. MySQL doesn't support the DATEPART function with the millisecond, nanosecond, or TZoffset datepart. Mathematical Functions Function ABS ACOS ASIN ATN2 ATAN CEILING COS 153

158 Functions Function COT DEGREES EXP FLOOR LOG10 LOG PI POWER RADIANS RAND ROUND SIGN SIN SQRT SQUARE TAN MySQL doesn't support the ROUND function with the function argument. String Functions Function ASCII CHAR CHARINDEX CONCAT DIFFERENCE FORMAT LEFT LEN LOWER 154

159 Functions Function LTRIM NCHAR PATINDEX QUOTENAME REPLACE REPLICATE REVERSE RIGHT RTRIM SOUNDEX SPACE STR STUFF SUBSTRING UNICODE UPPER Configuration Functions Function

160 Functions Function Conversion Functions Function CAST and CONVERT PARSE TRY_CAST TRY_CONVERT TRY_PARSE Security Functions Function CERTENCODED CERTPRIVATEKEY CURRENT_USER DATABASE_PRINCIP- AL_ID HAS_PERMS_BY_NAME IS_MEMBER IS_ROLEMEMBER IS_SRVROLEMEMBER ORIGINAL_LOGIN PERMISSIONS PWDCOMPARE 156

161 Functions Function PWDENCRYPT SCHEMA_ID SCHEMA_NAME SESSION_USER SUSER_ID SUSER_NAME SUSER_SID SUSER_SNAME sys.fn_builtin_permissions sys.fn_get_audit_file sys.fn_my_permissions SYSTEM_USER USER_ID USER_NAME System Functions Function $PARTITION BINARY_CHECKSUM CHECKSUM CONNECTIONPROPERTY CONTEXT_INFO CURRENT_REQUEST_ID ERROR_LINE 157

162 Functions Function ERROR_MESSAGE ERROR_NUMBER ERROR_PROCEDURE ERROR_SEVERITY ERROR_STATE FORMATMESSAGE GET_FILESTREAM_TRANS- ACTION_CONTEXT GETANSINULL HOST_ID HOST_NAME ISNULL MIN_ACTIVE_ROWVER- SION NEWID NEWSEQUENTIALID PARSENAME ROWCOUNT_BIG XACT_STATE Logical Functions Function CHOOSE IIF CREATE 158

163 Operators type_schema_name parameter_data_type = default READONLY RETURNS return_data_type WITH function_option BEGIN END MySQL supports only functions that return a scalar value. type_schema_name parameter_data_type = default READONLY RETURNS return_data_type WITH function_option BEGIN END RETURN scalar_expression RETURN scalar_expression MySQL supports only functions that return a scalar value. Operators Topics Arithmetic Operators (p. 160) Assignment Operator (p. 160) Bitwise Operators (p. 160) Comparison Operators (p. 161) Logical Operators (p. 161) 159

164 Operators Set Operators (p. 161) String Concatenation Operator (p. 162) Unary Operators (p. 162) Arithmetic Operators + += - -= * *= / /= % Assignment Operator = Bitwise Operators & ^ ~ 160

165 Operators Comparison Operators = > < >= <= <>!=!<!> Logical Operators ALL AND ANY BETWEEN EXISTS IN LIKE NOT OR SOME The AWS Schema Conversion Tool converts SOME to ANY. Set Operators UNION 161

166 Transactions UNION ALL EXCEPT INTERSECT Perform a manual conversion. Perform a manual conversion. String Concatenation Operator + Unary Operators + - Transactions Topics BEGIN TRANSACTION (p. 162) BEGIN TRANSACTION DISTRIBUTED transaction_name WITH MARK SAVE ROLLBACK MySQL doesn't support distributed transactions. Revise your architecture so that it doesn't use distributed transactions. MySQL doesn't support named transactions. Revise your code to eliminate marked transactions. MySQL doesn't support the WITH MARK option. Revise your code to eliminate marked transactions. 162

167 Data Types transaction_name savepoint_name COMMIT DELAYED_DURABILITY MySQL doesn't support named transactions. Revise your code to eliminate named transactions. Data Types Topics Numerics (p. 163) Date and Time (p. 164) Character Strings (p. 164) Binary Strings (p. 164) Special Types (p. 165) Numerics Data type Default Conversion bigint bigint int int smallint smallint tinyint tinyint unsigned bit bit(1) money numeric(19,4) smallmoney numeric(10,4) numeric numeric decimal decimal float double real float 163

168 Data Types Date and Time Data type Default Conversion date date through datetime2(7) datetime through :00:00 through 23:59: datetime datetime , through :00:00 through 23:59: datetimeoffset(7) smalldatetime datetime time(7) time Character Strings Data type Default Conversion char(len) char len= (2^8-1) symbols (loss range) varchar(len) varchar varchar(max) longtext text longtext nchar(len) len = char len= (2^8-1) symbols (loss range) nvarchar(len) varchar nvarchar(max) longtext ntext longtext Binary Strings Data type Default Conversion binary(len) blob varbinary(len) blob 164

169 Data Definition Language (DDL) Data type Default Conversion varbinary(max) longblob hierarchyid sql_variant table uniqueidentifier xml geography geometry Special Types Data type Default Conversion UNIQUEIDENTIFIER CHAR(38) OR BINARY(16) DOUBLE PRECISION FLOAT(53) IDENTITY AUTO_INCREMENT SYSNAME NVARCHAR(128) NOT NULL Data Definition Language (DDL) Topics CREATE TABLE (p. 165) CREATE INDEX (p. 166) CREATE TRIGGER (p. 166) CREATE VIEW (p. 166) CREATE TABLE CREATE TABLE statements are converted automatically except for the following clause: SET DEFAULT MySQL doesn't support the SET DEFAULT option for FOREIGN KEY. 165

170 Cursors CREATE INDEX The AWS Schema Conversion Tool does not support automatic migration of data definition language (DDL) code to create an index. CREATE TRIGGER CREATE TRIGGER statements are converted automatically except for the following clause: FOR MySQL doesn't support a FOR clause in a CREATE TRIGGER statement. CREATE VIEW CREATE VIEW statements are converted automatically except for the following clauses: SCHEMABINDING ENCRYPTION VIEW_METADATA AWS Schema Conversion Tool ignores this clause. AWS Schema Conversion Tool ignores this clause. AWS Schema Conversion Tool ignores this clause. Cursors Topics DECLARE CURSOR (p. 166) DECLARE CURSOR LOCAL GLOBAL FORWARD_ONLY SCROLL Change the global cursor to a local cursor, or revise your code so it doesn't require global cursors. Setting this option corresponds to the typical behavior of cursors in MySQL, so the AWS Schema Conversion Tool skips this option during conversion. Revise your code to eliminate cursors with the SCROLL option. 166

171 Related Topics STATIC KEYSET DYNAMIC FAST_FORWARD READ_ONLY SCROLL_LOCKS OPTIMISTIC TYPE_WARNING The membership and order of rows never changes for cursors in MySQL, so the AWS Schema Conversion Tool skips this option during conversion. Verify that the converted schema behavior is acceptable. Revise your code to eliminate dynamic cursors. Setting this option corresponds to the typical behavior of cursors in MySQL, so the AWS Schema Conversion Tool skips this option during conversion. All MySQL cursors are read-only, so the AWS Schema Conversion Tool skips this option during conversion. MySQL doesn't support the option SCROLL_LOCKS, so the AWS Schema Conversion Tool ignores this option during conversion. Verify that the converted schema behavior is acceptable. MySQL doesn't support the option OPTIMISTIC, so the AWS Schema Conversion Tool ignores this option during conversion. Verify that the converted schema behavior is acceptable. MySQL doesn't support the option TYPE_WARNING, so the AWS Schema Conversion Tool ignores this option during conversion. Verify that the converted schema behavior is acceptable. Change the global cursor to a local cursor, or revise your code so it doesn't require global cursors. Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Getting Started with the AWS Schema Conversion Tool (p. 10) Installing and Updating the AWS Schema Conversion Tool (p. 5) Keyboard Shortcuts The following table lists the keyboard shortcuts for the AWS Schema Conversion Tool. Keyboard Shortcut Ctrl+N Ctrl+L Ctrl+R Description Create a new project Connect to the source database. Connect to the target Amazon RDS DB instance. 167

172 Related Topics Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Getting Started with the AWS Schema Conversion Tool (p. 10) Installing and Updating the AWS Schema Conversion Tool (p. 5) 168

173 Cannot load objects from an Oracle source database Troubleshooting Issues with the AWS Schema Conversion Tool Following, you can find information about troubleshooting issues with the AWS Schema Conversion Tool. Cannot load objects from an Oracle source database When you attempt to load schema from an Oracle database, you might encounter one of the following errors: Cannot load objects tree. ORA-00942: table or view does not exist These errors occur because the user whose ID you used to connect to the Oracle database doesn't have sufficient permissions to read the schema, as required by the AWS Schema Conversion Tool. You can resolve the issue by granting the user select_catalog_role permission and also permission to any dictionary in the database. These permissions provide the read-only access to the views and system tables that is required by the AWS Schema Conversion Tool. The following example creates a user ID named min_privs and grants the user with this ID the minimum permissions required to convert schema from an Oracle source database. create user min_privs identified by min_privs; grant connect to min_privs; grant select_catalog_role to min_privs; grant select any dictionary to min_privs; 169

174 Related Topics Related Topics What Is the AWS Schema Conversion Tool? (p. 1) Getting Started with the AWS Schema Conversion Tool (p. 10) Installing and Updating the AWS Schema Conversion Tool (p. 5) 170

175 Document History The following table describes the important changes to the documentation since the last release of the AWS Schema Conversion Tool User Guide. Version: Latest documentation update: May 19, 2016 Change Maintenance release Maintenance release Maintenance release Maintenance release Maintenance release Maintenance release Preview release Description You can now use Secure Sockets Layer (SSL) to connect to your source database when you use the AWS Schema Conversion Tool. For more information, see Creating an AWS Schema Conversion Tool Project (p. 33). Adds support for MySQL and PostgreSQL as source databases for conversions. Adds support for editing the converted SQL that was generated for the target database engine. Adds improved selection capabilities in the source database and target DB instance tree views. Adds support for connecting to an Oracle source database using Transparent Network Substrate (TNS) names. Adds support for PostgreSQL as a target database engine. Adds the ability to generate converted schema as scripts and to save the scripts to files prior to applying the schema to the target DB instance. Adds offline project capability, the ability to check for new versions, and memory and performance management. Adds the Create New Database Migration Project wizard. Adds the ability to save the database migration assessment report as a PDF file. Provides the user guide for the AWS Schema Conversion Tool preview release. Date Changed May 19, 2016 April 11, 2016 March 2, 2016 January 14, 2016 December 2, 2015 October 19, 2015 October 7,