Merge pull request #33518 from aravindmahadevan-ms/patch-17

JillGrant615 · web-flow · commit 2f1876d4ba56 · 2025-04-01T12:39:48.000-06:00
SSMA for Oracle 10.1 release
diff --git a/docs/ssma/oracle/migrating-oracle-data-into-sql-server-oracletosql.md b/docs/ssma/oracle/migrating-oracle-data-into-sql-server-oracletosql.md
@@ -3,7 +3,8 @@ title: "Migrating Oracle Data into SQL Server (OracleToSQL)"
 description: Learn how to migrate data from an Oracle database to SQL Server, after you synchronize the converted objects, by using the SSMA for Oracle application.
 author: cpichuka
 ms.author: cpichuka
-ms.date: "01/19/2017"
+ms.reviewer: randolphwest
+ms.date: 04/01/2025
 ms.service: sql
 ms.subservice: ssma
 ms.topic: conceptual
@@ -18,111 +19,112 @@ helpviewer_keywords:
   - "Oracle Data Migration,Server-Side Migration"
 ---
 # Migrating Oracle Data into SQL Server (OracleToSQL)
-After you have successfully synchronized the converted objects with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], you can migrate data from Oracle to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
-  
+
+After you successfully synchronize the converted objects with [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], you can migrate data from Oracle to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] using SQL Server Migration Assistant (SSMA) for Oracle.
+
 > [!IMPORTANT]  
-> If the engine being used is Server Side Data Migration Engine, then, before you can migrate data, you must install the SSMA for Oracle Extension Pack and the Oracle providers on the computer that is running SSMA. The SQL Server Agent service must also be running. For more information about how to install the extension pack, see [Installing Server Components (OracleToSQL)](./installing-ssma-components-on-sql-server-oracletosql.md)  
-  
+> If the engine being used is Server Side Data Migration Engine, then before you can migrate data, you must install the SSMA for Oracle Extension Pack and the Oracle providers on the computer that is running SSMA. The SQL Server Agent service must also be running. For more information about how to install the extension pack, see [Installing SSMA components on SQL Server (OracleToSQL)](installing-ssma-components-on-sql-server-oracletosql.md).
+
 [!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
 
-## Setting Migration Options  
-Before migrating data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], review the project migration options in the **Project Settings** dialog box.  
-  
--   By using this dialog box you can set options such as migration batch size, table locking, constraint checking, null value handling, and identity value handling. For more information about the Project Migration Settings, see [Project Settings (Migration) (OracleToSQL)](./project-settings-migration-oracletosql.md).  
-  
--   The **Migration Engine** in the **Project Settings** dialog box, allows the user to perform the migration process using two types of data migration engines:  
-  
-    1.  Client Side Data Migration Engine  
-  
-    2.  Server Side Data Migration Engine  
-  
-**Client Side Data Migration:**  
-  
--   To initiate data-migration on the client side, select the **Client Side Data Migration Engine** option in the **Project Settings** dialog box.  
-  
--   In **Project Settings**, the **Client Side Data Migration Engine** option is set.  
-  
-    > [!NOTE]  
-    > The **Client-Side Data Migration Engine** resides inside the SSMA application and is, therefore, not dependent on the availability of the extension pack.  
-  
-**Server Side Data Migration:**  
-  
--   During the Server side data migration, the engine resides on the target database. It is installed through the extension pack. For more information on how to install the extension pack, see [Installing Server Components on SQL Server](installing-ssma-components-on-sql-server-oracletosql.md)  
-  
--   To initiate migration on the server side, select the **Server Side Data Migration Engine** option in the **Project Settings** dialog box.  
-  
-## Migrating Data to SQL Server  
-Migrating data is a bulk-load operation that moves rows of data from Oracle tables into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] tables in transactions. The number of rows loaded into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in each transaction is configured in the project settings.  
-  
-To view migration messages, make sure that the Output pane is visible. Otherwise, from the **View** menu, select **Output**.  
-  
-**To migrate data**  
-  
-1.  Verify the following:  
-  
-    -   The Oracle providers are installed on the computer that is running SSMA.  
-  
-    -   You have synchronized the converted objects with the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database.  
-  
-2.  In Oracle Metadata Explorer, select the objects that contain the data that you want to migrate:  
-  
-    -   To migrate data for all schemas, select the check box next to **Schemas**.  
-  
-    -   To migrate data or omit individual tables, first expand the schema, expand **Tables**, and then select or clear the check box next to the table.  
-  
-3.  To migrate data, two cases arise:  
-  
-    **Client Side Data Migration:**  
-  
-    -   For performing **Client Side Data Migration**, select the **Client Side Data Migration Engine** option in the **Project Settings** dialog box.  
-  
-    **Server Side Data Migration:**  
-  
-    -   Before performing data migration on the server side, ensure:  
-  
-        1.  The SSMA for Oracle Extension Pack is installed on the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
-  
-        2.  The SQL Server Agent service is running on the instance of SQL Server.  
-  
-    -   For performing **Server Side Data Migration**, select the **Server Side Data Migration Engine** option in the **Project Settings** dialog box.  
-  
-4.  Right-click **Schemas** in Oracle Metadata Explorer, and then click **Migrate Data**. You can also migrate data for individual objects or categories of objects: Right-click the object or its parent folder; select the **Migrate Data** option.  
-  
-    > [!NOTE]  
-    > If the SSMA for Oracle Extension Pack is not installed on the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], and if **Server Side Data Migration Engine** is selected, then while migrating the data to the target database, the following error is encountered: 'SSMA Data Migration components were not found on SQL Server, server-side data migration will not be possible. Please check if Extension Pack is installed correctly'. Click **Cancel** to terminate the data migration.  
-  
-5.  In the **Connect to Oracle** dialog box, enter the connection credentials, and then click **Connect**. For more information on connecting to Oracle, see [Connect To Oracle &#40;OracleToSQL&#41;](../../ssma/oracle/connect-to-oracle-oracletosql.md)  
-  
-    For connecting to the target database [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], enter the connection credentials in the **Connect to SQL Server** dialog box, and click **Connect**. For more information on connecting to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], see [Connect to SQL Server](../sybase/connecting-to-sql-server-sybasetosql.md)  
-  
-    Messages will appear in the **Output** pane. When the migration is complete, the **Data Migration Report** appears. If any data did not migrate, click the row that contains the errors, and then click **Details**. When you are finished with the report, click **Close**. For more information on Data Migration Report, see [Data Migration Report (SSMA Common)](../sybase/data-migration-report-sybasetosql.md)  
-  
+## Set migration options
+
+Before migrating data to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], review the project migration options in the **Project Settings** dialog box.
+
+In this dialog box, you can set options such as migration batch size, table locking, constraint checking, null value handling, and identity value handling. For more information about the Project Migration Settings, see [Project Settings (Migration)](project-settings-migration-oracletosql.md).
+
+The **Migration Engine** in the **Project Settings** dialog box, allows the user to perform the migration process using two types of data migration engines:
+
+- Client Side Data Migration Engine
+- Server Side Data Migration Engine
+
+### Client Side Data Migration
+
+To initiate data-migration on the client side, select the **Client Side Data Migration Engine** option in the **Project Settings** dialog box.
+
+In **Project Settings**, the **Client Side Data Migration Engine** option is set.
+
 > [!NOTE]  
