|
1 | 1 | --- |
2 | 2 | title: What Is Microsoft Copilot in SSMA for Oracle? |
3 | | -description: Learn how Copilot in SQL Server Migration Assistant (SSMA) provides intelligent, AI-powered assistance for complex or unsupported objects. |
4 | | -author: nilabjaball |
5 | | -ms.author: niball |
6 | | -ms.reviewer: randolphwest |
7 | | -ms.date: 11/12/2025 |
| 3 | +description: Learn how Copilot in SQL Server Migration Assistant (SSMA) for Oracle provides intelligent, AI-powered assistance to convert complex or unsupported objects. |
| 4 | +author: rwestMSFT |
| 5 | +ms.author: randolphwest |
| 6 | +ms.reviewer: niball, subasak |
| 7 | +ms.date: 02/02/2026 |
8 | 8 | ms.service: sql |
9 | 9 | ms.subservice: ssma |
10 | 10 | ms.topic: overview |
11 | 11 | ms.collection: |
12 | 12 | - ce-skilling-ai-copilot |
13 | 13 | ms.update-cycle: 180-days |
14 | 14 | --- |
| 15 | +# What is Microsoft Copilot in SSMA for Oracle (OracleToSQL)? |
15 | 16 |
|
16 | | -# What is Microsoft Copilot in SSMA for Oracle? |
17 | | - |
18 | | -Copilot in SQL Server Migration Assistant (SSMA) enhances the code conversion process from Oracle to SQL by providing intelligent, AI-powered assistance for complex or unsupported objects. When the SSMA rule engine encounters conversion challenges, such as syntax differences, proprietary Oracle features, or unsupported data types, Copilot steps in to analyze the issue, explain the root cause, and generate alternative SQL-compatible code. |
| 17 | +Copilot in SQL Server Migration Assistant (SSMA) enhances the code conversion process from Oracle to Transact-SQL by providing intelligent, AI-powered assistance for complex or unsupported objects. When the SSMA rule engine encounters conversion challenges, such as syntax differences, proprietary Oracle features, or unsupported data types, Copilot steps in to analyze the issue, explain the root cause, and generate alternative SQL-compatible code. |
19 | 18 |
|
20 | 19 | Copilot in SQL Server Migration Assistant (SSMA) is generally available from SSMA version 10.4. |
21 | 20 |
|
22 | 21 | By integrating with Azure OpenAI, Copilot in SSMA for Oracle allows you to review, refine, and validate the suggested code directly within the SSMA interface, streamlining the migration process and reducing manual effort. |
23 | 22 |
|
24 | 23 | ## Prerequisites |
25 | 24 |
|
26 | | -To use Copilot in SSMA for Oracle for code conversion, ensure you have one of the following methods configured: |
| 25 | +To use Copilot in SSMA for Oracle for code conversion, you can use one of the following methods: |
27 | 26 |
|
28 | 27 | ### Option 1: Azure OpenAI resource (Bring your own key) |
29 | 28 |
|
30 | | -- Azure OpenAI Endpoint URL |
31 | | -- Azure OpenAI Deployment |
32 | | -- Model Name |
33 | | -- Azure OpenAI Key |
| 29 | +- Azure OpenAI Endpoint URL. |
| 30 | +- Azure OpenAI Deployment. |
| 31 | +- Model name. |
| 32 | +- Azure OpenAI key. |
34 | 33 |
|
35 | | -If you don't have these details, follow the steps in the [How to create Azure OpenAI resource](#modify-azure-openai-settings) section. |
| 34 | +If you don't have these details, see the [Modify Azure OpenAI settings](#modify-azure-openai-settings) section. |
36 | 35 |
|
37 | 36 | ### Option 2: Microsoft-managed endpoint with Microsoft Entra ID authentication (Preview) |
38 | 37 |
|
39 | 38 | SSMA for Oracle 10.4 introduces this authentication type for Copilot in SSMA. |
40 | 39 |
|
41 | | -- No manual key entry required |
42 | | -- Sign in using your Microsoft Entra ID credentials |
43 | | -- Authentication is handled via a browser-based login flow |
| 40 | +- No manual key entry required. |
| 41 | +- Sign in using your Microsoft Entra ID credentials. |
| 42 | +- Authentication is handled through a browser-based authentication flow. |
44 | 43 |
|
45 | 44 | ## Steps to run Copilot in SSMA for Oracle |
46 | 45 |
|
47 | | -Once the code conversion is done, the target objects that the SSMA rule engine couldn't convert, display warnings or errors. For those objects, you can launch **Fix with Copilot**. |
| 46 | +After code conversion, the tool displays warnings or errors for target objects that the SSMA rule engine can't convert. For those objects, you can select **Fix with Copilot**. |
48 | 47 |
|
49 | | -If the OpenAI resource isn't registered, you're prompted with an authentication selection form. You can choose between: |
| 48 | +If the OpenAI resource isn't registered, the tool prompts you with an authentication selection form. You can choose between: |
50 | 49 |
|
51 | | -- **Microsoft Entra ID Authentication** (new flow) |
52 | | -- **Azure OpenAI Key** (existing flow) |
| 50 | +- **Microsoft Entra ID Authentication** (new flow). |
| 51 | +- **Azure OpenAI Key** (existing flow). |
53 | 52 |
|
54 | 53 | ### Microsoft Entra ID authentication flow (Preview) |
55 | 54 |
|
56 | | -1. Select **Microsoft Entra ID Authentication** and select **Next**. |
57 | | - |
58 | | -1. A browser window opens, prompting you to sign in. |
59 | | - |
60 | | -1. Once authenticated, the Copilot interface loads, and you can review the suggested code fixes. |
| 55 | +1. Select **Microsoft Entra ID Authentication**, and then select **Next**. |
| 56 | +1. A browser window opens and prompts you to sign in. |
| 57 | +1. After authentication, the Copilot interface loads, and you can review the suggested code fixes. |
61 | 58 |
|
62 | | -1. If you select the Copilot icon again, the authentication form doesn't reappear unless you sign out, or reset the settings. |
| 59 | +If you select the Copilot icon again, the authentication form doesn't reappear unless you sign out or reset the settings. |
63 | 60 |
|
64 | 61 | To sign out: |
65 | 62 |
|
66 | | -- Select the profile icon in the top-right corner and select **Log out**. |
| 63 | +- Select the profile icon in the upper-right corner, and then select **Log out**. |
67 | 64 |
|
68 | | -- Alternatively, navigate to **Tools** > **Project Settings** > **Copilot**, clear the saved credentials, and apply changes. |
| 65 | +Alternatively, go to **Tools** > **Project Settings** > **Copilot**, clear the saved credentials, and apply changes. |
69 | 66 |
|
70 | | -### Azure OpenAI Key flow |
| 67 | +### Azure OpenAI key flow |
71 | 68 |
|
72 | | -If you want to bring your own key, and the OpenAI resource isn't registered, you must complete the following fields: |
| 69 | +If you want to bring your own key and the OpenAI resource isn't registered, complete the following fields: |
73 | 70 |
|
74 | | -- Azure OpenAI Endpoint URL |
75 | | -- Azure OpenAI Deployment |
76 | | -- Model Name |
77 | | -- Azure OpenAI Key |
| 71 | +- Azure OpenAI Endpoint URL. |
| 72 | +- Azure OpenAI Deployment. |
| 73 | +- Model name. |
| 74 | +- Azure OpenAI key. |
78 | 75 |
|
79 | 76 | :::image type="content" source="media/copilot-in-ssma-overview/validate-endpoint.png" alt-text="Screenshot of Validate endpoint dialog."::: |
80 | 77 |
|
81 | | -Once the validation is successful, you can view the converted code. It takes a few minutes to generate the converted code. After the code is generated, you can review the suggested changes. |
| 78 | +After successful validation, you can view the converted code. It can take a few minutes to generate the converted code. After the code is generated, you can review the suggested changes. |
82 | 79 |
|
83 | 80 | ## Code conversion interface |
84 | 81 |
|
85 | 82 | The Code Conversion window has three sections: |
86 | 83 |
|
87 | 84 | | Section | Description | |
88 | 85 | | --- | --- | |
89 | | -| **Errors to fix** | This section shows the possible issues identified or errors to fix that SSMA rule engine couldn't convert or failed to parse the PL/SQL statement. | |
90 | | -| **Explanation** | Provides root cause of conversion issues, describing the logic behind its suggestions, and offering clear, contextual insights to help you understand and validate the generated Transact-SQL code. | |
91 | | -| **Code review window** | Allows you to view side-by-side differences between SSMA-generated and Copilot-converted code. It highlights changes, enabling you to evaluate improvements, understand modifications, and make informed decisions before accepting suggestions. | |
| 86 | +| **Errors to fix** | Shows the possible errors that the SSMA rule engine couldn't convert or failed to parse in the PL/SQL statement. | |
| 87 | +| **Explanation** | Provides the root cause of conversion issues, describes the logic behind the suggestions, and offers clear, contextual insights to help you understand and validate the generated Transact-SQL code. | |
| 88 | +| **Code review window** | Allows you to view side-by-side differences between SSMA-generated and Copilot-converted code. It highlights changes so that you can evaluate improvements, understand modifications, and make informed decisions before accepting suggestions. | |
92 | 89 |
|
93 | 90 | :::image type="content" source="media/copilot-in-ssma-overview/compare-code.png" alt-text="Screenshot of code comparison dialog." lightbox="media/copilot-in-ssma-overview/compare-code.png"::: |
94 | 91 |
|
95 | | -You can retry or send additional information in the prompt if they aren't satisfied with the conversion. If the converted code is suitable, you can accept the suggestions. |
| 92 | +You can retry or send additional information in the prompt if you're not satisfied with the conversion. If the converted code is suitable, you can accept the suggestions. |
96 | 93 |
|
97 | 94 | ## Manage accepted changes in the IDE |
98 | 95 |
|
99 | | -Once you review and accept the Copilot-generated code, you can find the accepted changes in the SSMA IDE. Follow these steps to save and synchronize the changes with your database: |
| 96 | +After you review and accept the Copilot-generated code, find the accepted changes in the SSMA IDE. Follow these steps to save and synchronize the changes with your database: |
100 | 97 |
|
101 | | -1. Navigate to the SSMA IDE where the accepted changes are displayed. |
102 | | -1. Save the changes to ensure they're stored locally. |
| 98 | +1. Go to the SSMA IDE where the accepted changes are displayed. |
| 99 | +1. Save the changes to store them locally. |
103 | 100 | 1. Use the synchronization feature to replicate the changes to your database. |
104 | 101 |
|
105 | 102 | ## Modify Azure OpenAI settings |
106 | 103 |
|
107 | | -If you need to change the Azure OpenAI details, go to **Tools** > **Project Settings** > **Copilot** in the SSMA menu. Update the **Azure OpenAI Endpoint**, **Azure OpenAI Deployment**, **Model Name**, and **Azure OpenAI Key** as required. |
| 104 | +If you need to change the Azure OpenAI details, go to **Tools** > **Project Settings** > **Copilot** in the SSMA menu. Update the **Azure OpenAI Endpoint**, **Azure OpenAI Deployment**, **Model Name**, and **Azure OpenAI Key** as needed. |
108 | 105 |
|
109 | 106 | ## Review and validation |
110 | 107 |
|
111 | | -As this code is generated by AI, it's crucial to review, validate, and test the changes before accepting or saving them. Ensure that the code meets your requirements, and functions correctly in your environment. |
| 108 | +Because AI generates this code, you must review, validate, and test the changes before you accept or save them. Ensure that the code meets your requirements and functions correctly in your environment. |
112 | 109 |
|
113 | 110 | ## Limitations |
114 | 111 |
|
115 | | -Copilot-generated code for tables and user-defined data types can't be saved directly in SSMA. In such cases, SSMA provides a download option to save the Copilot-generated code locally. |
| 112 | +You can't save Copilot-generated code for tables and user-defined data types directly in SSMA. In these cases, SSMA provides a download option to save the Copilot-generated code locally. |
116 | 113 |
|
117 | 114 | ## Related content |
118 | 115 |
|
|
0 commit comments