![]() ![]() In some cases a stored procedure must be called in an autonomous transaction. If the procedure can be directly converted to Transact-SQL, SSMA creates a stored procedure. In this case, SSMA creates a stored procedure and a function that calls the stored procedure. In some cases, the function must be converted to a stored procedure. If the function can be directly converted to Transact-SQL, SSMA creates a function. The following table shows which Oracle objects are converted, and the resulting SQL Server objects: Oracle Objects For more information, see Project Settings (Conversion) (OracleToSQL). By using this dialog box, you can set how SSMA converts functions and global variables. ![]() Setting Conversion Optionsīefore converting objects, review the project conversion options in the Project Settings dialog box. ![]() Use the output and error information to determine whether you have to modify your Oracle databases or your conversion process to obtain the desired conversion results. You can then view the objects and their properties by using the SQL Server Metadata Explorer.ĭuring the conversion, SSMA prints output messages to the Output pane and error messages to the Error List pane. ![]() It does not load the information into the instance of SQL Server. The Conversion ProcessĬonverting database objects takes the object definitions from Oracle, converts them to similar SQL Server objects, and then loads this information into the SSMA metadata. After you have connected to Oracle, connected to SQL Server, and set project and data mapping options, you can convert Oracle database objects to SQL Server database objects. ![]()
0 Comments
Leave a Reply. |