-> When SQL Express edition is used as the target database, only client side data migration is allowed and server side data migration is not supported.
+> The **Client-Side Data Migration Engine** resides inside the SSMA application and is, therefore, not dependent on the availability of the extension pack.
+
+### Server Side Data Migration
+
+During the Server side data migration, the engine resides on the target database. It's installed through the extension pack. For more information on how to install the extension pack, see [Installing SSMA components on SQL Server](installing-ssma-components-on-sql-server-oracletosql.md)
+
+To initiate migration on the server side, select the **Server Side Data Migration Engine** option in the **Project Settings** dialog box.
+
+## Migrate Data to SQL Server
+
+Migrating data is a bulk-load operation that moves rows of data from Oracle tables into [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] tables in transactions. The number of rows loaded into [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] in each transaction is configured in the project settings.
+
+To view migration messages, make sure that the Output pane is visible. Otherwise, from the **View** menu, select **Output**.
+
+### Migration process
+
+1. Verify the following requirements:
+
+   - The Oracle providers are installed on the computer that is running SSMA.
+   - You have synchronized the converted objects with the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] database.
 
-## Migrating data at scale (Preview)
+1. In Oracle Metadata Explorer, select the objects that contain the data that you want to migrate:
+
+   - To migrate data for all schemas, select the check box next to **Schemas**.
+
+   - To migrate data or omit individual tables, first expand the schema, expand **Tables**, and then select or clear the check box next to the table.
+
+1. To migrate data, two cases arise:
+
+   **Client Side Data Migration:**
+
+   - For performing **Client Side Data Migration**, select the **Client Side Data Migration Engine** option in the **Project Settings** dialog box.
+
+   **Server Side Data Migration:**
+
+   - Before performing data migration on the server side, ensure:
+
+     1. The SSMA for Oracle Extension Pack is installed on the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
+
+     1. The SQL Server Agent service is running on the instance of SQL Server.
+
+   - For performing **Server Side Data Migration**, select the **Server Side Data Migration Engine** option in the **Project Settings** dialog box.
+
+1. Right-click **Schemas** in Oracle Metadata Explorer, and then select **Migrate Data**. You can also migrate data for individual objects or categories of objects: Right-click the object or its parent folder; select the **Migrate Data** option.
+
+   If the SSMA for Oracle Extension Pack isn't installed on the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], and if **Server Side Data Migration Engine** is selected, then while migrating the data to the target database, you receive the following error:
+
+   ```output
+   SSMA Data Migration components were not found on SQL Server, server-side data migration will not be possible. Please check if Extension Pack is installed correctly.
+   ```
+
+   Select **Cancel** to terminate the data migration.
+
+1. In the **Connect to Oracle** dialog box, enter the connection credentials, and then select **Connect**. For more information on connecting to Oracle, see [Connect to Oracle](connect-to-oracle-oracletosql.md)
+
+   For connecting to the target database [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], enter the connection credentials in the **Connect to SQL Server** dialog box, and select **Connect**. For more information on connecting to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], see [Connecting to SQL Server](../oracle/connecting-to-sql-server-oracletosql.md).
+
+   Messages appear in the **Output** pane. When the migration is complete, the **Data Migration Report** appears. If any data didn't migrate, select the row that contains the errors, and then select **Details**. When you're finished with the report, select **Close**. For more information on Data Migration Report, see [Data Migration Report](../oracle/data-migration-report-oracletosql.md).
+
+> [!NOTE]  
+> When SQL Express edition is used as the target database, only client side data migration is allowed and server side data migration isn't supported.
 
-When large data size needs to be migrated within a short duration, at scale offline migration is a suitable option. This feature uses the Azure data factory pipeline and the scalability of cloud to migrate on-premises or external Oracle data source to Azure SQL platform whether IaaS VM or SQL PaaS. This capability will create the data factory or use an existing data factory to migrate data to Azure SQL PaaS or SQL VM.
+## Migrate data at scale (preview)
 
-1. For large offline migration, click on Migrate data at scale. 
+When large data size needs to be migrated within a short duration, at scale offline migration is a suitable option. This feature uses Azure Data Migration Service (DMS) in the backend, and the scalability of cloud to migrate on-premises or external Oracle data source to Azure SQL platform, whether using a virtual machine (IaaS VM) or Azure SQL (PaaS). You can create a new DMS service, or use an existing DMS service to migrate data to Azure SQL PaaS or SQL Server on Azure VM.
 
-1. Provide Microsoft Entra/Azure AD account for authentication. Once you enter the username, select **Connect**.
+1. For large offline migration, select **Migrate data with DMS (preview)**.
 
-1. Select the tenant and the subscription that already has the Azure SQL VM or Azure SQL database or managed instance configured and click next.
+1. Provide Microsoft Entra account for authentication. Once you enter the username, select **Connect**.
 
-1. The next step in the migrate workflow is to provide the data source credentials followed by the target SQL credentials.
+1. Select the tenant and the subscription that already has the SQL Server on Azure VM, Azure SQL database, or SQL managed instance configured, and select **Next**.
 
-1. For this migration, either you can use existing Azure resources -  resource group and the data factory name or click new to create a resource group and Azure data factory for migration.
+1. In the next step of the migration workflow, you can provide the data source, target database, and associated credentials.
 
-1. In order to migrate an external data source,  an integration runtime is required. Either click new and follow the steps to create the integration runtime or use an existing integration service. To create an integration service, a gateway installation needs to be configured and a key needs to be supplied to configure integration runtime.
+1. When you select your Azure resource, you can use existing resources by selecting the resource group and the data migration service name, or select **New** to create a resource group and Azure migration service for migration.
 
-1. Finally, provide a unique data  migration name. Migration name supports characters and numeric values. Avoid any special characters.
+1. In order to migrate an external data source, an integration runtime is required. Either select new and follow the steps to create the integration runtime or use an existing integration service. To create an integration service, a gateway installation needs to be configured and a key needs to be supplied to configure integration runtime.
 
-1. If the target tables contain data, it will be truncated and reloaded. A warning dialog box will appear.  Select OK to proceed or cancel to avoid truncate and load activity.
+1. The Monitor Migrations Wizard automatically opens within a few seconds of initiating the data migration. Select **View** under the activity you wish to monitor, to view a live migration status. You can also view the comprehensive report, which takes you to the Azure portal for more granular monitoring details about the migration activity. You can access the wizard with the **Monitoring** button next to **Migrate data with DMS(preview)**.
 
-1. It takes few minutes to create Azure data factory components. The status bar will provide the progress of the pipeline creation. If the pipeline is created successfully, a message will be written in the output log "A data factory pipeline [PipelineName] is created for the data migration activity."
+## Related content
 
-1. For monitoring the data migration, click on the monitoring URL or go to the data factory monitoring page in Azure portal.
-  
-## See Also  
-[Migrating Oracle Databases to SQL Server &#40;OracleToSQL&#41;](../../ssma/oracle/migrating-oracle-databases-to-sql-server-oracletosql.md)  
+- [Migrate Oracle Databases to SQL Server (OracleToSQL)](migrating-oracle-databases-to-sql-server-oracletosql.md)
