SSMAOracle

Guide to Migrating from Oracle to SQL Server 2005

SQL Server Technical Article

Writers: Vladimir Kisil, Denis Sevastyanov, Valery Fomenko, Yuri Rusakov Technical Reviewer: Darmadi Komo, Irena Balin, Dmitry Balin

Published: November 2007 Applies To: SQL Server 2005 Summary: This white paper explores challenges that arise when you migrate from an Oracle 7.3 database or later to SQL Server 2005. It describes the implementation differences of database objects, SQL dialects, and procedural code between the two platforms. The entire migration process using SQL Server Migration Assistant for Oracle (SSMA Oracle) is explained in depth, with a special focus on converting database objects and PL/SQL code.
Copyright
This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.
2007 Microsoft Corporation. All rights reserved.
Microsoft is a registered trademarks of Microsoft Corporation in the United States and other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Table of Contents
Overview of Oracle-to-SQL Server 2005 Migration............................................1 Main Migration Steps.......................................................................................1 Conversion of Database Objects........................................................................2 Differences in SQL Languages...........................................................................2 PL/SQL Conversion..........................................................................................3 Data Migration Architecture of SSMA for Oracle................................................4 Implementation in SSMA..................................................................................4 Solution Layers...............................................................................................4 Client Application............................................................................................4 Stored Procedures Interface.............................................................................5 Database Layer...............................................................................................5 Migration Executable.......................................................................................5 Message Handling...........................................................................................6 Validation of the Results...................................................................................6 Migrating Oracle Data Types.............................................................................6 Numeric Data Types........................................................................................8 Character Data Types......................................................................................8 Date and Time................................................................................................9 Boolean Type..................................................................................................9 Large Object Types..........................................................................................9 XML Type.....................................................................................................10 ROWID Types................................................................................................10 Emulating Oracle System Objects....................................................................10 Converting Oracle System Views.....................................................................10 Location of Generated System View Emulations for SSMA 3.0........................11 ALL_INDEXES System View........................................................................12 ALL_OBJECTS System View........................................................................12 ALL_SYNONYMS System View....................................................................12 ALL_TAB_COLUMNS System View...............................................................12 ALL_TABLES System View..........................................................................12 ALL_CONSTRAINTS System View................................................................12 ALL_SEQUENCES System View...................................................................12 ALL_VEWS System View............................................................................13 ALL_USERS System View...........................................................................13 ALL_SOURCE System View........................................................................13 GLOBAL_NAME System View......................................................................13 ALL_JOBS System View.............................................................................13 V$SESSION System View..........................................................................13
Microsoft Corporation 2007
ii
DBA_EXTENTS System View......................................................................13 V$LOCKED_OBJECT System View...............................................................14 DBA_FREE_SPACE system view..................................................................15 DBA_SEGMENTS system view....................................................................15 Converting Oracle System Functions................................................................16 TRIM System Function ..............................................................................23 USERENV System Function........................................................................24 NVL2 System Function..............................................................................24 Converting Oracle System Packages................................................................25 DBMS_SQL Package..................................................................................25 DBMS_OUTPUT package............................................................................26 UTL_FILE Package ...................................................................................27 DBMS_UTILITY Package............................................................................29 DBMS_SESSION Package...........................................................................29 DBMS_PIPE Package.................................................................................29 DBMS_LOB Package..................................................................................31 DBMS_JOB System Package.......................................................................37 DBMS_JOB.SUBMIT...................................................................................38 DBMS_JOB.REMOVE..................................................................................39 Example of an Oracle Job Conversion..........................................................39 Converting Nested PL/SQL Subprograms .......................................................44 Inline Substitution.........................................................................................45 Emulation by Using Transact-SQL Subprograms................................................52 Migrating Oracle User-Defined Functions........................................................63 Conversion Algorithm.....................................................................................63 Converting Function Calls When a Function Has Default Values for Parameters and with Various Parameter Notations....................................................................68 Converting Functions that Have Default Parameters Other Than Constants...........69 Solution 1................................................................................................69 Solution 2................................................................................................70 Migrating Oracle Triggers................................................................................72 Conversion Patterns.......................................................................................74 AFTER Triggers.........................................................................................75 BEFORE Triggers......................................................................................82 INSTEAD OF Triggers................................................................................90 Autonomous Transactions in Triggers..........................................................95 Notes on Autonomous Transaction Conversion in Triggers..............................96 Emulating Oracle Packages.............................................................................97 Converting Procedures and Functions...............................................................97 Converting Overloaded Procedures..................................................................98
iii
Converting Packaged Variables........................................................................99 Converting Simple Variables.......................................................................99 Converting Collections and Records.............................................................99 Converting Packaged Cursors..........................................................................99 Converting Initialization Section....................................................................100 Calling Initialization from the Within Procedure...........................................100 Calling Initialization from the Within Function.............................................100 SSMAs Package Variables Implementation Details......................................100 Package Conversion Code Example................................................................101 Emulating Oracle Sequences.........................................................................103 How SSMA 3.0 Creates and Drops Sequences..................................................103 NEXTVAL and CURRVAL Simulation in SSMA 3.0..............................................104 Examples of Conversion................................................................................105 Inserting Sequence Values Into a Table.....................................................105 Optimization Tips....................................................................................107 Migrating Hierarchical Queries .....................................................................109 Emulating Oracle Exceptions.........................................................................111 Exception Raising.........................................................................................112 Exception Handling......................................................................................113 SSMA Exceptions Migration...........................................................................115 Migrating Oracle Cursors...............................................................................117 Syntax.......................................................................................................117 Declaring a Cursor.......................................................................................118 Opening a Cursor.........................................................................................120 Fetching Data..............................................................................................120 CURRENT OF Clause.....................................................................................125 Closing a Cursor..........................................................................................125 Examples of SSMA 3.0 Conversion.................................................................125 FOR Loop Cursor Conversion....................................................................125 Cursor with Parameters...........................................................................127 Cursor Attributes Conversion....................................................................129 Simulating Oracle Transactions in SQL Server 2005......................................131 Choosing a Transaction Management Model....................................................131 Autocommit Transactions..............................................................................131 Implicit Transactions....................................................................................131 Explicit Transactions.....................................................................................131 Choosing a Concurrency Model......................................................................132 Make Transaction Behavior Look Like Oracle...................................................132 Simulating Oracle Autonomous Transactions................................................132 Simulating Autonomous Procedures and Packaged Procedures...........................134
iv
Simulating Autonomous Functions and Packaged Functions...............................134 Simulation of Autonomous Triggers................................................................135 Code Examples............................................................................................135 Migrating Oracle Collections and Records.....................................................139 Implementing Collections..............................................................................139 Implementing Records..................................................................................147 Implementing Records and Collections Via XML...............................................150 Implementing Records.............................................................................150 Implementing Collections.........................................................................152 Sample Functions for XML Record Emulation...................................................153 Conclusion.....................................................................................................155
Overview of Oracle-to-SQL Server 2005 Migration

Migrating from an Oracle database to Microsoft SQL Server 2005 frequently gives organizations benefits that range from lowered costs to a more feature-rich environment. The free Microsoft SQL Server Migration Assistant (SSMA) for Oracle speeds the migration process. SQL Server Migration Assistant for Oracle (SSMA for Oracle) 3.0 converts Oracle database objects (including stored procedures) to SQL Server database objects, loads those objects into SQL Server, migrates data from Oracle to SQL Server, and then validates the migration of code and data. This white paper explores the challenges that arise when migrating from an Oracle database to SQL Server 2005. It describes the implementation differences of database objects, SQL dialects, and procedural code between the two platforms. In-depth sections explain the entire SSMA for Oracle migration process, with a special focus on converting database objects and PL/SQL code.
Main Migration Steps

The first migration step is to decide on the physical structure of the target SQL Server database. In the simplest case, you can map the Oracle tablespaces to SQL Server filegroups. However, since the files in the filegroups and the information stored in the files is usually different, this is not usually possible. The next step is to choose how to map the Oracle schemas to the target. In SQL Server, schemas are not necessarily linked to a specific user or a login, and one server contains multiple databases. You can follow one of two typical approaches to schema mapping: 1. By default in SSMA, every Oracle schema becomes a separate SQL Server database. The target SQL Server schema in each of these databases is set to dbothe predefined name for the database owner. Use this method when there are few references between Oracle schemas. 2. Another approach is to map all Oracle schemas to one SQL Server database. In this case, an Oracle schema becomes a SQL Server schema with the same name. To use this method, you change the SSMA default settings. Use this method when different source schemas are deeply linked with each other. SSMA applies the selected schema-mapping method consistently when it converts both database objects and the references to them. After you chose your optimal schema mapping, you can start creating the target SQL Server database and its required schemas. Because the SQL Server security scheme is quite different from Oracles, we chose not to automate the security item migration in SSMA. That way, you can consider all possibilities and make the proper decisions yourself. The typical SSMA migration includes connecting to the source Oracle server, selecting the server that is running SQL Server as the target, and then performing the Convert Schema command. When the target objects are created in the SSMA workspace, you can save them by using the Load to Database command. Finally, execute the Migrate Data command, which transfers the data from the source to the target tables, making the necessary conversions. The data migration process is executed on the server that is running SQL Server. The internal implementation of this feature is described in Data Migration Architecture of SSMA for Oracle.
Microsoft Corporation 2007
Conversion of Database Objects

Not all Oracle database objects have direct equivalents in SQL Server. In many cases, SSMA creates additional objects to provide the proper emulation. General conversion rules are as follows: Each Oracle table is converted to a SQL Server table. During the conversion, all indexes, constraints, and triggers defined for a table are also converted. When determining the target table's structure, SSMA uses type mapping definitions. Data type conversion is described in Migrating Oracle Data Types. An Oracle view is converted to an SQL Server view. The only exception is the materialized view, which becomes an ordinary table. SSMA creates emulations for commonly used Oracle system views. For more about system view conversion, see Emulating Oracle System Objects. Oracle stored procedures are converted to SQL Server stored procedures. Note that Oracle procedures can use nested subprograms, which means that another procedure or function can be declared and called locally within the main procedure. This is called nested subprograms. The current version of SSMA does not support nested subprograms, but you can find methods to manually convert them in Converting Nested PL/SQL Subprograms. Oracle user-defined functions are converted to SQL Server functions if the converted function can be compatible with SQL Server requirements. Otherwise, SSMA creates two objects: one function and one stored procedure. The additional procedure incorporates all the logic of the original function and is invoked in a separate process. For more information, see Migrating Oracle User-Defined Functions. SSMA emulates most of the Oracle standard functions. See the complete list in Emulating Oracle System Objects. Oracle DML triggers are converted to SQL Server triggers, but because the trigger functionality is different, the number of triggers and their types can be changed. See a description of trigger conversion in Migrating Oracle Triggers. Some Oracle object categories, such as packages, do not have direct SQL Server equivalents. SSMA converts each packaged procedure or function into separate target subroutines and applies rules for standalone procedures or functions. Other issues related to package conversion, such as converting packaged variables, cursors, and types are explained in Emulating Oracle Packages. In addition, SSMA can emulate some commonly used Oracle system packages. See their description in Emulating Oracle System Objects. SQL Server has no exact equivalent to Oracle sequences. SSMA can use one of two sequence conversion methods. The first method is to convert a sequence to an SQL Server identity column. That is the optimal solution, but as Oracle sequence objects are not linked to tables, using sequences may not be compatible with identity column functionality. In that situation, SSMA uses a second method, which is to emulate sequences by additional tables. This is not as effective as the first method, but it ensures better compatibility with Oracle. See details in Emulating Oracle Sequences. Oracle private synonyms are converted to SQL Server synonyms stored in the target database. SSMA converts public synonyms to synonyms defined in the sysdb database.
Differences in SQL Languages

Oracle and SQL Server use different dialects of the SQL language, but SSMA can solve most of the problems introduced by this. For example, Oracle uses CONNECT BY
statements for hierarchical queries, while SQL Server implements hierarchical queries by using common table expressions. The syntax of common table expressions does not resemble the Oracle format, and the order of tree traversal is different. To learn how SSMA converts hierarchical queries, see Migrating Hierarchical Queries. Or consider how SSMA handles another non-standard Oracle feature: the special outer join syntax with the (+) qualifier. SSMA converts these queries by transforming them into ANSI format. Oracle pseudocolumns, such as ROWID or ROWNUM, present a special problem. When converting ROWNUM, SSMA emulates it with the TOP keyword of the SELECT statement if this pseudocolumn is used only to limit the size of the result set. If the row numbers appear in a SELECT list, SSMA uses the ROW_NUMBER( ) function. The ROWID problem can be solved by an optional column named ROWID, which stores a unique identifier in SQL Server. SSMA does not convert dynamic SQL statements because the actual statement is not known until execution time and, in most cases, cannot be reconstructed at conversion time. There is a workaround: The Oracle metabase tree displayed in SSMA contains a special node named Statements in which you can create and convert ad hoc SQL statements. If you can manually reproduce the final form of a dynamic SQL command, you can convert it as an object in the Statements node.
PL/SQL Conversion
The syntax of Oracles PL/SQL language is significantly different from the syntax of SQL Servers procedural language, Transact-SQL. This makes converting PL/SQL code from stored procedures, functions, or triggers a challenge. SSMA, however, can resolve most of the problems related to these conversions. SSMA also allows establishing special data type mappings for PL/SQL variables. Some conversion rules for PL/SQL are straightforward, such as converting assignment, IF, or LOOP statements. Other SSMA conversion algorithms are more complicated. Consider one difficult case: converting Oracle exceptions, which is described in Emulating Oracle Exceptions. The solution detailed there allows emulating Oracle behavior as exactly as possible, but you may need to review the code in order to eliminate dependencies on Oracle error codes and to simplify the processing of such conditions as NO_DATA_FOUND. Oracle cursor functionality is not identical to cursor functionality in SQL Server. SSMA handles the differences as described in Migrating Oracle Cursors. Oracle transactions are another conversion issue, especially autonomous transactions. In many cases you must review the code generated by SSMA to make the transaction implementation best suited to your needs. For instructions, see Simulating Oracle Transactions in SQL Server 2005 and Simulating Oracle Autonomous Transactions. Finally, many PL/SQL types do not have equivalents in Transact-SQL. Records and collections are examples of this. SSMA can process most cases of PL/SQL record usage, but support for collections has not yet been implemented. We propose several approaches to the manual emulation of PL/SQL collections in Migrating Oracle Collections and Records.
Data Migration Architecture of SSMA for Oracle

This section describes SSMA Oracle 3.0 components and their interaction during data migration. The components execute on different computers and use Microsoft SQL Server 2005 database objects for communication. This architecture produces the best migration performance and flexibility. Understanding this mechanism can help you set up the proper environment for SSMA data migration. It also helps you to better control, monitor, and optimize the process.
Implementation in SSMA
We based the SSMA for Oracle 3.0 implementation on the SqlBulkCopy class, defined in the .NET Framework 2.0. SqlBulkCopy functionality resembles the bcp utility, which allows transferring large amounts of data quickly and efficiently. Access to the source database is established by the .NET Framework Data Provider for Oracle, which uses the Oracle Call Interface (OCI) from Oracle client software. Optionally, you can use .NET Framework Data Provider for OLE DB, which requires an installed Oracle OLE DB provider. We considered the following when designing SSMA Oracle 3.0 data migration: The data transfer process must run on SQL Server. That limits the number of installed Oracle clients and reduces network traffic. The client application controls the process by using SQL Server stored procedures. Therefore, you do not need any additional communication channels with the server and can reuse the existing server connection for this purpose. All tables that are selected for migration are transferred by a single execution command from the SSMA user. The user monitors the data flow progress and can terminate it at any time.
Solution Layers
Four layers participate in the data migration process: Client application, an SSMA executable Stored procedures that serve as interfaces to all server actions The database layer, which comprises two tables: o o The package information table The status table
The server executable, which starts as part of a SQL Server job, executes the data transfer, and reflects its status
Client Application
SSMA lets users choose an arbitrary set of source tables for migration. The batch size for bulk copy operations is a user-defined setting. When the process starts, the program displays the progress bar and Stop button. If any errors are found, SSMA shows the appropriate error message and terminates the transfer. In addition, the user can press the Stop button to terminate the process. If the transfer is completed normally, SSMA compares the number of rows in each source
with the corresponding target table. If they are equal, the transfer is considered to be successful. As the client application does not directly control the data migration process, SSMA uses a Messages table to receive feedback about the migration status.
Stored Procedures Interface

The following SQL Server stored procedures control the migration process: bcp_save_migration_package writes the package ID and XML parameters into the bcp_migration_packages table. bcp_start_migration_process creates the SQL Server job that starts the migration executable and returns the ID of the job created. bcp_read_new_migration_messages returns the rows added by the migration executable, filtered by known job ID. stop_agent_process stops the migration job, including closing the original connections and killing the migration executable. The data will be migrated partially. bcp_clean_migration_data is a procedure that cleans up a migration job. bcp_post_process is a procedure that runs all post-processing tasks related to the single migrated table.
Database Layer
SSMA uses a Packages table, named [ssma_oracle].[bcp_migration_packages], to store information about the current package. Each row corresponds to one migration run. It contains package GUID and XML that represents RSA-encrypted connection strings and the tables that should be migrated. A Messages table, named [ssma_oracle].[ssmafs_bcp_migration_messages] accumulates messages coming from migration executables during their work.
Migration Executable
The migration application, SSMA for Oracle Data Migration Assistant.exe, is executed on a SQL Server host. The executable's directory is determined during the Extension Pack installation. When bcp_start_migration_package starts the application, it uses hardcoded file names and retrieves the directory name from a server environment variable. When it starts, the migration application gets the package ID from the command string and reads all other package-related information from the Packages table. That information includes source and destination connection strings, and a list of the tables to migrate. Then the tables are processed one at a time. You get source rows via the IDataReader interface and move them to the target table with the WriteToServer method. The BatchSize setting defines the number of rows in a buffer. When the buffer is full, all rows in it are committed to the target. To notify you about the progress of a bulk copy operation, the data migration executable uses the SqlRowsCopied event and NotifyAfter property. When a SqlRowsCopied event is generated, the application inserts new rows, sending information about the progress to the Messages table. The NotifyAfter property
defines the number of rows that are processed before generating a SqlRowsCopied event. This number is 25 percent of the source table's row count. Another type of output recordthe termination messageis written to the Messages table when the application terminates either successfully or because of an exception. In the latter case, the error text is included. If BatchSize = 1, additional information about the columns of the row where the problem occurred is extracted, so that you can locate the problematic row.
Message Handling
The client application receives feedback from the migration executable by means of the Messages table. During migration, the client is in the loop, polling this table and verifying that new rows with the proper package ID appear there. If there are no new rows during a significant period of time, this may indicate problems with the server executable and the process terminates with a time-out message. When the table migration completes, the server executable writes a successful completion message. If the table is large enough, you may see many intermediate messages, which show that the next batch was successfully committed. If an error occurs, the client displays the error message that was received from the server process.
Validation of the Results

Before the migration starts, the client application calculates the number of rows in each table that will be migrated. With this data, you can evaluate the correct progress position. After the migration completes, the client must calculate the target table's row counts. If they are equal, the overall migration result is considered to be successful. Otherwise, the user is notified of the discrepancy and can view the source and destination counts.
Migrating Oracle Data Types

Most data types used in Oracle do not have exact equivalents in Microsoft SQL Server 2005. They differ in scale, precision, length, and functionality. This section explains the data type mapping implemented in SSMA Oracle 3.0, and includes remarks about conversion issues. SSMA supports the ANSI and DB2 types implemented in Oracle, as well as the built-in Oracle types. SSMA type mapping is applied to table columns, subprogram arguments, a function's returned value, and to local variables. Usually the mapping rules are the same for all these categories, but in some cases there are differences. In SSMA, you can adjust mapping rules for some predefined limits. You can establish custom mappings for the whole schema, for specific group of objects, or to a single object on the Oracle view pane's Type Mapping tab (Figure 1).
Figure 1: The Type Mapping tab in Oracle This section does not describe migrating complex data types such as object types, collections, or records. It does not cover ANY types and some specific structures, such as spatial or media types. Oracle allows you to create subtypes that are actually aliases of some basic types. SSMA does not process subtypes, but you can emulate that functionality manually if you can convert the basic type. Generally it is enough to replace the Oracle declaration: SUBTYPE <type-name> IS <basic-type> [NOT NULL] With the SQL Server 2005 declaration: CREATE TYPE <type-name> FROM <basic-type-converted> [NOT NULL] You may need to change the target <type-name> if the subtype is defined in the Oracle package. To establish the scope of this name, add a package prefix such as PackageName$<type-name>.
Numeric Data Types

The basic fixed point numeric type in Oracle is NUMBER(<precision>, <scale>). Its variation for integer numbers is NUMBER(<precision>), and a floating point value can be stored in NUMBER. By default, SSMA maps NUMBER(<precision>, <scale>) to numeric(<precision>, <scale>) and NUMBER(<precision>) to numeric(<precision>). NUMBER becomes float(53), which has the maximum precision from SQL Server floating-point numbers. In Oracle, INTEGER(<precision>) and INTEGER types are treated like NUMBER(<precision>, 0). As SQL Server has a special int type that stores integers more efficiently, SSMA maps INTEGER to int. PL/SQL types such as BINARY_INTEGER and PLS_INTEGER are also mapped to int by default. You may wish to customize the default mapping of numeric types if you know the exact range of actual values. In fact, you can choose any SQL Server numeric type as the target for the mapping. Be cautious when mapping a source type to a type that has less precision, such as NUMBER -> smallint or NUMBER(20) -> int. Doing so could create overflows or loss of precision during data migration or during code execution. In some cases, you may wish to set the precision to larger than the default, such as when mapping INTEGER to bigint. You may find another reason to change default number mappings: when you convert a NUMBER field to a SQL Server identity column. As SQL Server does not support float numbers as identities, change it to an int or numeric type. SSMA recognizes various synonyms of NUMBER types such as NUMERIC, DECIMAL, NATURAL, POSITIVE, DOUBLE_PRECISION, REAL, BINARY_FLOAT, and BINARY_DOUBLE and applies the proper mapping for each one. SIGNTYPE is mapped to smallint to allow storing -1 as a possible value.
Character Data Types

SSMA converts the basic character types VARCHAR2 and CHAR to SQL Server varchar and char, correspondingly preserving their length. If a PL/SQL variable is declared with a constant size greater than 8,000, SSMA maps to varchar(max). If some formal parameter of a procedure or a function has a character type, Oracle does not require that its length be explicitly declared. Meanwhile, SQL Server always wants to know the exact size of varchar or char parameters. As a result, SSMA has no other choice than to apply the maximum length by default. That means that VARCHAR2 or CHAR parameters are automatically declared as varchar(max) in the target code. If you know the exact length of the source data, you can change the default mapping. Use customized mappings when Oracle is configured to store multi-byte strings in VARCHAR2 / CHAR columns or variables. In that case, map the character types to Unicode types in SQL Server. For example: VARCHAR2 CHAR -> nvarchar -> nchar
Otherwise, non-ASCII strings can be distorted during data migration or target code execution. Note that source strings declared as national (NVARCHAR2 and NCHAR) are automatically mapped to nvarchar and nchar.
A similar approach is applied to Oracle RAW strings. This type can be mapped to binary or varbinary (the default), but if their size exceeds the 8,000-byte limit, map them to varbinary(max). SSMA recognizes various synonyms of these types, namely VARCHAR, CHARACTER, CHARACTER VARYING, NATIONAL CHARACTER, NATIONAL CHARACTER VARYING, and STRING.
Date and Time

The default conversion target for DATE is datetime. Note that the SQL Server datetime type can store dates from 01/01/1753 to 12/31/9999. This range is not as wide as Oracles date, which starts from 4712 BC. This can create problems if these early dates are used in the application. However, SQL Server can store contemporary dates more efficiently with the smalldatetime type, which supports dates from 01/01/1900 to 06/06/2079. To customize the mapping, in SSMA choose smalldatetime as the target type. Another Oracle type that holds the date and time is TIMESTAMP. It resembles DATE except that it has greater precision (up to nanoseconds). The SQL Server timestamp is a completely different type not related to a moment in time. Thus, the best way to convert TIMESTAMP is to use the default SSMA mapping to datetime. In most cases, the loss of precision caused by this conversion is acceptable. The current version of SQL Server does not store time zone information in dates. The implementation of datetime in the next version of SQL Server should provide increased precision and time zones. The Oracle INTERVAL data type does not have a corresponding type in SQL Server, but you can emulate any operations with intervals by using the SQL Server functions dateadd and datediff. Their syntax is quite different, and at this moment SSMA does not perform these conversions automatically.
Boolean Type
SQL Server does not have a Boolean type. Statements containing Boolean values are transformed by SSMA to replace the value with conditional expressions. SSMA emulates stored Boolean data by using the SQL Server bit type.
Large Object Types

The best choice for migrating Oracle LOBs (large object types) are new types introduced in SQL Server 2005: varchar(max), nvarchar(max) and varbinary(max). Oracle LONG, CLOB NCLOB LONG RAW, BLOB, BFILE SQL Server 2005 varchar(max) nvarchar(max) varbinary(max)
You can change SSMA mapping to use the older-style text, ntext, and image types, but this is not recommended. SQL Server 2005 operations over new types are simple compared to the approaches in both Oracle and SQL Server 2000. Currently, SSMA does not automatically convert operations on large types. Still, it can migrate the data of all the above types. The BFILE type is somewhat different; since SQL Server does not
10
support the Oracle concept of saving data out of the database, the result of the data migration is that the file contents are loaded into a SQL Server table in binary format. You may consider converting that result into a varchar format if the file is a text file. If the Oracle server supports multi-byte encoding of characters, map LONG and CLOB types to nvarchar(max) to preserve the Unicode characters.
XML Type
The default mapping of the Oracle XMLType is to SQL Server xml. All XML data in XMLType columns can be successfully migrated by using SSMA. Note that XQuery operations on these types are similar in Oracle and SQL Server, but differences exist and you should handle them manually.
ROWID Types
The ROWID and UROWID types are mapped to uniqueidentifier, which is a GUID that could be generated for each row. Before you convert any code that relies on the ROWID pseudocolumn, ensure that SSMA added the ROWID column (see option Generate ROWID column in the SSMA project settings). You can migrate data in columns of ROWID type to SQL Server as is, but their correspondence with the SSMA-generated ROWID column will be broken because uniqueidentifier no longer represents the physical address of a row like it was in Oracle.
Emulating Oracle System Objects

This section describes how SSMA Oracle 3.0 converts Oracle system objects including views, standard functions, and packaged subroutines. You will also find hints about how to convert packages that are currently unsupported.
Converting Oracle System Views

SSMA Oracle 3.0 can convert Oracle system views, which are frequently used. It does not convert columns that are too closely linked with Oracle physical structures or have no equivalent in SQL Server 2005. The following views can be migrated automatically to SQL Server views: ALL_INDEXES DBA_INDEXES ALL_OBJECTS DBA_OBJECTS ALL_SYNONYMS DBA_SYNONYMS ALL_TAB_COLUMNS DBA_TAB_COLUMNS ALL_TABLES DBA_TABLES ALL_CONSTRAINTS DBA_ CONSTRAINTS ALL_SEQUENCES
11
DBA_SEQUENCES ALL_VIEWS DBA_VIEWS ALL_USERS DBA _USERS ALL_SOURCE DBA_SOURCE GLOBAL_NAME ALL_JOBS DBA_ JOBS V$SESSION ALL_EXTENTS V$LOCKED_OBJECT DBA_FREE_SPACE DBA_SEGMENTS
In this section, we describe ways to manually convert the following views:
Location of Generated System View Emulations for SSMA 3.0

Views emulating Oracle DBA_* views and ALL_* views are created in <target_db>.ssma_oracle.DBA_* and <target_db>.ssma_oracle.ALL_*, correspondingly. USER_* views are created in each scheme where these views are used, and they have additional WHERE conditions with the format: OWNER = <target_schema> Note that SSMA creates only those target views that are actually referenced in the generated code. Note In the following code we assume that SSMA creates DBA_* and USER_* views based on ALL_* and therefore we do not describe DBA_* and USER_*in this document. Example CREATE VIEW ssma_oracle.ALL_TRIGGERS AS select UPPER(t.name) as TRIGGER_NAME, UPPER(s.name) as TABLE_OWNER, UPPER(o.name) as TABLE_NAME, CASE WHEN t.is_disabled = 0 THEN 'ENABLED' ELSE 'DISABLED'
12
END as STATUS from sys.triggers t, sys.tables o, sys.schemas AS s where t.parent_id = o.object_id and o.schema_id = s.schema_id GO CREATE VIEW USER1.USER_TRIGGERS AS SELECT * FROM ssma_oracle.ALL_TRIGGERS v WHERE v.OWNER = N'TEST_USER'
CREATE SYNONYM ssma_oracle.DBA_TRIGGERS FOR TEST_DATABASE.ssma_oracle.ALL_TRIGGERS
ALL_INDEXES System View

SSMA converts owner, index_name, index_type, table_owner, table_name, table_type, uniqueness, compression, and prefix_length columns.
ALL_OBJECTS System View

SSMA converts owner, object_name, object_type, created, last_ddl_time, and generated columns.
ALL_SYNONYMS System View

SSMA convert all columns for this view.
ALL_TAB_COLUMNS System View

SSMA converts OWNER, table_name, column_name, DATA_TYPE, data_length, data_precision, data_scale, nullable, and column_id columns.
ALL_TABLES System View

SSMA V3 converts owner and table_name columns.
ALL_CONSTRAINTS System View

SSMA converts owner, constraint_name, constraint_type, table_name, search_condition, r_owner, r_constraint_name, delete_rule, status, deferable, and generated columns.
ALL_SEQUENCES System View

SSMA converts sequence_owner, sequence_name, minvalue, increment_by, cycle_flag, order_flag, cache_size, and last_number columns.
13
ALL_VEWS System View

SSMA converts owner, view_name, text_length, and text columns.
ALL_USERS System View

SSMA converts all columns for this view.
ALL_SOURCE System View

SSMA converts owner, name, and text columns.
GLOBAL_NAME System View

SSMA converts all columns for this view.
ALL_JOBS System View

SSMA converts job, last_date, last_sec, next_date, next_sec, total_time, broken, and what columns.
V$SESSION System View

SSMA converts sid, username, status, schemaname, program, logon_time, and last_call_et columns.
DBA_EXTENTS System View

SSMA does not automatically convert DBA_EXTENTS. You can emulate owner, segment_name, segment_type, bytes, and blocks. The following code produces the result similar to DBA_EXTENTS: insert #extentinfo exec( ' dbcc extentinfo ( 0 ) with tableresults ' ) select UPPER(s.name) AS owner, UPPER(t.name) AS object_name, 'TABLE' AS segment_type, ext_size*8192 as bytes, ext_size as blocks from #extentinfo AS e, sys.tables AS t, sys.schemas AS s WHERE t.schema_id = s.schema_id AND e.obj_id = t.object_id UNION ALL
14
select UPPER(s.name) AS owner, UPPER(i.name) AS object_name, 'INDEX' AS segment_type, ext_size*8192 as bytes, ext_size as blocks from #extentinfo AS e, sys.indexes AS i, sys.tables AS t, sys.schemas AS s WHERE t.schema_id = s.schema_id AND i.object_id = t.object_id AND e.obj_id = t.object_id
V$LOCKED_OBJECT System View

SSMA does not automatically convert V$LOCKED_OBJECT. You can emulate V$LOCKED_OBJECT data by using the following columns in SQL Server 2005: os_user_name, session_id, oracle_username, locked_mode The following view provides the emulation: CREATE VIEW ssma_oracle.V$LOCK_OBJECT AS SELECT s.hostname as OS_USER_NAME, s.spid as SESSION_ID, UPPER(u.name) as ORACLE_USERNAME, CASE WHEN d.request_mode = 'IX' THEN 3 WHEN d.request_mode = 'IS' THEN 2 WHEN d.request_mode = 'X' THEN 6 WHEN d.request_mode = 'S' THEN 4 ELSE 0 END as LOCKED_MODE FROM sys.dm_tran_locks as d LEFT OUTER JOIN (master..sysprocesses as s LEFT OUTER JOIN sysusers as u ON s.uid = u.uid) ON d.request_session_id = s.spid WHERE resource_type = 'OBJECT' and request_mode NOT IN ('Sch-M', 'Sch-S')
15
DBA_FREE_SPACE system view

SSMA does not automatically convert DBA_FREE_SPACE. You can emulate it in SQL Server 2005 in the following columns: file_id, bytes, blocks. The following code performs the emulation: CREATE VIEW DBA_FREE_SPACE AS SELECT a.data_space_id as FILE_ID, SUM(a.total_pages - a.used_pages)*8192 as BYTES, SUM(a.total_pages - a.used_pages) as BLOCKS FROM sys.allocation_units as a GROUP BY a.data_space_id
DBA_SEGMENTS system view

SSMA does not automatically convert the DBA_SEGMENTS view. You can emulate it in SQL Server 2005 with the following columns: owner, segment_name, segment_type, bytes. We propose the following emulation: CREATE VIEW ssma_ora.DBA_SEGMENTS AS SELECT UPPER(s.name) AS owner, UPPER(o.name) AS SEGMENT_NAME, 'TABLE' AS SEGMENT_TYPE, SUM(a.used_pages*8192) as BYTES FROM sys.tables AS o INNER JOIN sys.schemas AS s ON s.schema_id = o.schema_id left join (sys.partitions as p join sys.allocation_units a on p.partition_id = a.container_id left join sys.internal_tables it on p.object_id = it.object_id) on o.object_id = p.object_id WHERE UNION ALL SELECT (o.is_ms_shipped = 0) GROUP BY s.name, o.name
16
UPPER(s.name) AS owner, UPPER(i.name) AS SEGMENT_NAME, 'INDEX' AS OBJECT_TYPE, SUM(a.used_pages*8192) as BYTES FROM sys.indexes AS i INNER JOIN sys.objects AS o ON i.object_id = o.object_id and o.type = 'U' INNER JOIN sys.schemas AS s ON o.schema_id = s.schema_id left join (sys.partitions as p join sys.allocation_units a on p.partition_id = a.container_id left join sys.internal_tables it on p.object_id = it.object_id) on o.object_id = p.object_id GROUP BY s.name, i.name
Converting Oracle System Functions

SSMA converts Oracle system functions to either SQL Server system functions or to user-defined functions from the Microsoft Extension Library for SQL Server. The library is created in the sysdb database when you install the SSMA Extension Pack. The following table lists the Oracle system functions and SQL Server mappings. Function conversion status (S) Y: The function is fully converted. P: The function is partially converted. Type of conversion (T) M: Using standard Transact-SQL mapping. F: Using database user-defined functions. E: Using extended stored procedures. Note The prefix [ssma_oracle] is placed before functions in the sysdb.ssma_oracle schema, as required for SQL Server functions that are part of the Extension Pack installation. Oracle System Function
ABS(p1) ACOS(p1) ADD_MONTHS(p1, p2) ASCII(p1) ASIN(p1) ATAN(p1) BITAND(p1, p2)
S
Y Y Y Y Y Y Y
T
M M M M M M F
Conversion to SQL Server

ABS(p1) ACOS(p1) DATEADD(m, p2, p1) ASCII(p1) ASIN(p1) ATAN(p1) ssma_oracle.BITAND(p1, p2)
Comment
17
Oracle System Function

CAST(p1 AS t1) CEIL(p1) CHR(p1 [USING NCHAR_CS]) COALESCE(p1, ) CONCAT(p1, p2) COS(p1) COSH(p1) CURRENT_DATE
S
Y Y P Y Y Y Y P
T
M M M M M M F M

CAST(p1 AS t1) CEILING(p1) CHAR(p1) COALESCE(p1, ) Into expression (p1 + p2) COS(p1) ssma_oracle.COSH(p1) no spaces are allowed in ssma_ora user name. GETUTCDATE() Currently SSMA does not process CURRENT_DATE correctly.
Comment
USING NCHAR_CS is currently not supported.
Limitation: CURRENT_DATE returns date in the time zone of DB session, but GETUTCDATE() returns UTC only.
DECODE(p1, p2, p3 [, p4]) EXP(p1) EXTRACT(p1 FROM p2)
Y Y P
M M M
CASE p1 WHEN p2 THEN p3 [ELSE p4] END EXP(p1) DATEPART(part-p1, p2) Only p1 = (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is converted. For p1 = (TIMEZONE_HOUR, TIMEZONE_MINUTE, TIMEZONE_REGION, TIMEZONE_ABBR) a message is generated saying that it is impossible to convert.
FLOOR(p1) GREATEST(p1,p2
Y P
M F
FLOOR(p1) ssma_oracle. Function type is based on the p1 data type. If the Oracle source is GREATEST(p1,p2,p3), SSMA transforms it as GREATEST(p1, GREATEST(p2,p3)) and so on.
[,p3pn])
GREATEST_DATETIME(p1, p2) GREATEST_FLOAT(p1, p2) GREATEST_INT(p1, p2) GREATEST_NVARCHAR(p1, p2) GREATEST_REAL(p1, p2)
18

GREATEST_VARCHAR(p1, p2)
Comment
INITCAP(p1)
ssma_oracle. INITCAP _VARCHAR(p1) INITCAP _NVARCHAR(p1)
Function type is based on the p1 data type. Currently supports the following argument types: CHAR, NCHAR, VARCHAR2, NVARCHAR2. For other types, a message is generated. INSTRB, INSTRC, INSTR2, INSTR4 currently not converted.
INSTR(p1,p2[,p3,p4])
ssma_oracle. INSTR2_CHAR(p1, p2) INSTR2_NCHAR(p1, p2) INSTR2_NVARCHAR(p1, p2) INSTR2_VARCHAR(p1, p2) INSTR3_CHAR(p1, p2, p3) INSTR3_NCHAR(p1, p2, p3) INSTR3_NVARCHAR(p1, p2, p3) INSTR3_VARCHAR(p1, p2, p3) INSTR4_CHAR(p1, p2, p3, p4) INSTR4_NCHAR(p1, p2, p3, p4) INSTR4_NVARCHAR(p1, p2, p3, p4) INSTR4_VARCHAR(p1, p2, p3, p4)
LAST_DAY(p1) LEAST(p1, p2 [, p3 pn])
Y P
F F
ssma_oracle.LAST_DAY(p1) ssma_oracle. Function type is based on the p1 data type. If Oracle source is LEAST (p1,p2,p3), SSMA transforms it as LEAST (p1, LEAST (p2,p3)) and so on.
LEAST_DATETIME (p1, p2) LEAST_FLOAT (p1, p2) LEAST_INT (p1, p2) LEAST_NVARCHAR (p1, p2) LEAST_REAL (p1, p2) LEAST_VARCHAR (p1, p2)
19

LENGTH(p1)
S
P
T
F

ssma_oracle.
Comment
LENGTHB, LENGTHC, LENGTH2, LENGTH4 currently not converted. Function type determined based on the p1 data type.
LENGTH_CHAR(p1) LENGTH_NCHAR(p1) LENGTH_NVARCHAR(p1) LENGTH_VARCHAR(p1) LN(p1) LOG(p1, p2) LOWER(p1) LPAD(p1, p2) Y Y Y Y M F M F LOG(p1) ssma_oracle.LOG_ANYBASE(p1, p2) LOWER(p1) ssma_oracle. LPAD_VARCHAR(p1, p2, p3) LPAD_NVARCHAR(p1, p2, p3)
Function type is based on the p1 data type. P3 = (by default). Currently supports the following argument types: CHAR, NCHAR, VARCHAR2, NVARCHAR2. For other types a message is generated. Function type is based on the p1 data type. Currently supports the following argument types: CHAR, NCHAR, VARCHAR2, NVARCHAR2.
LPAD(p1, p2, p3)
ssma_oracle. LPAD_VARCHAR(p1, p2, p3) LPAD_NVARCHAR(p1,p2,p3)
LTRIM(p1) LTRIM(p1, p2)
Y Y
M F
LTRIM(p1) ssma_oracle. LTRIM2_VARCHAR(p1, p2) LTRIM2_NVARCHAR(p1, p2) Function type is based on the p1 data type. Currently supports the following argument types: CHAR, NCHAR, VARCHAR2, NVARCHAR2. No check of parameter data types.
MOD(p1, p2)
M M
Into expression (p1 % p2) DATEDIFF( MONTH, CAST(p2 AS float), CAST( DATEADD(DAY, ( -CAST(DATEPART(DAY, p2) AS float(53)) + 1 ), p1) AS float)) ssma_oracle.NEXT_DAY (p1, p2)
MONTHS_BETWEEN(p1, Y p2)
NEXT_DAY (p1, p2)
20

NEW_TIME(p1, p2, p3) NLS_INITCAP(p1[, p2])
S
Y P
T
F F

ssma_oracle.NEW_TIME(p1, p2, p3) ssma_oracle. NLS_INITCAP_NVARCHAR(p1)
Comment
Only function calls with one argument are currently supported. The type of function is determined by the first argument data type. The following data types of the first argument are currently supported: NCHAR, NVARCHAR2. For other data types a message is generated.
NULLIF(p1, p2) NVL(p1, p2) POWER(p1,p2) RAWTOHEX (p1) REPLACE(p1, p2) REPLACE(p1, p2, p3)
Y Y Y Y P
M M M F M
NULLIF(p1, p2) ISNULL(p1, p2) POWER(p1,p2) ssma_oracle.RAWTOHEX_VARCHAR (p1) REPLACE(p1, p2 , ) REPLACE(p1, p2 , p3) Varchar is supported as returned the value type.
ROUND(p1) [ p1 date ] Y ROUND(p1, p2) [ p1 date ] ROUND(p1) numeric ] [ p1 Y Y Y
ssma_oracle.ROUND_DATE (p1, NULL) ssma_oracle.ROUND_DATE (p1, p2)
F M F
ssma_oracle.ROUND_NUMERIC_0 (p1) ROUND (p1, p2) ssma_oracle. RPAD_VARCHAR(p1, p2, p3) RPAD_NVARCHAR(p1, p2, p3) The type of function is determined by the first argument data type. P3 = (by default). The following data types of the first argument are currently supported: CHAR, NCHAR, VARCHAR2, NVARCHAR2. For other data types a message is generated. The type of function is determined by the first argument data type. The following data types of the
ROUND (p1, p2) [ p1 numeric ] RPAD(p1, p2)
RPAD(p1, p2, p3)
ssma_oracle. RPAD_VARCHAR(p1, p2, p3) RPAD_NVARCHAR(p1,p2,p3)
21
Comment
RTRIM(p1) RTRIM(p1,p2)
Y Y
M F
RTRIM(p1) ssma_oracle. RTRIM2_VARCHAR(p1,p2) RTRIM2_NVARCHAR(p1,p2)
first argument currently supported: CHAR, NCHAR, VARCHAR2, NVARCHAR2. For The function type is based on the p1 data type. Currently supported following argument types are: CHAR, NCHAR, VARCHAR2, NVARCHAR2.
SIGN(p1) SIN(p1) SINH(p1) SQRT(p1) SUBSTR(p1, p2[, p3])
Y Y Y Y P
M M F M F
SIGN(p1) SIN(p1) ssma_oracle.SINH(p1) SQRT (p1) ssma_oracle. SUBSTR2_CHAR(p1,p2) SUBSTR2_NCHAR(p1,p2) SUBSTR2_NVARCHAR(p1,p2) SUBSTR2_VARCHAR(p1,p2) SUBSTR3_CHAR(p1,p2,p3) SUBSTR3_NCHAR(p1,p2,p3) SUBSTR3_NVARCHAR(p1,p2,p3) SUBSTR3_VARCHAR(p1,p2,p3) The function type is based on the p1 data type.
SYS_GUID()
NEWID()
Not guaranteed to work correctly. For example, SELECT SYS_GUID() from dual differs from SELECT NEWID().
SYSDATE TAN(p1) TANH(p1) TO_CHAR(p1) TO_CHAR(p1, p2)
Y Y Y Y P
M M F M F
GETDATE() TAN(p1) ssma_oracle.TANH(p1) CAST(p1 AS CHAR) ssma_oracle. Not guaranteed to work correctly. p1 can have date or numeric
22
Comment
type. Formats currently not supported are E, EE, TZD, TZH, TZR. Allowable numeric formats are comma, period, 0, 9, and fm.
TO_CHAR_DATE (p1, p2) TO_CHAR_NUMERIC (p1, p2) TO_DATE(p1) TO_DATE(p1, p2) TO_NUMBER(p1[, p2[, p3]]) P M P F CAST(p1 AS datetime) ssma_oracle.TO_DATE2 (p1, p2) CAST(p1 AS NUMERIC)
Character value of p1 is not supported.
Only 1- or 2-argument format is converted. Currently supported with only one argument. The conversion is not guaranteed to be fully equivalent. The type of function is determined by the first argument data type. The following data types of the first argument are currently supported: CHAR, NCHAR, VARCHAR2, NVARCHAR2. For other data types a message is generated Currently supported only for p1 of NUMERIC and DATE types.
TRANSLATE(p1, p2, p3) Y
ssma_oracle. TRANSLATE_VARCHAR(p1, p2, p3) TRANSLATE_NVARCHAR(p1, p2, p3)
TRUNC(p1[, p2])
ssma_oracle. TRUNC(p1[, p2]) TRUNC_DATE(p1) TRUNC_DATE2(p1, p2)
TRIM
ssma_oracle.TRIM2, ssma_oracle.TRIM3 SUSER_SID()
The parameters are transformed (see the explanations below). The conversion is not guaranteed to be fully equivalent.
UID
UPPER(p1) USER
Y Y
M M F
UPPER(p1) SESSION_USER ssma_oracle.WIDTH_BUCKET(p1, p2, p3, p4)
WIDTH_BUCKET(p1, p2, Y p3, p4)
23
See the rules for special transformations for some of the Oracle system functions in Converting Oracle System Functions in this document.
TRIM System Function

Oracle TRIM( { { LEADING | TRAILING | BOTH } <trim_character> | <trim_character> } FROM trim_source ) SQL Server sysdb.ssma_oracle.trim3_varchar( { { 1 | 2 | 3 } | 3 }, <trim_character>, <trim_source> ) Oracle TRIM( [ [ LEADING | TRAILING | BOTH ] FROM <trim_source> ] | <trim_source> ) SQL Server sysdb.ssma_oracle.trim2_varchar( [ 1 | 2 | 3 ] | 3, <trim_source> ) Example TRIM function Oracle SELECT TRIM(LEADING FROM ' SELECT TRIM(TRAILING FROM ' SELECT TRIM(BOTH FROM ' SELECT TRIM(' 2234 3452
2234 3452 2234 3452
') FROM dual; ') FROM dual;
2234 3452
') FROM dual;
') FROM dual;
SELECT TRIM(LEADING '2' FROM '2234 3452') FROM dual; SELECT TRIM(TRAILING '2' FROM '2234 3452') FROM dual; SELECT TRIM(BOTH '2' FROM '2234 3452') FROM dual; SELECT TRIM('2' FROM '2234 3452') FROM dual;
24
SQL Server SELECT sysdb.ssma_oracle.TRIM2_VARCHAR(1, ' SELECT sysdb.ssma_oracle.TRIM2_VARCHAR(2, ' SELECT sysdb.ssma_oracle.TRIM2_VARCHAR(3, ' SELECT sysdb.ssma_oracle.TRIM2_VARCHAR(3, '
2234 3452 2234 3452 2234 3452 2234 3452
') ') ') ')
SELECT sysdb.ssma_oracle.TRIM3_VARCHAR(1, '2', '2234 3452') SELECT sysdb.ssma_oracle.TRIM3_VARCHAR(2, '2', '2234 3452') SELECT sysdb.ssma_oracle.TRIM3_VARCHAR(3, '2', '2234 3452') SELECT sysdb.ssma_oracle.TRIM3_VARCHAR(3, '2', '2234 3452')
USERENV System Function

To convert function USERENV('SESSIONID') use the @@SPID function. Example Oracle SELECT USERENV('SESSIONID') FROM dual; SQL Server SELECT @@SPID To convert function USERENV('TERMINAL') use the host_name() function. Example Oracle SELECT USERENV('TERMINAL') FROM dual; SQL Server SELECT host_name()
NVL2 System Function

To convert function NVL2 use CASE-expression: Example Oracle NVL2(<expr1>, <expr2>, <expr3>) SQL Server CASE WHEN (<expr1> IS NULL) THEN <expr3> ELSE <expr2> END
25
Converting Oracle System Packages

This section covers the migration of commonly used subroutines in Oracle standard packages. Some of the modules are migrated automatically by SSMA, and some should be handled manually. Examples illustrate our approach for the conversion.
DBMS_SQL Package
SSMA automatically covers cases where: The dynamic SQL is processed manually. The statement is not SELECT. Conversion to SQL Server
[ssma_oracle].DBMS_SQL_OPEN_CURSOR()
Oracle Function or Procedure

OPEN_CURSOR()
Comment
The conversion is not guaranteed to be fully equivalent. The conversion is not guaranteed to be fully equivalent. The conversion is not guaranteed to be fully equivalent. The conversion is not guaranteed to be fully equivalent.
PARSE(p1,p2,p3)
[ssma_oracle].DBMS_SQL_PARSE p1,p2,p3
EXECUTE(p1)
[ssma_oracle].DBMS_SQL_EXECUTE (p1)
CLOSE_CURSOR(p1)
[ssma_oracle].DBMS_SQL_CLOSE_CURSOR (p1)
Example Oracle declare cur int; ret int; begin cur := dbms_sql.open_cursor(); dbms_sql.parse(cur, 'ALTER TABLE t1 ADD COLUMN4 NUMBER', dbms_sql.NATIVE); ret := dbms_sql.execute(cur); dbms_sql.close_cursor(cur); end; SQL Server Declare @cur numeric(38),
26
@ret numeric(38) begin set @cur = sysdb.ssma_oracle.dbms_sql_open_cursor() declare @param_expr_2 integer set @param_expr_2 = sysdb.ssma_oracle.getpv_const_integer('sys', 'dbms_sql', 'native') exec sysdb.ssma_oracle.dbms_sql_parse @cur, 'ALTER TABLE t1 ADD COLUMN4 float(53)', @param_expr_2 set @ret = sysdb.ssma_oracle.dbms_sql_execute(@cur) exec sysdb.ssma_oracle.dbms_sql_close_cursor @cur end
DBMS_OUTPUT package
SSMA can handle commonly used PUT_LINE functions. Oracle function or procedure
PUT_LINE(p1)
T
M

PRINT p1
Comment
The conversion is not guaranteed to be fully equivalent.
Example Oracle declare tname varchar2(255); begin tname:='Hello, world!'; dbms_output.put_line(tname); end; SQL Server DECLARE @tname varchar(255) BEGIN SET @tname = 'Hello, world!' PRINT @tname END
27
UTL_FILE Package
The following table lists the UTL_FILE subprograms that SSMA processes automatically. Oracle function or procedure
IS_OPEN(p1) FCLOSE(p1) FFLUSH (p1) FOPEN ( p1,p2,p3, p4) GET_LINE PUT PUTF(p1, p2) PUT_LINE
T
S S S S S S S S

UTL_FILE_IS_OPEN(p1) UTL_FILE_FCLOSE p1 UTL_FILE_FFLUSH p1 UTL_FILE_FOPEN$IMPL(p1,p2,p3,p4,p5) UTL_FILE_GET_LINE(p1,p2,p3) UTL_FILE_PUT(p1,p2) UTL_FILE_PUTF(p1,p2) UTL_FILE_PUT_LINE(p1,p2)
Comment
p5 return value p2 return value
Example Oracle DECLARE outfile utl_file.file_type; my_world varchar2(4) := 'Zork'; V1 VARCHAR2(32767); Begin outfile := utl_file.fopen('USER_DIR','1.txt','w',1280); utl_file.put_line(outfile,'Hello, world!'); utl_file.PUT(outfile, 'Hello, world NEW! '); UTL_FILE.FFLUSH (outfile); IF utl_file.is_open(outfile) THEN Utl_file.fclose(outfile); END IF; outfile := utl_file.fopen('USER_DIR','1.txt','r'); UTL_FILE.GET_LINE(outfile,V1,32767); DBMS_OUTPUT.put_line('V1= '||V1); IF utl_file.is_open(outfile) THEN
28
Utl_file.fclose(outfile); END IF; End write_log_file; SQL Server DECLARE @outfile XML, @my_world varchar(4), @V1 varchar(max) SET @my_world = 'Zork' BEGIN EXEC sysdb.ssma_oracle.UTL_FILE_FOPEN$IMPL 'USER_DIR', '1.txt', 'w', 1280, @outfile OUTPUT EXEC sysdb.ssma_oracle.UTL_FILE_PUT_LINE @outfile, 'Hello, world!' EXEC sysdb.ssma_oracle.UTL_FILE_PUT @outfile, 'Hello, world NEW! ' EXEC sysdb.ssma_oracle.UTL_FILE_FFLUSH @outfile IF (sysdb.ssma_oracle.UTL_FILE_IS_OPEN(@outfile) <> /* FALSE */ 0) EXEC sysdb.ssma_oracle.UTL_FILE_FCLOSE @outfile EXEC sysdb.ssma_oracle.UTL_FILE_FOPEN$IMPL 'USER_DIR', '1.txt', 'r', 1024, @outfile OUTPUT EXEC sysdb.ssma_oracle.UTL_FILE_GET_LINE @outfile, @V1 OUTPUT, 32767 PRINT ('V1= ' + isnull(@V1, '')) IF (sysdb.ssma_oracle.UTL_FILE_IS_OPEN(@outfile) <> /* FALSE */ 0) EXEC sysdb.ssma_oracle.UTL_FILE_FCLOSE @outfile END
29
DBMS_UTILITY Package
SSMA supports only the GET_TIME function. Oracle function or procedure
GET_TIME
T
M

SELECT CONVERT(NUMERIC(38, 0), (CONVERT(NUMERIC(38, 10), getdate()) * 8640000))
Comment
DBMS_SESSION Package
SSMA supports only the UNIQUE_SESSION_ID function. Oracle function or procedure
UNIQUE_SESSION_ID
T
M

[sysdb].ssma_oracle.unique_session_id()
Comment
Return value is different
DBMS_PIPE Package
SSMA 3.0 does not convert the DBMS_PIPE system package. To emulate it manually, follow these suggestions. The DBMS_PIPE package has the following subprograms: function Create_Pipe() procedure Pack_Message() function Send_Message() function Receive_Message() function Next_Item_Type() procedure Unpck_Message() procedure Remove_Pipe() procedure Purge() procedure Reset_Buffer() function Unique_Session_Name()
Use a separate table to store data that is transferred via pipe. Heres an example: Use sysdb Go Create Table sysdb.ssma.Pipes( ID Bigint Not null Identity(1, 1), PipeName Varchar(128) Not Null Default 'Default', DataValue Varchar(8000) ); go Grant Select, Insert, Delete On sysdb.ssma.Pipes to public
30
Go The pack-send and receive-unpack commands are usually used in pairs. Therefore, you can do the following replacement: Oracle s := dbms_pipe.receive_message('<Pipe_Name>'); if s = 0 then dbms_pipe.unpack_message(chr); end if; SQL Server DECLARE @s bigint, @chr varchar(8000) BEGIN SET @chr = '' Select @s = Min(ID) from sysdb.ssma.Pipes where PipeName = '<Pipe_Name>' If @s is not null Begin Select @chr = DataValue From sysdb.ssma.Pipes where ID = @s Delete From sysdb.ssma.Pipes where ID = @s End Oracle dbms_pipe.pack_message(info); status := dbms_pipe.send_message('<Pipe_Name>'); SQL Server Insert Into sysdb.ssma.Pipes (PipeName, DataValue) Values ('<Pipe_Name>', @info) Follow these recommendations to emulate the work of this package: Create_Pipe(). Can be ignored. Pack_Message(), Unpack_Message(). Add storage as a buffer or ignore. Send_Message(), Receive_Message(). Will be emulated as insert/select on the Pipes table (as shown in earlier example code). Next_Item_Type(). Will demand to add datatype field to your Pipes table.
31
Remove_Pipe() Emulate as Delete From Pipes where PipeName = '<PipeName>' Purge(). In our emulation, this means the same as Remove_Pipe(). Reset_Buffer(). Needed if you emulate the buffer (and pack and unpack procedures). Unique_Session_Name(). Return session name. Possible to emulate it as SessionID.
DBMS_LOB Package
SSMA does not automatically convert the DBMS_LOB package. This section contains suggestions for its possible emulation. First we analyze the following DBMS_LOB package procedures and functions: DBMS_LOB.READ DBMS_LOB.WRITE DBMS_LOB.GETLENGTH DBMS_LOB.SUBSTR DBMS_LOB.WRITEAPPEND DBMS_LOB.OPEN DBMS_LOB.CLOSE
Lets examine each in more detail. DBMS_LOB.READ Procedure dbms_lob$read_clob procedure emulate work with CLOB type. dbms_lob$read_blob procedure emulate work with BLOB, BFILE type. CREATE PROCEDURE dbms_lob$read_clob @lob_loc VARCHAR(MAX), @amount INT OUTPUT, @offset INT, @buffer VARCHAR(MAX) OUTPUT as BEGIN SET @buffer = substring(@lob_loc, @offset, @amount) END; GO CREATE PROCEDURE dbms_lob$read_blob @lob_loc VARBINARY(MAX), @amount INT OUTPUT,
32
@offset INT, @buffer VARBINARY(MAX) OUTPUT as BEGIN SET @buffer = substring(@lob_loc, @offset, @amount) END; GO DBMS_LOB.WRITE Procedure Again, we have different variants for clob and blob. CREATE PROCEDURE dbms_lob$write_clob @lob_loc VARCHAR(MAX) OUTPUT, @amount INT, @offset INT, @buffer VARCHAR(MAX) as BEGIN SET @lob_loc = STUFF(@lob_loc, @offset, @amount, @buffer) END; GO CREATE PROCEDURE dbms_lob$write_blob @lob_loc VARBINARY(MAX) OUTPUT, @amount INT, @offset INT, @buffer VARBINARY(MAX) as BEGIN SET @lob_loc = CAST(STUFF(@lob_loc, @offset, @amount, @buffer) as VARBINARY(MAX)) END; Example Oracle DECLARE clob_selected clob_updated CLOB; CLOB;
33
read_amount read_offset write_amount write_offset buffer BEGIN
INTEGER; INTEGER; INTEGER; INTEGER; VARCHAR2(20);
SELECT ad_sourcetext INTO clob_selected FROM Print_media WHERE ad_id = 20020; SELECT ad_sourcetext INTO clob_updated FROM Print_media WHERE ad_id = 20020 FOR UPDATE; read_amount := 10; read_offset := 1; dbms_lob.read(clob_selected, read_amount, read_offset, buffer); dbms_output.put_line('clob_selected value: ' || buffer); write_amount := 3; write_offset := 5; buffer := 'uuuu'; dbms_lob.write(clob_updated, write_amount, write_offset, buffer); INSERT INTO PRINT_MEDIA VALUES (20050, clob_updated); COMMIT; END; SQL Server DECLARE @clob_selected @clob_updated @read_amount @read_offset @write_amount VARCHAR(MAX), VARCHAR(MAX), INT, INT, INT,
34
@write_offset @buffer
INT, VARCHAR(20)
SELECT @clob_selected = ad_sourcetext FROM Print_media WHERE ad_id = 20020; SELECT @clob_updated = ad_sourcetext FROM Print_media WHERE ad_id = 20020 SET @read_amount = 10; SET @read_offset = 1; EXECUTE dbms_lob$read_clob @clob_selected, @read_amount OUTPUT, @read_offset, @buffer OUTPUT PRINT'clob_selected value: ' + @buffer SET @write_amount = 3; SET @write_offset = 5; SET @buffer = 'uuuu'; EXECUTE dbms_lob$write_clob @clob_updated OUTPUT, @write_amount, @write_offset, @buffer INSERT INTO PRINT_MEDIA VALUES (20050, @clob_updated); IF @@TRANCOUNT > 0 COMMIT WORK DBMS_LOB.GETLENGTH Function CREATE FUNCTION dbms_lob$getlength_clob ( @lob_loc VARCHAR(MAX) ) RETURNS BIGINT as BEGIN RETURN(LEN(@lob_loc)) END; GO CREATE FUNCTION dbms_lob$getlength_blob (
35
@lob_loc VARBINARY(MAX) ) RETURNS BIGINT as BEGIN RETURN(LEN(@lob_loc)) END; GO DBMS_LOB.SUBSTR Function CREATE FUNCTION dbms_lob$substr_clob ( @lob_loc VARCHAR(MAX), @amount INT as BEGIN RETURN(substring(@lob_loc, @offset, @amount)) END; GO CREATE FUNCTION dbms_lob$substr_blob ( @lob_loc VARBINARY(MAX), @amount INT as BEGIN RETURN(substring(@lob_loc, @offset, @amount)) END; GO DBMS_LOB.WRITEAPPEND Procedure CREATE PROCEDURE dbms_lob$writeappend_clob @lob_loc VARCHAR(MAX) OUTPUT, @amount INT, @buffer VARCHAR(MAX) as BEGIN SET @lob_loc = @lob_loc + ISNULL(SUBSTRING(@buffer, 1, @amount),'') END; = 32767, @offset INT) RETURNS VARBINARY(MAX) = 32767, @offset INT) RETURNS VARCHAR(MAX)
36
GO CREATE PROCEDURE dbms_lob$writeappend_blob @lob_loc VARBINARY(MAX) OUTPUT, @amount INT, @buffer VARBINARY(MAX) as BEGIN SET @lob_loc = @lob_loc + ISNULL(SUBSTRING(@buffer, 1, @amount), CAST('' as VARBINARY(max))) END; GO DBMS_LOB.OPEN Procedure Ignore the DBMS_LOB.OPEN procedure during the conversion. DBMS_LOB.CLOSE Procedure Ignore the DBMS_LOB.CLOSE procedure during the conversion. Example Oracle CREATE PROCEDURE PrintBLOB_proc ( Dest_loc CLOB, Src_loc CLOB ) IS BEGIN /* Opening the LOB is optional: */ DBMS_LOB.OPEN (Dest_loc, DBMS_LOB.LOB_READWRITE); DBMS_LOB.OPEN (Src_loc, DBMS_LOB.LOB_READONLY); dbms_output.put_line(DBMS_LOB.getlength(Dest_loc)); dbms_output.put_line(DBMS_LOB.getlength(Src_loc)); /* Closing the LOB is mandatory if you have opened it: */ DBMS_LOB.CLOSE (Dest_loc); DBMS_LOB.CLOSE (Src_loc); END; SQL Server CREATE PROCEDURE PrintBLOB_proc
37
@Dest_loc VARCHAR(MAX), @Src_loc VARCHAR(MAX) AS BEGIN PRINT DBMS_LOB$getlength(@Dest_loc) PRINT DBMS_LOB$getlength(@Src_loc) END
DBMS_JOB System Package

Both Oracle and SQL Server support jobs, but how they are created and executed is quite different. The following example shows how to create the equivalent to an Oracle job in SQL Server. The subroutines discussed are: Submit a job to the job queue: DBMS_JOB.SUBMIT ( <job_id> OUT binary_integer, <what> IN varchar2, <next_date> IN date DEFAULT defaultsysdate, <interval> IN varchar2 DEFAULT 'NULL', <no_parse> IN boolean DEFAULT false, <instance> IN DEFAULT any_instance, <force> IN boolean DEFAULT false); Remove a job from the queue: DBMS_JOB.REMOVE (<job_id> IN binary_integer); Where: <job_id> is the identifier of the job just created; usually it is saved by the program and used afterwards to reference this job (in a REMOVE statement). <what> is the string representing commands to be executed by the job process. To run it, Oracle puts this parameter into a BEGINEND block, like this: BEGIN <what> END. <next_date> is the moment when the first run of the job is scheduled. <interval> is a string with an expression of DATE type, which is evaluated during the job run. Its value is the date + time of the next run. The <instance> and <force> parameters are related to the Oracle clustering mechanism and we ignore them here. Also, we dont convert the <no_parse> parameter, which controls when Oracle parses the command. Note Convert the <what> and <interval> dynamic SQL strings independently. The important thing is to add the [database].[owner] qualifications to all object names
38
that are referenced by this code. This is necessary because DB defaults are not effective during job execution. Convert the SUBMIT and REMOVE routines into sysdb database procedures named DBMS_JOB_SUBMIT and DBMS_JOB_REMOVE, respectively. In addition, create a new special wrapper procedure _JOB_WRAPPER for implementing intime evaluations and scheduling the next run. Note that Oracle and SQL Server use different identification schemes for jobs. In Oracle, the job is identified by sequential binary integer (job_id). In SQL Server, job identification is by uniqueidentifier job_id and by unique job name. In our emulation scheme, we create three SQL Server stored procedures: DBMS_JOB_SUBMIT procedure This SQL Server procedure creates a job and schedules its first execution. Find the full text of the procedure later in this section. To submit a job under SQL Server: 1. Create a job and get its identifier by using sp_add_job. 1. Add an execution step to the job by using sp_add_jobstep (we use a single step). 2. Attach the job to the local server by using sp_add_jobserver. 3. Schedule the first execution by using sp_add_jobschedule (we use one-time execution at the specific time). To save Oracle job information, we store Oracle <job_id> in the Transact-SQL job_name parameter and the <what> command as job description. There is some limitation here because the job description is nvarchar(512), so we cannot convert any command that is longer than 512 Unicode characters. The MS SQL identifier is generated automatically as job_id during execution of sp_add_job. DBMS_JOB_REMOVE procedure This procedure locates the SQL Server job ID by using the supplied Oracle job number, and removes the job and all associated information by using sp_delete_job. JOB_WRAPPER procedure This procedure executes the job command and changes the job schedule so that the next run is set according to the <interval> parameter.
DBMS_JOB.SUBMIT
Convert a call to the SUBMIT procedure into the following SQL Server code:
EXEC DBMS_JOB_SUBMIT <job-id-ora> OUTPUT, <ms-command>, <next_date>, <interval>, <ora_command>

Where: <job-id-ora> is the Oracle-type job number; its declaration must be present in the source program.
39
<ms-command> is the command in the source <what> parameter (dynamic SQL statement) that is converted to SQL Server independently. If the converted code contains several statements, divide them with semicolons (;). Because <mscommand> will run out of the current context (asynchronously inside of the_JOB_WRAPPER procedure), put all generated declarations into this string. <next_date> is the date of first scheduled run. Convert it as normal date expression. <interval> is the string with a dynamic SQL expression, which is evaluated at each job run to get the next execution date / time. Like <ms-command>, convert it to the corresponding SQL Server expression. <ora_command> is the parameter that is not present in Oracle format. This is the original <what> parameter without any changes. You save it for reference purposes.
Note that the <no_parse>, <instance>, and <force> parameters are not included in the converted statement. Instead we use the new <ora_command> item.
DBMS_JOB.REMOVE
Convert a call to the REMOVE procedure into the following code: EXEC DBMS_JOB_REMOVE <job-id-ora> Where <job-id-ora> is the Oracle-type number of the job that you want to delete. The source program must supply its declaration.
Example of an Oracle Job Conversion

1. Submit a job Oracle PL/SQL Table the job will modify: Procedure executed at each step: create table ticks (d date); create or replace procedure ticker (curr_date date) as begin insert into ticks values (curr_date); commit; end; Job submitting: declare j number; sInterval varchar2(50); begin sInterval := 'sysdate + 1/8640'; -- 10 sec dbms_job.submit(job => j, what => 'ticker(sysdate);', next_date => sysdate + 1/8640, -- 10 sec interval => sInterval);
40
dbms_output.put_line('job no = ' || j); end; SQL Server In this example, commands are executed by the sa user in the AUS database:
use AUS go
Table the job will modify:
create table ticks (d datetime) go

Procedure executed at each step:
create procedure ticker (@curr_date datetime) as begin insert into ticks values (@curr_date); end; go
Job submitting:
declare @j float(53), @sInterval varchar(50) begin set @sInterval = 'getdate() + 1./8640' currently by the converter a bug]
--[dot is not added
/* parameter calculation is normally generated by the converter*/ declare @param_expr_0 datetime set @param_expr_0 = getdate() + 1./8640 -- 10 sec /* note AUS.DBO.ticker */ exec DBMS_JOB_SUBMIT @j OUTPUT, N'DECLARE @param_expr_1 DATETIME; SET @param_expr_1 = getdate(); EXEC AUS.DBO.TICKER @param_expr_1', @param_expr_0, @sInterval, N'ticker(sysdate);' /* parameter to save the original command */ print 'job no = ' + cast (@j as varchar) end go
2. Locate and remove a job This solution uses emulation of the Oracle USER_JOBS system view, which can be generated by SSMA Oracle 3.0. Oracle
41
declare j number; begin SELECT job INTO j FROM user_jobs WHERE (what = 'ticker(sysdate);'); dbms_output.put_line(j); dbms_job.remove(j); end; SQL Server
declare @j float(53); begin SELECT @j = job FROM USER_JOBS WHERE (what = 'ticker(sysdate);'); -- note Oracle expression left here print @j exec DBMS_JOB_REMOVE @j end
3. Source of new sysdb procedures
------------------------S U B M I T------------------create procedure DBMS_JOB_SUBMIT ( @p_job_id int OUTPUT, -- Oracle job id @p_what nvarchar(4000), -- command converted to SQL Server @p_next_date datetime, -- date of the first run @p_interval nvarchar(4000),-- interval expression converted to SQL Server @p_what_ora nvarchar(512) -- original Oracle command ) as begin declare @v_name nvarchar(512), @v_job_ora int, @v_job_ms uniqueidentifier, @v_command nvarchar(4000), @v_buf varchar(40), @v_nextdate int, @v_nexttime int -- 1. Create new job select @v_job_ora = max( case isnumeric(substring(name,6,100)) when 1 then cast(substring(name,6,100) as int) else 0 end
42
) from msdb..sysjobs where substring(name,1,5)='_JOB_' set @v_job_ora = isnull(@v_job_ora,0) + 1 set @v_name = '_JOB_' + cast(@v_job_ora as varchar(12)) exec msdb..sp_add_job @job_name = @v_name, @description = @p_what_ora, command for reference @job_id = @v_job_ms OUTPUT -- 2. Add a job step set @v_command = N'exec _job_wrapper ''' + cast(@v_job_ms as varchar(40)) + ''', N''' + @p_what + ''', N''' + @p_interval +'''' exec msdb..sp_add_jobstep @job_id = @v_job_ms, @step_name = N'oracle job emulation', @command = @v_command -- 3. Attach to local server exec msdb..sp_add_jobserver @job_id = @v_job_ms, @server_name = N'(LOCAL)' -- 4. Make schedule for the first run /* date format is YYYY-MM-DD hh:mm:ss */ set @v_buf = convert(varchar, @p_next_date, 20) set @v_nextdate = substring(@v_buf,1,4)+substring(@v_buf,6,2)+substring(@v_buf,9,2 ) set @v_nexttime = substring(@v_buf,12,2)+substring(@v_buf,15,2)+substring(@v_buf,1 8,2) exec msdb..sp_add_jobschedule @job_id = @v_job_ms, @name = 'oracle job emulation', @freq_type = 1, @freq_subday_type = 1, @active_start_date = @v_nextdate, @active_start_time = @v_nexttime
-- saving non-converted Oracle
43
end go -----------------------------R E M O V E----------------------------use sysdb go create procedure DBMS_JOB_REMOVE ( @p_job_id int -- Oracle-style job id ) as begin declare @v_job_id uniqueidentifier -- SQL Server job id select @v_job_id = job_id
from msdb..sysjobs
where name = '_JOB_' + cast(@p_job_id as varchar(12)) if @v_job_id is not null exec msdb..sp_delete_job @v_job_id end go --------------------------W R A P P E R-----------------------------use sysdb go create procedure _JOB_WRAPPER ( @p_job_id_ms uniqueidentifier, @p_what nvarchar(512), @p_interval nvarchar(4000) ) as begin declare @v_command nvarchar(4000), @v_buf varchar(40), @v_nextdate int, @v_nexttime int -- 1. Execute job command execute (@p_what) -- 2. Evaluate next run date
44
set @v_command = 'set @buf = convert(varchar, ' + @p_interval + ', 20)' exec sp_executesql @v_command, N'@buf varchar(40) output', @v_buf output -- 3. Redefine the schedule /* ODBC date format: YYYY-MM-DD hh:mm:ss */ set @v_nextdate = substring(@v_buf,1,4)+substring(@v_buf,6,2)+substring(@v_buf,9,2 ) set @v_nexttime = substring(@v_buf,12,2)+substring(@v_buf,15,2)+substring(@v_buf,1 8,2) exec msdb..sp_update_jobschedule @job_id = @p_job_id_ms, @name = 'oracle job emulation', @enabled = 1, @freq_type = 1, @freq_subday_type = 1, @active_start_date = @v_nextdate, @active_start_time = @v_nexttime end
Converting Nested PL/SQL Subprograms

Oracle allows nesting PL/SQL subprogram (procedure or function) definitions within another subprogram. These subprograms can be called only from inside the PL/SQL block or the subprogram in which they were declared. There are no special limitations for parameters or the functionality of nested procedures or functions. That means that any of these subprograms can in turn include other subprogram declarations, which makes multiple levels of nesting possible. In addition, the nested modules can be overloaded; that is, they can use the same name a few times with different parameter sets. Microsoft SQL Server 2005 does not provide similar functionality. It is possible to create a standalone SQL Server procedure or function that emulates Oracle nested subprograms. But doing so presents the problem of how to handle local variables. In PL/SQL, a nested subprogram declared at level N has full access to all local variables declared at levels N, N-1, . . . 1. In SQL Server, the local declarations of other procedures are not visible. SSMA Oracle 3.0 cannot handle this issue, so you must resolve the problem manually. You have two possible solutions: If the nested modules are small enough, just expand each call of the nested module with its contents. In this case, you have only one target procedure and therefore all local declarations are accessible. (See the next section, Inline Substitution.)
45
For large procedures and a relatively limited number of local variables, pass all local stuff to the nested procedure and back as input and/or output parameters. You can also emulate functions this wayif they dont create side effects by modifying the local variables. (See Emulation by Using Transact-SQL Procedures later in this document.)
Inline Substitution
In the first solution, a nested module itself is not converted to any target object, but each call of the module should be expanded to inline blocks in the outermost subprogram. Form the inline block according to the following pattern: <parameter_declaration> <return_value_parameter_declaration> <parameters_assignments> <module_body> <output_parameters_assignments> <return_value_assignment> Next is the body of a procedure or a function. Convert this in compliance with common procedure/function conversion principles. You can use SSMA at this step: <parameter_declaration> is a set of declare statements for input/output parameters variables <return_value_parameter_declaration> is the declare statement for the return parameter <parameters_assignments> are SET statements assigning input or default values to parameter variables <module_body> If the body has the return statement, it should be converted into a SET statement in the <return_value_assignment> section: <output_parameters_assignments> are SET statements assigning values to output parameter variables <return_value_assignment> is SET statement assigning value to the return parameter To create this solution you generate additional variables. The nested modules variable name at the target can be constructed as a concatenation of the main module name, nested module name, the variable name, and the serial number in the case of multiple calls of the module: @[<main_module_name>$. . .]<nested_module_name>$<variable_name><N>
46
In the rare case when the length of the generated variable name formed after the given pattern exceeds 128 symbols, the nested module variable name can be formed as a concatenation of its source name and a number that is unique within the scope of outermost module. Example 1: Simple usage of a local module The first example creates additional variables for the parameters dept_id, checked and the local variable lv_sales. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int; procedure DeptSales(dept_id int, checked int:=0) is lv_sales int; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year and chk = checked; dept_sales := lv_sales; end DeptSales; begin DeptSales(100); DeptSales(200,1); end Proc1; SQL Server CREATE AS declare @on_year int set @on_year = 2000 declare @dept_sales int declare @DeptSales$lv_sales1 int declare @DeptSales$dept_id1 int declare @DeptSales$checked1 int set @DeptSales$dept_id1 = 100 PROCEDURE Proc1
47
set @DeptSales$checked1 = 0 select @DeptSales$lv_sales1 = sales from departmentsales where id = @DeptSales$dept_id1 AND year = @on_year and checked = @DeptSales$checked1 set @dept_sales = @DeptSales$lv_sales1 declare @DeptSales$lv_sales2 int declare @DeptSales$dept_id2 int declare @DeptSales$checked2 int set @DeptSales$dept_id2 = 200 set @DeptSales$checked1 = 1 select @DeptSales$lv_sales = sales from departmentsales where id = @DeptSales$dept_id2 AND year = @on_year and checked = @DeptSales$checked2 set @dept_sales = @DeptSales$lv_sales2 RETURN Example 2 Example 2 adds another call level to the Dept_Sales procedure. Note that the target code has not changed. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int; procedure DeptSales(dept_id int, checked int:=0) is lv_sales int; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year and chk = checked; dept_sales := lv_sales; end DeptSales; procedure DeptSales_300 is begin
48
DeptSales(300); end DeptSales_300; begin DeptSales(100); DeptSales_300; end Proc1; SQL Server CREATE AS declare @on_year int set @on_year = 2000 declare @dept_sales int declare @DeptSales$lv_sales1 int declare @DeptSales$dept_id1 int declare @DeptSales$checked1 int set @DeptSales$checked1 = 0 set @DeptSales$dept_id1 = 100 select @DeptSales$lv_sales1 = sales from departmentsales where id = @DeptSales$dept_id1 AND year = @on_year and checked = @DeptSales$checked1 set @dept_sales = @DeptSales$lv_sales1 declare @DeptSales$lv_sales2 int declare @DeptSales$dept_id2 int declare @DeptSales$checked2 int set @DeptSales$checked2 = 0 set @DeptSales$dept_id2 = 300 select @DeptSales$lv_sales = sales from departmentsales where id = @DeptSales$dept_id2 AND year = @on_year and checked = @DeptSales$checked2 set @dept_sales = @DeptSales$lv_sales2 RETURN PROCEDURE Proc1
49
Example 3 The third example illustrates what you should do with overloaded procedures. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int := 0; procedure DeptSales(dept_id int) is lv_sales int; procedure Add is dept_sales := dept_sales + lv_sales; end Add; procedure Add(i int) is dept_sales := dept_sales + i; end Add; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; Add; Add(200); end DeptSales; begin DeptSales(100); end Proc1; SQL Server CREATE AS declare @on_year int set @on_year = 2000 declare @dept_sales int declare @DeptSales$lv_sales1 int declare @DeptSales$dept_id1 int set @DeptSales$dept_id1 = 100 PROCEDURE Proc1
50
select @DeptSales$lv_sales1 = sales from departmentsales where id = @DeptSales$dept_id1 AND year = @on_year set @dept_sales = @dept_sales + @DeptSales$lv_sales1; declare @DeptSales$Add$OVR2$i int set @DeptSales$Add$OVR2$i = 200; set @dept_sales = @dept_sales + @DeptSales$Add$OVR2$i Example 4 To convert an output parameter, add an assignment statement that saves the output value stored in the intermediate variable. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int; procedure DeptSales(dept_id int, lv_sales out int) is begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; end DeptSales; begin DeptSales(dept_sales); end Proc1; SQL Server CREATE AS declare @on_year int set @on_year = 2000 declare @dept_sales int declare @DeptSales$dept_id1 int declare @DeptSales$lv_sales1 int set @DeptSales$dept_id1 = 100 set @DeptSales$lv_sales1 = @dept_sales select @DeptSales$lv_sales1 = sales from departmentsales PROCEDURE Proc1
51
where id = @DeptSales$dept_id1 AND year = @on_year set @dept_sales = @DeptSales$lv_sales1 RETURN Example 5 Handling a function return value is similar to the output parameter. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int; function DeptSales(dept_id int) return int is lv_sales int; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; return lv_sales; end DeptSales; begin dept_sales := DeptSales(100); end Proc1; SQL Server CREATE AS declare @on_year int set @on_year = 2000 declare @dept_sales int declare @DeptSales$dept_id1 int declare @DeptSales$lv_sales1 int set @DeptSales$dept_id1 = 100 select @DeptSales$lv_sales1 = sales from departmentsales where id = @DeptSales$dept_id1 AND year = @on_year PROCEDURE Proc1
52
set @dept_sales = @DeptSales$lv_sales1 RETURN
Emulation by Using Transact-SQL Subprograms

To convert nested PL/SQL subprograms when you are working with large procedures with a limited number of variables, you convert all nested subprograms into stored procedures and functions with special naming rules. Pass variables of the outer module that are used by the modules that are declared in it as parameters of the module call. Analyze the original module and collect the following information: A list of all locally declared subroutines References of each nested subroutine to outer modules Calls of each nested module from other modules A list of the variables and parameters of outer modules used in each nested module Type of access to the external variables in a nested modulethe type can be read/write or read-only
After that, create a set of procedures that emulate Oracle nested modules and have additional input/output parameters for access to external variables. Pass external variables as output parameters in a nested module call in the following cases: The variable is used at the left side of assignment operator: var1 := . . . The variable accepts values in the SELECT INTO command: SELECT count(*) INTO person_count FROM person; The variable is used as an output parameter in an external modules call statement: CalcDeptSum(39, dept_sum); Otherwise the external variable should be passed as an input parameter. If a nested module calls another nested module, it should inherit its list of parameters to get access to external variables. Nested modules formed in this way cannot be called within SELECT DML statements. Local modules presented as functions should be implemented as procedures if they use a set-level access to external variables. Otherwise they can be formed as functions. Construct the name of the procedure that emulates a nested module as a concatenation of the main and a nested module names: < main_module_name>$[<nested_module_name>$...]<nested_module_name>] In the case of overloaded modules, add the additional prefix to their names: <module_name>OVR<N> Where <N> is the serial number of the overloaded module. Form the name of a variable that is external to a nested module and is used as an input/output parameter by using the following pattern:
53
@$[<outer_module>$. . .]<variable_name> Example 1 In the simplest case, you dont have any local variables. Oracle create procedure Proc1 is procedure DeptSales(dept_id int) is lv_sales int; begin select sales into lv_sales from departmentsales where id = dept_id; end DeptSales; begin DeptSales(100); end Proc1; SQL Server CREATE @dept_id AS declare @lv_sales int Select @lv_sales = sales From departmentsales Where id = @dept_id RETURN GO CREATE AS Execute Proc1$DeptSales 100 RETURN GO Example 2 PROCEDURE Proc1 PROCEDURE int Proc1$DeptSales
54
In this example, an external variable named on_year is read only. It is added to the parameter list as an IN parameter. Oracle create procedure Proc1 is on_year int := 2000; procedure DeptSales(dept_id int) is lv_sales int; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; end DeptSales; begin DeptSales(100); end Proc1; SQL Server CREATE @dept_id AS declare @lv_sales int select @lv_sales = sales From departmentsales where id = @dept_id AND year = @$on_year RETURN GO CREATE AS declare @on_year int set @on_year = 2000 Execute Proc1$DeptSales 100,@on_year RETURN GO Example 3 PROCEDURE Proc1 PROCEDURE int, -- Proc1.on_year Proc1$DeptSales
@$on_year int
55
Next, the external variable dept_sales is modified in a nested module. It is treated as an output parameter. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int; procedure DeptSales(dept_id int) is lv_sales int; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; dept_sales := lv_sales; end DeptSales; begin DeptSales(100); end Proc1; SQL Server CREATE PROCEDURE Proc1$DeptSales -- Proc1.on_year
@dept_id int, @$on_year int, AS declare @lv_sales int select @lv_sales = sales from departmentsales where id = @dept_id AND year = @$on_year set @$dept_sales = @lv_sales RETURN GO CREATE AS declare @on_year int set @on_year = 2000 PROCEDURE Proc1 @$dept_sales int OUTPUT -- Proc1.dept_sales
56
declare @dept_sales int Execute Proc1$DeptSales 100, @on_year, @$dept_sales = @dept_sales OUTPUT RETURN GO Example 4 In this example, the nested module calls another nested module that is defined at the same level. In this case, all external variables used in the caller module should also be passed to the called module. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int; procedure DeptSales(dept_id int) is lv_sales int; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; dept_sales := lv_sales; end DeptSales; procedure DeptSales_300 is begin DeptSales(300); end DeptSales_300; begin DeptSales(100); DeptSales_300; end Proc1; SQL Server CREATE PROCEDURE Proc1$DeptSales
57
@dept_id int, @$on_year int, AS declare @lv_sales int Select @lv_sales = sales From departmentsales Where id = @dept_id AND year = @$on_year set @$dept_sales = @lv_sales RETURN GO CREATE PROCEDURE Proc1$DeptSales_300 -- Proc1.on_year -- Proc1.on_year @$dept_sales int OUTPUT -- Proc1.dept_sales
@$on_year int, AS Execute Proc1$DeptSales 300, @$on_year,
@$dept_sales int OUTPUT -- Proc1.dept_sales
@$dept_sales = @$dept_sales OUTPUT RETURN GO CREATE AS declare @on_year int set @on_year = 2000 declare @dept_sales int Execute Proc1$DeptSales 100, @on_year, @$dept_sales = @dept_sales OUTPUT Execute Proc1$DeptSales_300 @on_year, @$dept_sales = @dept_sales OUTPUT RETURN PROCEDURE Proc1
58
GO Example 5 The next example shows the variable on_year used by the external procedure GetNextYear as an output parameter. So, the variable is also passed to the nested module as an output parameter. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int; procedure DeptSales(dept_id int) is lv_sales int; begin GetNextYear(on_year); select sales into lv_sales from departmentsales where id = dept_id and year = on_year; CheckLimit(dept_id, dept_sales + lv_sales); end DeptSales; begin GetDeptSum(100, dept_sales); DeptSales(100); end Proc1; SQL Server CREATE PROCEDURE Proc1$DeptSales -- Proc1.on_year -- Proc1.dept_sales
@dept_id int, @$on_year int OUTPUT, @$dept_sales int AS declare @lv_sales int Execute dbo.GetNextYear @par_yyy = @$on_year OUTPUT Select @lv_sales = sales From departmentsales Where id = @dept_id AND year = @$on_year Execute dbo.CheckLimit @dept_id, @$dept_sales + @lv_sales
59
RETURN GO CREATE AS declare @on_year int set @on_year = 2000 declare @dept_sales int Execute dbo.GetDeptSum 100, @$par_sum = @dept_sales OUTPUT Execute Proc1$DeptSales 100, @$on_year = @on_year OUTPUT, @dept_sales RETURN GO Example 6 In this example, a nested module includes a declaration of its own nested module, Add. The inner module requires access to the variable dept_sales declared in the main procedure and to the local variable lv_sales defined in DeptSales. In this case, pass all external variables that are used by the inner module (Add) to the procedure that emulates the first nested module (DeptSales). Oracle create procedure Proc1 is on_year int := 2000; dept_sales int := 0; procedure DeptSales(dept_id int) is lv_sales int; procedure Add is dept_sales := dept_sales + lv_sales; end Add; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; Add; end DeptSales; . . . PROCEDURE Proc1
60
end Proc1; SQL Server CREATE PROCEDURE Proc1$DeptSales$Add
@$dept_sales int OUTPUT -- Proc1.dept_sales @$DeptSales$lv_sales int,-- DeptSales.lv_sales AS set @$dept_sales = @$dept_sales + @$DeptSales$lv_sales RETURN GO CREATE PROCEDURE Proc1$DeptSales -- Proc1.on_year
@dept_id int, @$on_year int, AS declare @lv_sales int Select @lv_sales = sales From departmentsales Where id = @dept_id AND year = @$on_year Execute Proc1$DeptSales$Add @$dept_sales = @$dept_sales OUTPUT, @lv_sales RETURN GO Example 7 In this example, the nested module DeptSales has a nested module named Add and a local variable named lv_sales. The main module has its own local module with the same name and a variable with the same name. Oracle create procedure Proc1 is on_year int := 2000; dept_sales int := 0; procedure DeptSales(dept_id int) is lv_sales int; @$dept_sales int OUTPUT -- Proc1.dept_sales
61
procedure Add is dept_sales := dept_sales + lv_sales; end Add; begin select sales into lv_sales from departmentsales where id = dept_id and year = on_year; Add; declare lv_sales int := 500,000; end DeptSales; procedure Add is dept_sales := dept_sales + lv_sales; end Add; begin Add; end; . . . SQL Server CREATE PROCEDURE Proc1$DeptSales$NOLABEL1$Add -- Proc1.dept_sales -- unnamed_block.lv_sales
@$dept_sales int OUTPUT, @$DeptSales$NOLABEL1$lv_sales int AS
set @$dept_sales = @$dept_sales + @$DeptSales$NOLABEL1$lv_sales RETURN GO CREATE PROCEDURE Proc1$DeptSales$Add -- Proc1.dept_sales -- DeptSales.lv_sales
@$dept_sales int OUTPUT, @$DeptSales$lv_sales int AS
set @$dept_sales = @$dept_sales + @$DeptSales$lv_sales
62
RETURN GO CREATE PROCEDURE Proc1$DeptSales -- Proc1.on_year
@dept_id int, @$on_year int, AS declare @lv_sales int Select @lv_sales = sales From departmentsales Where id = @dept_id AND year = @$on_year Execute Proc1$DeptSales$Add @$dept_sales = @$dept_sales OUTPUT, @lv_sales declare @NOLABEL1@lv_sales int set @NOLABEL1@lv_sales = 500000 Execute Proc1$DeptSales$NOLABEL1$Add @$dept_sales = @$dept_sales OUTPUT, @NOLABEL1@lv_sales RETURN GO @$dept_sales int OUTPUT -- Proc1.dept_sales
63
Migrating Oracle User-Defined Functions

This section describes how SSMA Oracle 3.0 converts Oracle user-defined functions. While Oracle functions closely resemble Transact-SQL functions, significant differences do exist. The main difference is that Transact-SQL functions cannot contain DML statements and cannot invoke stored procedures. In addition, Transact-SQL functions do not support transaction-management commands. These are stiff restrictions. A workaround implements a function body as a stored procedure and invokes it within the function by means of an extended procedure. Note that some Oracle function features, such as output parameters, are not currently supported.
Conversion Algorithm
The general format of an Oracle user-defined function is: FUNCTION [schema.]name [({@parameter_name [ IN | OUT | IN OUT ] [ NOCOPY ] [ type_schema_name. ] parameter_data_type default_value } [ ,...n ] ) ] RETURN <return_data_type> [AUTHID {DEFINER | CURRENT_USER}] [DETERMINISTIC] [PARALLEL ENABLE ...] [AGGREGATE | PIPELINED] { IS | AS } { LANGUAGE { Java_declaration | C_declaration } | { [<declaration statements>] BEGIN <executable statements> RETURN <return statement> [EXCEPTION exception handler statements] END [ name ]; }} And the proper Transact-SQL format of a scalar function is: CREATE FUNCTION [ schema_name. ] function_name ( [ { @parameter_name [ AS ][ type_schema_name. ] parameter_data_type [:= | DEFAULT]
64
[ = default_value ] } [ ,...n ] ] ) RETURNS <return_data_type> [WITH { EXEC | EXECUTE } AS { CALLER | OWNER }] [ AS ] BEGIN <function_body> RETURN <scalar_expression> END [ ; ] The following clauses and arguments are not supported by SSMA and are ignored during conversion: AGGREGATE DETERMINISTIC LANGUAGE PIPELINED PARALLEL_ENABLE IN, OUT, and NOCOPY
For the remaining function options, the following rules are applied during conversion: The OUT qualifier is used when a function is implemented as a procedure. The [:= | DEFAULT] option of a function parameter is converted to an equals sign (=). The AUTHID clause is converted to an EXECUTE AS clause. The CURRENT_USER argument is converted to a CALLER argument. The DEFINER argument is converted to an OWNER argument.
As a result of the conversion you get either: One Transact-SQL function body Two objects: Implementation of a function in the form of a procedure A function that is a wrapper for the procedure calling
Following are the conditions when you must create this additional procedure: The source function is defined as an autonomous transaction by PRAGMA AUTONOMOUS_TRANSACTION. A function contains statements that are not valid in SQL Server user-defined functions, such as:
65
DML operations (UPDATE, INSERT, DELETE) that modify tables, except for local table variables A call of a stored procedure Transaction-management commands The raise exception command Exception-handling statements FETCH statements that return data to the client Cursor operations that reference global cursors
If any of these conditions are present, implement the function both as a procedure and a function. In this case, the procedure is used in a call via an extended procedure in the function body. Implement the function body according to the following pattern: CREATE FUNCTION [schema.] <function_name> ( <parameters list> ) RETURNS <return_type> AS BEGIN declare @spid int, @login_time datetime select @spid = sysdb.ssma_ora.get_active_spid(),@login_time = sysdb.ssma_ora.get_active_login_time() DECLARE @return_value_variable <function_return_type> EXEC master.dbo.xp_ora2ms_exec2_ex @@spid,@login_time, <database_name>, <schema_name>, <function_implementation_as_procedure_name>, bind_to_transaction_flag, [parameter1, parameter2, ... ,] @return_value_variable OUTPUT RETURN @return_value_variable END The syntax of the xp_ora2ms_exec2_ex procedure is: xp_ora2ms_exec2_ex
66
<active_spid> int, <login_time> datetime, <ms_db_name> varchar, <ms_schema_name> varchar, <ms_procedure_name> varchar, <bind_to_transaction_flag> varchar, [optional_parameters_for_procedure] Where: <active_spid> [input parameter] is the session ID of the current user process. <login_time> [input parameter] is the login time of the current user process. <ms_db_name> [input parameter] is the database name owner of the stored proceduure. <ms_schema_name> [input parameter] is the schema name owner of the stored procedure. <ms_procedure_name> [input parameter] is the name of the stored procedure. <bind_to_transaction_flag> [input parameter] binds or unbinds a connection to the current transaction. Valid values are 'TRUE,' 'true, 'Y, 'y. Other values are ignored. optional_parameters_for_procedure [input/output parameter] are the procedure parameters.
If PRAGMA AUTONOMOUS_TRANSACTION is used, set the xp_ora2ms_exec2_ex procedures bind to transaction parameter to true. Otherwise, set it to false. For details about autonomous transactions, see Simulating Oracle Autonomous Transactions. A functions procedure implementation is converted according to the following pattern: CREATE PROCEDURE [schema.] <function_name>$IMPL <parameters list> , @return_value_argument <function_return_type> OUTPUT AS BEGIN set implicit_transactions on AUTONOMOUS_TRANSACTION*/ <function implementation> SET @return_value_argument = <return_expression> RETURN END Where <return_expression> is an expression that a function uses in the RETURN operator. So, the RETURN statement in a functions procedure implementation is converted according to this pattern: /*only in case of PRAGMA
67
PL-SQL Code RETURN <return_expresion>; Transact-SQL Code SET @return_value_argument = <return_expression> RETURN Convert multiple RETURNs in the same way: PL-SQL Code ... IF <condition> THEN RETURN <return_expresion_1>; ELSE RETURN <return_expresion_2>; ENDIF ... Transact-SQL Code ... IF <condition> BEGIN SET @return_value_argument = <return_expression_1> RETURN END ELSE BEGIN SET @return_value_argument = <return_expression_1> RETURN END ... When possible, use a procedure-call statement when converting a function call. That approach, unlike a call via an extended procedure, allows exposing the output that a function produces. Examples PL-SQL Code
68
declare i int :=fn_test1(); begin i:=fn_test2(); DBMS_OUTPUT.PUT_LINE(i); end; Transact-SQL Code DECLARE @i int exec FN_TEST1$IMPL @i out BEGIN exec FN_TEST2$IMPL @i out PRINT @i END
Converting Function Calls When a Function Has Default Values for Parameters and with Various Parameter Notations
When calling functions in Oracle, you can pass parameters by using: Positional notation. Parameters are specified in the order in which they are declared in the procedure. Named notation. The name of each parameter is specified along with its value. An arrow (=>) serves as the association operator. The order of the parameters is not significant. Mixed notation. The first parameters are specified with positional notation, then switched to named notation for the last parameters.
Because SQL Server does not support named notation for parameters that are passed to functions, the named notation is converted to the positional notation call. In addition, SQL Server functions do not support omitted parameters, so when the default parameters are omitted, the statement is converted by adding the keyword, default, instead of the omitted parameters. Examples PL-SQL Code CREATE OR REPLACE FUNCTION fn_test ( p_1 VARCHAR2, p_2 VARCHAR2 DEFAULT 'p_2', p_3 VARCHAR2 DEFAULT 'p_3') RETURN VARCHAR2 IS BEGIN return null; END;
69
/ select fn_test('p1') from dual; declare a varchar2(50); begin a:= fn_test('p_1','hello','world'); a:= fn_test('p_1'); a:= fn_test('p_1',p_3=>'world'); a:= fn_test(p_2=>'hello',p_3=>'world',p_1=>'p_1'); end; Transact-SQL Code CREATE FUNCTION fn_test ( @p_1 VARCHAR(8000), @p_2 VARCHAR(8000)= 'p_2', @p_3 VARCHAR(8000)= 'p_3') RETURNS BEGIN return null; END; GO select dbo.fn_test('p1',default,default) declare @a varchar(50) begin set @a = dbo.fn_test('p_1','hello','world') set @a = dbo.fn_test('p_1', default, default) set @a = dbo.fn_test('p_1',default, 'world') set @a = dbo.fn_test('p_1','hello','world') end; VARCHAR(8000) as
Converting Functions that Have Default Parameters Other Than Constants

Next we examine two solutions for omitted parameters. Solution 1 is the solution that is implemented in SSMA 3.0. Solution 2 presents an alternative for manual migration, which can be useful in complex cases.
Solution 1
How you convert a function call depends on whether the function is a standalone or a packaged function. You cannot identify default values for the parameters of a standalone function (neither their existence nor their value). There is an option in
70
Project Preferences that you use to choose whether to mark calls that have omitted parameters as an error or warning. An expression is simple if it is constant or null; otherwise it is considered to be a heavy expression. When the function or procedure declaration is converted, simple defaultargument values are converted, while heavy default-argument values are skipped and a warning message is generated. (Heavy default expressions are substituted in each packaged function call if the parameter was omitted.) Unlike standalone functions, SSMA can obtain the default value of packaged functions. So, packaged function calls are converted in the following way. Packaged function calls: For named parameters, change the parameter order to an order that is valid in SQL Server. Transform named notation to not named. Replace omitted parameters with the default value. If a function parameter has a default value that is treated as a simple expression, pass the default keyword instead of the omitted parameter. If a function parameter has a default value that is treated as a heavy expression, pass the expression instead of the omitted parameter. Change the order of parameters to an order that is valid in SQL Server. Transform named notation to not named. Mark function calls that have omitted parameters as a warning or error.
Function calls that are not packaged:
Solution 2
In Solution 2, when the default value for a parameter is not a constant value, convert the default value to a null value. Add a parameter of the nvarchar(4000) data type named @params to the target function parameter list. That parameter should contain a text mask of the names of parameters that are passed explicitly. By checking this parameter, it is possible to know whether the parameter is omitted or if it has explicitly passed a null value. The pattern for converting functions that use default values other than constants is as follows: PL-SQL Code CREATE OR REPLACE FUNCTION <function_name> ( <param1_name> <param1_datatype>, <param2_name> <param2_datatype> DEFAULT <heavy2_statement>, <param3_name> <param3_datatype> DEFAULT <heavy3_statement>) RETURN <return_datatype> IS BEGIN <function_body> END; Transact-SQL Code
71
CREATE FUNCTION <function_name> ( <@param1_name> <param1_datatype>, <@param2_name> <param2_datatype> = null, <@param3_name> <param3_datatype> = null, @params nvarchar(4000) ) RETURNS <return_datatype> as BEGIN if <@param2_name> is null and charindex('<@param2_name>',@params)=0 set <@param2_name> = <heavy2_statement> if <@param3_name> is null and charindex('<@param3_name>',@params)=0 set <@param3_name> = <heavy3_statement> <function_body> END When a function has at least one default value, the function call statement should be converted by taking into account that the function has a text-mask parameter where all passed parameter names should be concatenated as a string. Examples PL-SQL Code CREATE OR REPLACE FUNCTION fn_test ( p_1 VARCHAR2 DEFAULT 'p_1', p_2 VARCHAR2 DEFAULT to_char(sysdate), p_3 VARCHAR2 DEFAULT SYSDATE ||' '|| user) RETURN VARCHAR2 IS BEGIN return p_1 || p_2 || p_3; END; / select fn_test('p1') from dual; select fn_test('p1', 'p2') from dual; Transact-SQL Code CREATE function fn_test ( @p_1 VARCHAR(8000) = 'p_1', @p_2 VARCHAR(8000) = null, @p_3 VARCHAR(8000) = null,
72
@params nvarchar(4000) ) RETURNS varchar(8000) as BEGIN if @p_2 is null and charindex('@p_2',@params)=0 set @p_2 = cast(getdate() as varchar(8000)) if @p_3 is null and charindex('@p_3',@params)=0 set @p_3 = cast (getdate() as varchar(8000)) + ' ' + SESSION_USER return @p_1 + ' ' + @p_2 +' ' +@p_3 END; GO select dbo.fn_test('p1',default,default,'@p_1') select dbo.fn_test('p1', 'p2',default,'@p_1@p_2')
Migrating Oracle Triggers

This section describes the differences between Oracle and Microsoft SQL Server 2005 triggers, and how SSMA Oracle 3.0 handles them when it converts Oracle triggers to SQL Server. (This section does not cover DDL or system triggers. The discussion is limited to DML triggers, that is, triggers on INSERT, UPDATE, or DELETE statements.) The first major difference between Oracle and SQL Server triggers is that the most common Oracle trigger is a row-level trigger (FOR EACH ROW), which fires for each row of the source statement. SQL Server, however, supports only statement-level triggers, which fire only once per statement, irrespective of the number of rows affected. In a row-level trigger, Oracle uses an :OLD alias to refer to column values that existed before the statement executes, and to the changed values by using a :NEW alias. SQL Server uses two pseudotables, inserted and deleted, and each can have multiple rows. If the triggering statement is UPDATE, a row's older version is present in deleted, and the newer in inserted. But it is not easy to tell which pair belongs to the same row if the updated table does not have a primary key or the primary key was modified. You can resolve this problem only if SSMA generates a special ROWID column for the table. Therefore, if you are converting tables with UPDATE triggers, we recommend setting the Generate ROWID column option to Yes in the SSMA project settings. (See Figure 2.) To emulate row-level triggers, SSMA processes each row in a cursor loop.
73
Figure 2: Set up the Generate ROWID column option The second major difference between Oracle and SQL Server triggers comes from Oracle BEFORE triggers. Because Oracle fires these triggers before the triggering statement, it is possible to modify the actual field values that will be stored in the table, or even cancel the execution of the triggering statement if it is found to be unnecessary. To emulate this in SQL Server, you must create INSTEAD OF triggers. That means you must incorporate the triggering statement into the target trigger's body. Because multiple rows can be affected, SSMA puts the statement in a separate cursor loop. In some cases, you cannot convert Oracle triggers to SQL Server triggers with one-toone correspondence. If an Oracle trigger is defined for several events at once (for example, INSERT or UPDATE), you must create two separate target triggers, one for INSERT and one for UPDATE. In addition, as SQL Server supports only one INSTEAD OF trigger per table, SSMA combines the logic of all BEFORE triggers on that table into a
74
single target trigger. This means that triggers are not converted independently of each other; SSMA takes the entire set of triggers belonging to a table and converts them into another set of SQL Server triggers so that the general relation is many-to-many. In brief, the conversion rules are: All BEFORE triggers for a table are converted into one INSTEAD OF trigger. AFTER triggers remain AFTER triggers in SQL Server. INSTEAD OF triggers on Oracle views remain INSTEAD OF triggers. Row-level triggers are emulated with a cursor loop. Triggers that are defined for multiple events are split into separate target triggers.
Sometimes an Oracle trigger is defined for a specific column with the UPDATE OF column [, column ]... ] clause. To emulate this, SSMA wraps the trigger body with the following SQL Server construction: IF (UPDATE(column) [OR UPDATE(column) . . .] BEGIN <trigger body> END SSMA emulates the trigger-specific functions INSERTING, UPDATING, and DELETING by saving the current trigger type in a variable, and then checking that value. For example: DECLARE @triggerType char(1) SELECT @triggerType = 'I' . . . IF (@triggerType = 'I' ) . . . IF (@triggerType = 'U' ) . . . IF (@triggerType = 'D' ) . . . /* emulation of INSERTING */ /* emulation of UPDATING */ /* emulation of DELETING */ /* if the current type is inserting */
The UPDATING function can have a column name as an argument. SSMA can convert such usage if the argument is a character literal. In this case, the Oracle expression: UPDATING (column_name) Is transformed into: UPDATE (columns_name) Note that the original quotes are removed.
Conversion Patterns
This section illustrates the conversion algorithms SSMA uses to convert various types of Oracle triggers. Each example schematically outlines a particular type of trigger. Comments describe the typical contents of source triggers and the structure of the corresponding target triggers as generated by SSMA.
75
AFTER Triggers
TABLE-LEVEL TRIGGERS Table-level AFTER triggers fire only once per table, resembling the behavior of SQL Server AFTER triggers. Thus, the required changes are minimal. Table-level triggers are converted according to this pattern: CREATE TRIGGER [ schema. ]trigger ON <table> AFTER <UPDATE |INSERT | DELETE> AS /* beginning of trigger implementation */ SET NOCOUNT ON ---------------------------------------------------------------------------/* Oracle-trigger implementation: begin */ BEGIN -- UPDATE OF CLAUSE FOR TRIGGER FOR UPDATE EVENT -- (UPDATE OF COLUMN[, COLUMN] ... ]) IF (UPDATE(<COLUMN>) OR UPDATE((<COLUMN>) ...) BEGIN <TRIGGER_BODY> END END /* Oracle-trigger implementation: end */ ---------------------------------------------------------------------------/* end of trigger implementation */
ROW-LEVEL TRIGGERS Since Oracle Database fires a row-level trigger once for each row, emulate row-level triggers with cursor processing. For row-level triggers, a restriction can be specified in the WHEN clause. The restriction is an SQL condition that must be satisfied for the database to fire the trigger. Also, the special variables :NEW and :OLD are available in row-level triggers to refer to new and old records respectively. In SQL Server, the new and old records are stored in the inserted and deleted tables. So, row-level triggers are emulated in the same way as table-level ones, except for the trigger implementation wrapped into the cursor processing block. Replace references to :OLD and :NEW values with values fetched into variables from deleted or updated tables, respectively. THE PATTERN FOR ROW-LEVEL AFTER INSERT TRIGGER
76
CREATE TRIGGER [ schema. ]trigger ON <table> AFTER INSERT AS /* beginning of trigger implementation */ SET NOCOUNT ON /* column variables declaration */ DECLARE /* declare variables to store column values. if trigger has no references to :OLD or :NEW records then define the only uniqueidentifier type variable to store ROWID column value */ @column_new_value$0 uniqueidentifier /* trigger has NO references to :OLD or :NEW* or has explicit reference to ROWID/
/* trigger has references to :OLD or :NEW*/ @column_new_value$X <COLUMN_X_TYPE>, @column_new_value$Y <COLUMN_Y_TYPE>, ... @column_old_value$A <COLUMN_A_TYPE>, @column_old_value$B <COLUMN_B_TYPE> ... /* iterate for each for from inserted/updated table(s) */ DECLARE ForEachInsertedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR /* trigger has NO references to :OLD or :NEW*/ SELECT ROWID FROM inserted /* trigger has references to :OLD or :NEW* or has explicit reference to ROWID/ SELECT [ROWID], <COLUMN_X_NAME>,<COLUMN_Y_NAME> .. FROM inserted OPEN ForEachInsertedRowTriggerCursor
77
FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO /* trigger has NO references to :OLD or :NEW* or has explicit reference to ROWID / @column_new_value$0 /* trigger has references to :NEW*/ @column_new_value$X @column_new_value$Y ...
WHILE @@fetch_status = 0 BEGIN ---------------------------------------------------------------------------/* Oracle-trigger implementation: begin */ BEGIN IF <WHILE_CLAUSE> BEGIN <TRIGGER_BODY> END END /* Oracle-trigger implementation: end */ ---------------------------------------------------------------------------FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO /* trigger has NO references to :NEW* or has explicit reference to ROWID / @column_new_value$0 /* trigger has references to :NEW*/ @column_new_value$X, @column_new_value$Y ... END CLOSE ForEachInsertedRowTriggerCursor
78
DEALLOCATE ForEachInsertedRowTriggerCursor /* end of trigger implementation */
THE PATTERN FOR ROW-LEVEL AFTER DELETE CREATE TRIGGER [ schema. ]trigger ON <table> AFTER DELETE AS /* beginning of trigger implementation */ SET NOCOUNT ON /* column variables declaration */ DECLARE /* Declare variables to store column values. If the trigger has no references to :OLD or :NEW records then define the only uniqueidentifier type variable to store ROWID column value. Else define variables to store old or new records. */ @column_new_value$0 uniqueidentifier /* trigger has NO references to :OLD or :NEW or the trigger has explicit reference to ROWID */
/* trigger has references to :OLD or :NEW*/ @column_new_value$X <COLUMN_X_TYPE>, @column_new_value$Y <COLUMN_Y_TYPE>, ... @column_old_value$A <COLUMN_A_TYPE>, @column_old_value$B <COLUMN_B_TYPE>, ...
/* iterate for each for from inserted/updated table(s) */ DECLARE ForEachDeletedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR SELECT [ROWID,] [<COLUMN_A_NAME>, <COLUMN_B_NAME>..] FROM deleted OPEN ForEachDeletedRowTriggerCursor
79
FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO [@column_old_value$0,] [@column_old_value$A, @column_old_value$B ... ]
WHILE @@fetch_status = 0 BEGIN ---------------------------------------------------------------------------/* Oracle-trigger implementation: begin */ BEGIN IF <WHERE_CLAUSE> BEGIN <TRIGGER_BODY> END END /* Oracle-trigger implementation: end */ ---------------------------------------------------------------------------/*this is a trigger for delete event or a trigger for update event that has no references both to :OLD and :NEW */ FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO [@column_old_value$0,] [@column_old_value$A, @column_old_value$B ... ] END CLOSE ForEachDeletedRowTriggerCursor DEALLOCATE ForEachDeletedRowTriggerCursor
/*
end of trigger implementation */
THE PATTERN FOR ROW-LEVEL AFTER UPDATE TRIGGERS CREATE TRIGGER [ schema. ]trigger ON <table> AFTER UPDATE AS
80
/*
beginning of trigger implementation */
SET NOCOUNT ON /* column variables declaration */ DECLARE /* Declare variables to store column values. If the trigger has no references to :OLD or :NEW records then define the only uniqueidentifier type variable to store ROWID column value. Else define variables to store old or new records. If the trigger has reference both to :OLD and :NEW then ALWAYS define uniqueidentifier type variable to synchronize inserted row with deleted row. */ @column_new_value$0 uniqueidentifier /* trigger has NO references to :OLD or :NEW or the trigger has references BOTH to :OLD and :NEW or the trigger has explicit reference to ROWID */
/* trigger has references to :OLD or :NEW*/ @column_new_value$X <COLUMN_X_TYPE>, @column_new_value$Y <COLUMN_Y_TYPE>, ... @column_old_value$A <COLUMN_A_TYPE>, @column_old_value$B <COLUMN_B_TYPE>, ...
/*the trigger has NO references both to :OLD and :NEW or has reference only to :OLD*/ DECLARE ForEachDeletedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR /*the trigger has NO references to :OLD and :NEW*/ SELECT ROWID FROM deleted /*the trigger has references to :OLD*/ SELECT <COLUMN_A_NAME>, <COLUMN_B_NAME>.. FROM deleted /*the trigger has references to :OLD and explicit reference to ROWID */
81
SELECT ROWID, <COLUMN_A_NAME>, <COLUMN_B_NAME>.. FROM deleted
OPEN ForEachDeletedRowTriggerCursor FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO @column_old_value$0
/*the trigger has references to :NEW. If the trigger has references both to :OLD and :NEW then we have to declare cursor for select ROWID from inserted to synchronize inserted row with deleted row. */ DECLARE ForEachInsertedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR SELECT [ROWID,] <COLUMN_X_NAME>, <COLUMN_Y_NAME> ... FROM inserted OPEN ForEachInsertedRowTriggerCursor FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO [@column_new_value$0,] @column_new_value$X, @column_new_value$Y
WHILE @@fetch_status = 0 BEGIN /*The trigger has reference both to :OLD and :NEW. We have to synchronize inserted row with deleted row */ SELECT @column_old_value$A = <COLUMN_A_NAME>, @column_old_value$B = <COLUMN_B_NAME> FROM deleted WHERE ROWID = @column_new_value$0 ------------------------------------------------------------------/* Oracle-trigger implementation: begin */ BEGIN -- UPDATE OF CLAUSE -- (UPDATE OF COLUMN[, COLUMN] ... ]) IF (UPDATE(<COLUMN>) OR UPDATE((<COLUMN>) ...)
82
BEGIN IF <WHERE_CLAUSE> BEGIN <TRIGGER_BODY> END END END /* Oracle-trigger implementation: end */ ------------------------------------------------------------------/*the trigger has NO references both to :OLD and :NEW or has reference only to :OLD*/ FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO [@column_old_value$0,] [@column_old_value$A, @column_old_value$B ... ] END CLOSE ForEachDeletedRowTriggerCursor DEALLOCATE ForEachDeletedRowTriggerCursor
/* the trigger has references to :NEW */ FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO [@column_new_value$0,] @column_new_value$X, @column_new_value$Y END CLOSE ForEachInsertedRowTriggerCursor DEALLOCATE ForEachInsertedRowTriggerCursor
/*
BEFORE Triggers
Because BEFORE triggers do not exist in SQL Server, SSMA emulates them by means of INSTEAD OF triggers. That change requires that the triggering statement be moved into the body of the trigger. Also, all triggers for a specific event should go into one target INSTEAD OF trigger.
83
THE PATTERN FOR BEFORE DELETE TRIGGERS CREATE TRIGGER [ schema. ] INSTEAD_OF_DELETE_ON_<table> ON <table> INSTEAD OF DELETE AS /* beginning of trigger implementation */ SET NOCOUNT ON /* column variables declaration */ DECLARE @column_old_value$0 uniqueidentifier /* trigger has references to :OLD or :NEW*/ @column_new_value$X <COLUMN_X_TYPE>, @column_new_value$Y <COLUMN_Y_TYPE>, ... @column_old_value$A <COLUMN_A_TYPE>, @column_old_value$B <COLUMN_B_TYPE> ... ------------------------------------------------------------------/* insert all table-level triggers implementations here */ <BEFORE_DELETE table-level trigger_1 body> <BEFORE_DELETE table-level trigger_2 body> ... ------------------------------------------------------------------/* iterate for each for from inserted/updated table(s) */ DECLARE ForEachDeletedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR SELECT ROWID /*if the trigger has refrences to :OLD*/ <COLUMN_A_NAME>,<COLUMN_B_NAME>, ... FROM deleted OPEN ForEachDeletedRowTriggerCursor
84
FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO @column_old_value$0 /*if the trigger has refrences to :OLD*/ , @column_old_value$A ,@column_old_value$B ... WHILE @@fetch_status = 0 BEGIN /* insert all row-level triggers implementations here*/ /* Oracle-trigger BEFORE_DELETE row-level trigger_1 implementation: begin */ BEGIN IF (<BEFORE_DELETE row-level trigger_1 WHERE_CLAUSE>) BEGIN <BEFORE_DELETE row-level trigger_1 body> END END /* Oracle-trigger dbo BEFORE_DELETE row-level trigger_1 implementation: end */ /* Oracle-trigger BEFORE_DELETE row-level trigger_2 implementation: begin */ BEGIN IF (<BEFORE_DELETE row-level trigger_2 WHERE_CLAUSE>) BEGIN <BEFORE_DELETE row-level trigger_2 body> END END /* Oracle-trigger dbo BEFORE_DELETE row-level trigger_2 implementation: end */ ... /* DML-operation emulation */ DELETE FROM <table>
85
WHERE ROWID = @column_old_value$0 FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO @column_old_value$0 /*if the trigger has refrences to :OLD*/ , @column_old_value$A ,@column_old_value$B ... END CLOSE ForEachDeletedRowTriggerCursor DEALLOCATE ForEachDeletedRowTriggerCursor /* end of trigger implementation */
THE PATTERN FOR BEFORE UPDATE TRIGGERS CREATE TRIGGER dbo.INSTEAD_OF_UPDATE_ON_<table> ON <table> INSTEAD OF UPDATE AS /* begin of trigger implementation */ SET NOCOUNT ON /* column variables declaration */ /* declare variables to store all table columns */ DECLARE @column_new_value$0 uniqueidentifier, @column_new_value$1 <COLUMN_1_TYPE>, @column_new_value$2 <COLUMN_1_TYPE>, ... /*declare variables to store values of :OLD*/ @column_old_value$A <COLUMN_A_TYPE>, @column_old_value$B <COLUMN_B_TYPE>, -----------------------------------------------------------------/* insert all table-level triggers implementations here */ <BEFORE_UPDATE table-level trigger_1 body>
86
<BEFORE_UPDATE table-level trigger_2 body> ... -----------------------------------------------------------------/* iterate for each for from inserted/updated table(s) */ DECLARE ForEachInsertedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR SELECT ROWID, <COLUMN_NAME_1>, <COLUMN_NAME_2> ... FROM inserted OPEN ForEachInsertedRowTriggerCursor FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO @column_new_value$0, @column_new_value$1, @column_new_value$2, ... WHILE @@fetch_status = 0 BEGIN /*if the trigger has references to :OLD*/ /* synchronize inserted row with deleted row */ SELECT @column_old_value$A = <COLUMN_A_NAME>, @column_old_value$B = <COLUMN_B_NAME>, ... FROM deleted WHERE ROWID = @column_new_value$0
/* insert all row-level triggers implementations here */ /* Oracle-trigger BEFORE_UPDATE row-level trigger_1 implementation: begin */ BEGIN -- (UPDATE OF COLUMN[, COLUMN] ... ]) IF (UPDATE(<COLUMN>) OR UPDATE((<COLUMN>) ...) BEGIN IF <<BEFORE_UPDATE row-level trigger_1 WHERE_CLAUSE>> BEGIN <BEFORE_UPDATE row-level trigger_1 body>
87
END END END /* Oracle-trigger dbo BEFORE_UPDATE row-level trigger_1 implementation: end */ /* Oracle-trigger BEFORE_UPDATE row-level trigger_2 implementation: begin */ BEGIN -- (UPDATE OF COLUMN[, COLUMN] ... ]) IF (UPDATE(<COLUMN>) OR UPDATE((<COLUMN>) ...) BEGIN IF <<BEFORE_UPDATE row-level trigger_2 WHERE_CLAUSE>> BEGIN <BEFORE_UPDATE row-level trigger_2 body> END END END /* Oracle-trigger dbo BEFORE_UPDATE row-level trigger_2 implementation: end */ ... /* DML-operation emulation */ UPDATE <table> SET <COLUMN_NAME_1> = @column_new_value$1, <COLUMN_NAME_1> = @column_new_value$1, ... WHERE ROWID = @column_new_value$0 FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO @column_new_value$0, @column_new_value$1, @column_new_value$2, ... END
88
CLOSE ForEachInsertedRowTriggerCursor DEALLOCATE ForEachInsertedRowTriggerCursor /* end of trigger implementation */
THE PATTERN FOR BEFORE INSERT TRIGGERS CREATE TRIGGER dbo.INSTEAD_OF_INSERT_ON_<table> ON <table> INSTEAD OF INSERT AS /* beginning of trigger implementation */ SET NOCOUNT ON /* column variables declaration */ /* declare variables to store all table columns */ DECLARE @column_new_value$1 <COLUMN_1_TYPE>, @column_new_value$2 <COLUMN_1_TYPE>, ... /*declare variables to store values of :OLD*/ @column_old_value$A <COLUMN_A_TYPE>, @column_old_value$B <COLUMN_B_TYPE>, ... ---------------------------------------------------------------------------/* insert all table-level triggers implementations here */ <BEFORE_INSERT table-level trigger_1 body> <BEFORE_INSERT table-level trigger_2 body> ... ---------------------------------------------------------------------------/* iterate for each for from inserted/updated table(s) */ DECLARE ForEachInsertedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR
89
SELECT <COLUMN_1_NAME>,<COLUMN_2_NAME> ... FROM inserted OPEN ForEachInsertedRowTriggerCursor FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO @column_new_value$1, @column_new_value$2, ... WHILE @@fetch_status = 0 BEGIN /* insert all row-level triggers implementations here */ /* Oracle-trigger BEFORE_INSERT row-level trigger_1 implementation: begin */ BEGIN IF (<BEFORE_UPDATE row-level trigger_1 WHERE_CLAUSE>) BEGIN <BEFORE_UPDATE row-level trigger_1 body> END END /* Oracle-trigger dbo BEFORE_UPDATE row-level trigger_1 implementation: end */ /* Oracle-trigger BEFORE_INSERT row-level trigger_2 implementation: begin */ BEGIN IF (<BEFORE_UPDATE row-level trigger_2 WHERE_CLAUSE>) BEGIN <BEFORE_UPDATE row-level trigger_2 body> END END /* Oracle-trigger dbo BEFORE_UPDATE row-level trigger_2 implementation: end */ ... /* DML-operation emulation */ INSERT INTO <table> (<COLUMN_1_NAME>,<COLUMN_2_NAME> ...) VALUES (@column_new_value$1, @column_new_value$2, ...)
90
FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO @column_new_value$1, @column_new_value$2, ... END CLOSE ForEachInsertedRowTriggerCursor DEALLOCATE ForEachInsertedRowTriggerCursor /* end of trigger implementation */
INSTEAD OF Triggers
Oracle INSTEAD OF triggers remain INSTEAD OF triggers in SQL Server. Combine multiple INSTEAD OF triggers that are defined on the same event into one trigger. INSTEAD OF trigger statements are implicitly activated for each row. THE PATTERN FOR INSTEAD OF UPDATE TRIGGERS AND INSTEAD OF DELETE TRIGGERS CREATE TRIGGER [schema. ]INSTEAD_OF_UPDATE_ON_VIEW_<table> ON <table> INSTEAD OF {UPDATE | DELETE} AS /* beginning of trigger implementation */ SET NOCOUNT ON /* column variables declaration */ DECLARE /*if the trigger has no refrences to :OLD that define one variable to store first column. Else define only columns that has references to :OLD*/ @column_old_value$1 <COLUMN_1_TYPE> @column_old_value$X <COLUMN_X_TYPE>, @column_old_value$Y <COLUMN_Y_TYPE>, ... /*define columns to store references to :NEW*/ @column_new_value$A <COLUMN_A_TYPE>,
91
@column_new_value$B <COLUMN_B_TYPE>, ... /* iterate for each for from inserted/updated table(s) */ /* For trigger for UPDATE event that has references to :NEW define and open cursor from inserted as well*/ DECLARE ForEachInsertedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR SELECT <COLUMN_A_NAME>, <COLUMN_B_NAME> ... FROM inserted OPEN ForEachInsertedRowTriggerCursor FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO @column_new_value$A, @column_new_value$B ... DECLARE ForEachDeletedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR SELECT <COLUMN_X_NAME>, <COLUMN_Y_NAME> ... FROM deleted OPEN ForEachDeletedRowTriggerCursor FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO /* trigger has no references to :OLD*/ @column_old_value$1 /* trigger has references to :OLD*/ @column_old_value$X, @column_old_value$Y ... WHILE @@fetch_status = 0 BEGIN ---------------------------------------------------------------------------/* Oracle-trigger INSTEAD OF UPDATE/DELETE trigger_1 implementation: begin */ BEGIN < INSTEAD OF UPDATE/DELETE trigger_1 BODY> END
92
/* Oracle-trigger INSTEAD OF UPDATE/DELETE trigger_1 implementation: end */ /* Oracle-trigger INSTEAD OF UPDATE/DELETE trigger_2 implementation: begin */ BEGIN < INSTEAD OF UPDATE/DELETE trigger_1 BODY> END /* Oracle-trigger INSTEAD OF UPDATE/DELETE trigger_2 implementation: end */ ... ---------------------------------------------------------------------------/*Only for trigger for UPDATE event that has references to :NEW*/ FETCH NEXT FROM ForEachInsertedRowTriggerCursor INTO @column_new_value$A, @column_new_value$B ... OPEN ForEachDeletedRowTriggerCursor FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO /* trigger has no references to :OLD*/ @column_old_value$1 /* trigger has references to :OLD*/ @column_old_value$X, @column_old_value$Y ... END /*Only for trigger for UPDATE event that has references to :NEW*/ CLOSE ForEachInsertedRowTriggerCursor DEALLOCATE ForEachInsertedRowTriggerCursor CLOSE ForEachDeletedRowTriggerCursor DEALLOCATE ForEachDeletedRowTriggerCursor /* end of trigger implementation */
THE PATTERN FOR INSTEAD OF INSERT TRIGGERS
93
INSTEAD OF triggers are converted in the same way as DELETE and UPDATE triggers, except the iteration for each row is made with the inserted table. CREATE TRIGGER [schema. ]INSTEAD_OF_INSERT_ON_VIEW_<table> ON <table> INSTEAD OF INSERT AS /* beginning of trigger implementation */ SET NOCOUNT ON /* column variables declaration */ DECLARE to :NEW*/ /*if the trigger has no refrences to :NEW that define one variable store first column. Else define only columns that has references to @column_new_value$1 <COLUMN_1_TYPE> @column_new_value$X <COLUMN_X_TYPE>, @column_new_value$Y <COLUMN_Y_TYPE>, ... /*define columns to store references to :OLD */ @column_old_value$A <COLUMN_A_TYPE>, @column_old_value$B <COLUMN_B_TYPE>, ... /* iterate for each for from inserted/updated table(s) */ DECLARE ForEachInsertedRowTriggerCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY FOR SELECT <COLUMN_X_NAME>, <COLUMN_Y_NAME> ... FROM inserted OPEN ForEachInsertedRowTriggerCursor FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO /* trigger has no references to :NEW*/ @column_new_value$1 /* trigger has references to :NEW*/ @column_new_value$X, @column_new_value$Y ...
94
WHILE @@fetch_status = 0 BEGIN ---------------------------------------------------------------------------/* Oracle-trigger INSTEAD OF INSERT trigger_1 implementation: begin */ BEGIN < INSTEAD OF INSERT trigger_1 BODY> END /* Oracle-trigger INSTEAD OF INSERT trigger_1 implementation: end */ /* Oracle-trigger INSTEAD OF INSERT trigger_2 implementation: begin */ BEGIN < INSTEAD OF INSERT trigger_1 BODY> END /* Oracle-trigger INSTEAD OF INSERT trigger_2 implementation: end */ ... ---------------------------------------------------------------------------OPEN ForEachInsertedRowTriggerCursor FETCH NEXT FROM ForEachDeletedRowTriggerCursor INTO /* trigger has no references to :NEW*/ @column_new_value$1 /* trigger has references to :NEW*/ @column_new_value$X, @column_new_value$Y ... END CLOSE ForEachInsertedRowTriggerCursor DEALLOCATE ForEachInsertedRowTriggerCursor
95
/*
Autonomous Transactions in Triggers

Convert triggers with PRAGMA AUTONOMOUS_TRANSACTION as described earlier, except execute the trigger body in a separate connection. SSMA uses the xp_ora2ms_exec2_ex extended procedure, which launches the trigger body's procedure implementation. That procedure is created when you install the SSMA Extension Pack. THE PATTERN FOR THE TRIGGER BODY declare @spid int, @login_time datetime select @spid = ssma_ora.get_active_spid(), @login_time = ssma_ora.get_active_login_time() EXEC master.dbo.xp_ora2ms_exec2_ex @spid, @ login_time, <database_name>, <schema_name>, <trigger_implementation_as_procedure_name>, 0, [parameter1, parameter2, ... ,] The trigger body's procedure implementation follows a pattern that depends on the trigger type. For all types of table-level triggers, this procedure has no parameters. Since the first PL-SQL statement in an autonomous routine begins a new transaction, the procedure body should begin with the set implicit_transactions on statement. Pattern for implementation of table-level triggers create procedure <trigger_name>$imlp as begin set implicit_transactions on <TRIGGER_BODY> end For row-level triggers, SSMA passes NEW and OLD rows to the procedure. In BEFORE UPDATE and BEFORE INSERT row-level triggers, you can write to the :NEW value. So in autonomous transactions you must pass a :NEW value back to a trigger. In that way, the pattern for row-level trigger-body procedure implementation looks like following. Pattern for implementing AFTER, INSTEAD OF, and BEFORE DELETE row-level triggers create procedure <trigger_name>$impl @rowid,@column_new_value$1,@column_new_value$2, ... ,
96
@column_old_value$1,@column_old_value$2.. as begin set implicit_transactions on <TRIGGER_BODY> end Pattern for implementing BEFORE UPDATE and BEFORE INSERT row-level triggers create procedure before <trigger_name>$imlp @rowid,@column_new_value$1 output ,@column_new_value$2 output, ... , @column_old_value$1,@column_old_value$2.. as begin set implicit_transactions on <TRIGGER_BODY> end The logic of these patterns for all types of row-level triggers remains the same, except SSMA creates references to all columns of :NEW and :OLD values. In row-level triggers for the INSERT event, you pass references to :NEW value and null values instead of :OLD value. In row-level triggers for the DELETE event, you pass references to :OLD value and null values instead of :NEW value. In row-level triggers for the UPDATE event, you pass references to both :OLD value and :NEW value.
Notes on Autonomous Transaction Conversion in Triggers

In Oracle, none of the changes made in the main transaction are visible to an autonomous transaction. To protect the autonomous transaction from reading uncommitted data, we recommend using a row-versioning isolation level. To provide the complete emulation of autonomous transactions in SQL Server and to enable a rowversioning isolation level, set the ALLOW_SNAPSHOT_ISOLATION option to ON for each database referenced in the autonomous block. In addition, start the autonomous block with a SNAPSHOT isolation level. Alternatively, you can start an autonomous block with the READ COMMITTED isolation level when the READ_COMMITTED_SNAPSHOT database option is set to ON.
97
Emulating Oracle Packages

Oracle supports encapsulating variables, types, stored procedures, and functions into a package. This section describes SSMA Oracle 3.0 conversion algorithms, which allow packages to be emulated in Microsoft SQL Server 2005. When you convert Oracle packages, you need to convert: Packaged procedures and functions (both public and private) Packaged variables Packaged cursors Package initialization routines Let's examine each of these in turn.
Converting Procedures and Functions

As one of its functions, an Oracle package allows you to group procedures and functions. In SQL Server 2005, you can group procedures and functions by their names. Suppose that you have the following Oracle package: CREATE OR REPLACE PACKAGE MY_PACKAGE IS space varchar(1) := ' '; unitname varchar(128) := 'My Simple Package'; curd date := sysdate; procedure MySimpleProcedure; procedure MySimpleProcedure(s in varchar); function MyFunction return varchar2; END;
CREATE OR REPLACE PACKAGE BODY MY_PACKAGE IS procedure MySimpleProcedure is begin dbms_output.put_line(MyFunction); end; procedure MySimpleProcedure(s in varchar) is begin dbms_output.put_line(s); end; function MyFunction return varchar2 is begin
98
return 'Hello, World!'; end; END; In SQL Server 2005, you can group procedures and functions by giving them names such as Scott.MY_PACKAGE$MySimpleProcedure and Scott.MY_PACKAGE$MyFunction. The naming pattern is <schema name>.<package name>$<procedure or function name>. For detailed information about converting functions, see Migrating Oracle UserDefined Functions. Convert the Invoker rights clause AUTHID to an EXECUTE AS clause, and apply it to all packaged procedures and functions. Also convert the CURRENT_USER argument to the CALLER argument, and convert the DEFINER argument to the OWNER argument.
Converting Overloaded Procedures

You can create overloaded procedures in Oracle (procedures with same name but with different parameters and bodies). SQL Server 2005, in contrast, does not support procedure overloading. Therefore, you should distinguish each procedures instance. The naming pattern could resemble <schema name>.<package name>$<procedure name>$ovl<# of procedure instance>. For example, Scott$MY_PACKAGE$MySimpleProcedure$OVL1 and Scott$MY_PACKAGE$MySimpleProcedure$OVL2. Here's a sample converted Transact-SQL code: create function Scott.MY_PACKAGE$MyFunction() returns varchar(max) as begin return 'Hello, world!' end go create procedure Scott.MY_PACKAGE$MySimpleProcedure$OVL1 as begin print dbo.MY_PACKAGE$MyFunction() end go create procedure Scott.MY_PACKAGE$MySimpleProcedure$OVL2(@s varchar(max)) as begin print @s end
99
go
Converting Packaged Variables

To store packaged variables, establish session-depended storage. SSMA Oracle 3.0 provides an excellent solution. For the task, SSMA uses special tables that reside in a sysdb database. For access to these variables SSMA uses a set of transactionindependent GET and SET procedures and functions. Also, these procedures ensure session independence you should distinguish between variables from different sessions. SSMA distinguishes package variables by SPID (session identifier) and the sessions login time. Note If a packaged variable is declared with an initial value, you must move the initialization to the package's initialization section.
Converting Simple Variables

Simple variables (numeric, varchar, datetime) are stored separately in the appropriate column in table ssma_oracle.db_storage in the sysdb database. In some cases you can replace constant packaged variables with user-defined functions (UDFs) that return the appropriate value. For example, you could convert the packaged variable unitname (from the earlier example) as: create function scott$my_package$unitname() returns varchar(128) as begin return 'My Simple Package' end And, you should convert all references to this variable: dbms_output.put_line(my_package.unitname); To: print scott.my_package$unitname()
Converting Collections and Records

SSMA represents packaged collections and records as XML and stores them as nvarchar(max) in the ssma_oracle.db_storage table. (For more details about collection and records conversion as XML, see Implementing Records and Collections Via XML.)
Converting Packaged Cursors

Convert packaged cursors as GLOBAL cursors with names such as <schema>$<package name>$<cursor name>. Invoke the declaration of cursor in the package initialization section. Make sure that each database method that uses packaged cursors contains the call of the package initialization procedure. Invoke the call before the first usage of the packaged cursor.
100
(For basic information about cursor conversion, see Migrating Oracle Cursors. You will also find a description of converting FOUND, ISOPEN, and NOTFOUND cursor attributes.) Convert the ROWCOUNT attribute as a package variable. Initialize that variable to null in the init section; after OPEN, set its value to zero and increment its value after each FETCH.
Converting Initialization Section

You could convert the initialization section itself as the usual packaged procedure. Within each converted procedure or function, include a call to the initialization procedure. Note Initialization should be performed only one time per session, so the initialization procedure must check each packages initialization status.
Calling Initialization from the Within Procedure

Calling the initialization procedure from within a GET procedure has one main problem: the initialization of packaged variables requires that you insert a number of rows into a storage table and that insertion should be transaction-independent. This is because SSMA uses an extended stored procedure to perform this task.
Calling Initialization from the Within Function

Before you obtain the value from a packaged variable, you should initialize it. To do so, you must call the initialization routine. You cannot call stored procedures directly from within a function, so SSMA calls the initialization procedure by executing an extended stored procedure.
SSMAs Package Variables Implementation Details

SSMA stores package variables in the sysdb database in a ssma_oracle.db_storage table. The table is filtered by SPID and login time. This filtering allows you to distinguish between variables of different sessions. SSMA creates the initialization procedure with a name such as Scott.MY_PACKAGE$SSMA_Initialize_Package. The name pattern is <schema>.<pacakagename>$SSMA_Initialize_Package. At the beginning of each procedure SSMA places a call to the sysdb.ssma_oracle.db_check_init_package procedure. That procedure checks if the package is not yet initialized, and, if not, initializes the package. As a mark of package initialization, SSMA uses package variable with a name such as $<dbname>.<schema>.<package>$init$. If that variable is present in the db_storage table, the package is already initialized, and therefore no initialization call is required. As it is not possible to call a procedure from a UDF, the check for initialization is performed by the function db_fn_check_init_package. In its turn db_fn_check_init_package makes a call to xp_ora2ms_exec2 to execute the package initialization routine. Each initialization procedure cleans the storage table and sets default values for each packaged variable:
100
101
CREATE PROCEDURE dbo.MY_PACKAGE$SSMA_Initialize_Package AS EXECUTE sysdb.ssma_oracle.db_clean_storage EXECUTE sysdb.ssma_oracle.set_pv_varchar 'SYS', 'DBO', 'MY_PACKAGE', 'SPACE', ' ' EXECUTE sysdb.ssma_oracle.set_pv_varchar 'SYS', 'DBO', 'MY_PACKAGE', 'UNITNAME', 'My Simple Package'
Package Conversion Code Example

For further reference, consider the following package conversion example: CREATE FUNCTION dbo.MY_PACKAGE$MyFunction () RETURNS varchar(max) AS BEGIN EXECUTE sysdb.ssma_oracle.db_fn_check_init_package 'SCOTT', 'DBO', 'MY_PACKAGE' RETURN 'Hello, World!' END GO CREATE PROCEDURE dbo.MY_PACKAGE$MySimpleProcedure$1 AS BEGIN EXECUTE sysdb.ssma_oracle.db_check_init_package 'SCOTT', 'DBO', 'MY_PACKAGE' PRINT dbo.MY_PACKAGE$MyFunction() END GO
101
102
CREATE PROCEDURE dbo.MY_PACKAGE$MySimpleProcedure$2 @s varchar(max) AS BEGIN EXECUTE sysdb.ssma_oracle.db_check_init_package 'SCOTT', 'DBO', 'MY_PACKAGE' PRINT @s END GO CREATE PROCEDURE dbo.MY_PACKAGE$SSMA_Initialize_Package AS EXECUTE sysdb.ssma_oracle.db_clean_storage EXECUTE sysdb.ssma_oracle.set_pv_varchar 'SCOTT', 'DBO', 'MY_PACKAGE', 'SPACE', '' EXECUTE sysdb.ssma_oracle.set_pv_varchar 'SCOTT', 'DBO', 'MY_PACKAGE', 'UNITNAME', 'My Simple Package' DECLARE @temp datetime SET @temp = getdate() EXECUTE sysdb.ssma_oracle.set_pv_datetime 'SCOTT', 'DBO', 'MY_PACKAGE', 'CURD', @temp GO
102
103
Emulating Oracle Sequences

When migrating from Oracle to Microsoft SQL Server 2005, you must remember that SQL Server 2005 does not natively support sequences as Oracle does. But with SQL Server Migration Assistant Oracle 2.0 and later, it is easy to simulate Oracle sequences by using a SSMA function. The essential tasks that the sequences simulating engine should provide are: Generate the next value of a sequence by using the NEXTVAL method. Retrieve current value of the sequence by using the CURRVAL method. This value is bound to the current session scope. Keep the sequence value if the transaction is rolled back.
SSMA 1.0 and 2.0 approached the problem by using a single table to hold all the sequence values. Each sequence object was represented by a single row that held the sequence properties, such as sequence name, current value, and increment. An update statement generated the next value and saved the global sequence value. A second update saved the current sequence value within the session scope. The SQL Server analogue of the CURRVAL function read the session scope sequence value. Since the NEXTVAL function was implemented like a function, and a SQL Server limitation does not allow DML statements within functions, the generation of the next value was invoked by the extended stored procedure. That procedure, which is the wrapper that invokes any stored procedure, makes this invocation within a new connection. Thus, using the extended procedure provided for saving the sequence value even if the transaction is rolled back. That approach has a major drawback: poor performance. First, performance suffers because it is necessary to make two updatesupdate the sequence value and update the current value. Second, performance suffers because of the time needed to call the xp_ora2ms_exec2 extended procedure. Most of that time is used to open a new connection. The SSMA 3.0 solution is based on SQL Server identity columns. A table with an identity column is created for every sequence. In the IDENTITY property, the same properties are used as in the ORACLE sequence, except for MAXVALUE, MINVALUE, and CYCLE. The identity value is transaction-independent.
How SSMA 3.0 Creates and Drops Sequences

The following procedures are intended for sequence DML operations, which are creation and dropping. sysdb.ssma_oracle.db_create_sequence @dbname, @schema, @name, @seed, @increment Arguments:
103
104
@dbname: The name of the database that contains the sequence. @schema: The name of the schema that contains the sequence. @name: The sequence name. @seed: The seed value. @increment: The increment value.
The procedure creates a permanent table with the name that identifies the sequence. The table has one identity column of numeric(38) data type named as ID. Also, the db_create_sequence procedure creates a procedure that inserts the default value into the given table. The procedure is created in the same database in which the sequence table is located. Execute permission on the procedure is granted to public when the sequence is created, giving users indirect access to the sequence tables. The following example creates a sequence with the name orders_seq in the target database: exec sysdb.ssma_oracle.db_create_sequence @dbname = 'customers', @name = 'orders_seq', @increment = 2 The following function drops the sequence: sysdb.ssma_oracle.db_drop_sequence @dbname, @schema, @name Arguments @dbname: The database name that contains the sequence. @schema: The schema name that contains the sequence. @name: The sequence name.
The following example drops a sequence named orders_seq in the target database: exec ssma.db_drop_sequence @dbname = 'customers', @name = 'orders_seq'
NEXTVAL and CURRVAL Simulation in SSMA 3.0

In SSMA Oracle 3.0, ORACLE sequence simulation is implemented via both TransactSQL procedures and functions. The implementation of a sequence via a Transact-SQL procedure does not allow using it in DML commands, but significantly improves performance. The NEXTVAL simulation method executes an insert command. The insert command is rolled back immediately to keep the table empty. This approach gains maximum speed. If there is an external transaction, the transaction point is saved and the transaction is rolled back to it after insert. The following procedure is the stored procedure version of NEXTVAL: sysdb.ssma_oracle.db_sp_get_next_sequence_value(
104
105
@dbname, @schema, @name, [@curval] output Arguments: @dbname: The name of the database that contains the sequence. @schema: The name of the schema that contains the sequence. @name: The sequence name. @curval: The current value of a sequence.
The ORACLE sequence implementation via a Transact-SQL function allows using it in DML commands. Since Transact-SQL functions cannot use DML commands and invoke stored procedures, an SSMA NEXTVAL function implementation issues an autonomous command via xp_ora2ms_exec2 to invoke the NEXTVAL procedure version. This causes a decrease in performance as compared with the procedure version. The following function is the user-defined function version of NEXTVAL: sysdb.ssma_oracle.db_get_next_sequence_value(@dbname,@schema,@name) Arguments: @dbname: The name of the database that contains the sequence. @schema: The name of the schema that contains the sequence. @name: The sequence name.
Return types: numeric(38,0). The following function returns the current value of a sequence: sysdb.ssma_oracle. db_get_curval_sequence_value(@dbname,@schema,@name) Arguments @dbname: The database name that contains the sequence. @schema: The schema name that contains the sequence. @name: The sequence name.
Return types: numeric(38,0).
Examples of Conversion Inserting Sequence Values Into a Table

This example increments the employee sequence and uses its value for a new employee inserted into the sample table employees. Oracle
105
106
INSERT INTO employees (id, name) VALUES(employees_seq.nextval, 'David Miller'); Transact-SQL DECLARE @nextval numeric(38, 0) EXECUTE sysdb.ssma_oracle.db_sp_get_next_sequence_value 'customers','dbo','employees_seq', @nextval OUTPUT INSERT employees (id, name) VALUES(@nextval, 'David Miller') The following statement more closely follows the original but takes more time to execute: INSERT employees (id, name) VALUES(sysdb.ssma_oracle.db_get_next_sequence_value ('customers', 'dbo', 'employees_seq'), 'David Miller') The second example adds a new order with the next order number to the order table. Then it adds suborders with this number to the detail order table. Oracle INSERT INTO orders(id, customer_id) SELECT orders_seq.nextval, customer_id from orders_cache; INSERT INTO order_items (order_id, line_item_id, product_id) VALUES (orders_seq.currval, 1, 2412); INSERT INTO order_items (order_id, line_item_id, product_id) VALUES (orders_seq.currval, 2, 3456); Transact-SQL INSERT orders(id, customer_id) SELECT sysdb.ssma_oracle.db_get_next_sequence_value('customers', 'dbo', 'orders_seq'), customer_id from orders_cache; INSERT order_items(order_id, line_item_id, product_id) SELECT sysdb.ssma_oracle.db_get_curval_sequence_value ('customers ', 'dbo', 'orders_seq'), 1, 2412); INSERT order_items(order_id, line_item_id, product_id)
106
107
SELECT sysdb.ssma_oracle.db_get_curval_sequence_value ('customers ', 'dbo', 'orders_seq'), 2, 3456);
Optimization Tips
You can try an easier way to convert your Oracle sequences and get more performance, but only if you know exactly how the sequence is used. For example, if there are no methods using CURRVAL without previous NEXTVAL calls, you need not save and store the current sequence value, and you can use a local variable to store it. That gains performance because its not necessary to use DML routines to save and get the sequence current value. For example, if you have an ORACLE sequence: CREATE SEQUENCE employees_seq INCREMENT BY 1 START WITH 1 You must create a table with an IDENTITY column: create table employees_seq (id numeric(38) identity(1,1)) The statement INSERT INTO..VALUES can be transformed to Transact-SQL in the following way: Oracle begin INSERT INTO employees (id, name) VALUES(employees_seq.nextval, 'David Miller'); end; Transact-SQL begin declare @curval numeric(38) begin tran insert employees_seq default values set @curval=scope_identity() rollback INSERT INTO employees (id, name) VALUES(@curval, 'David Miller'); end; You can wrap the INSERT statement in a stored procedure. Additionally, it should check for an external opened transaction. If one exists, the transaction point should be saved instead of opening a new transaction:
107
108
create proc employees_seq_nextval(@curval numeric(38) out = null) as declare @tran bit set @tran = 0 if @@trancount>0 begin save tran seq set @tran = 1 end else begin tran insert employees_seq default values set @curval=scope_identity() if @tran=1 rollback tran seq else rollback Then the statement can be transformed to the following: begin declare @curval numeric(38) exec employees_seq_nextval @curval out INSERT INTO employees (id, name) VALUES(@curval, 'David Miller'); end; To convert statements where the next value of a sequence is retrieved in DML statements such as INSERT INTO..SELECT, wrap your stored procedure for getting a sequence in a function. You can do so with a master..xp_ora2ms_exec2 extended procedure that helps to invoke stored procedures from a function body. To invoke the xp_ora2ms_exec2 procedure, you must pass the current process id and login time as parameters: create function fn_employees_seq_nextval() RETURNS numeric(38,0) as begin declare @curval numeric(38,0) declare @spid int, @login_time datetime select @spid = sysdb.ssma_oracle.get_active_spid(),@login_time = sysdb.ssma_oracle.get_active_login_time() exec master..xp_ora2ms_exec2 @spid,@login_time,'orders','dbo', 'employees_seq_nextval',@dbname,@schema,@name,@curval output return @curval
108
109
end
Migrating Hierarchical Queries

This section describes problems and solutions when migrating Oracle hierarchical queries. Oracle provides the following syntax elements to build hierarchical queries: 1. The START WITH condition. Specifies the hierarchy's root rows. 2. The CONNECT BY condition. Specifies the relationship between the hierarchy's parent rows and child rows. 3. The PRIOR operator. Refers to the parent row. 4. The CONNECT_BY_ROOT operator. Retrieves the column value from the root row. 5. The NO_CYCLE parameter. Instructs the Oracle Database to return rows from a query, even if a cycle exists in the data. 6. The LEVEL, CONNECT_BY_ISCYCLE, and CONNECT_BY_ISLEAF pseudocolumns. 7. The SYS_CONNECT_BY_PATH function. Retrieves the path from the root to node. 8. The ORDER SIBLINGS BY clause. Applies ordering to the siblings of the hierarchy. Oracle processes hierarchical queries in this order: 1. Evaluates a join first, if one is present, whether the join is specified in the FROM clause or with WHERE clause predicates. 2. Evaluates the CONNECT BY condition. 3. Evaluates any remaining WHERE clause predicates. Oracle then uses the information from these evaluations to form the hierarchy as follows: 4. Oracle selects the hiearchy's root row(s) (those rows that satisfy the START WITH condition). 5. Oracle selects each root row's child rows. Each child row must satisfy the CONNECT BY condition with respect to one of the root rows. 6. Oracle selects successive generations of child rows. Oracle first selects the children of the rows returned in Step 2, and then the children of those children, and so on. Oracle always selects children by evaluating the CONNECT BY condition with respect to a current parent row. 7. If the query contains a WHERE clause without a join, Oracle eliminates all rows from the hierarchy that do not satisfy the WHERE clause's conditions. Oracle evaluates that condition for each row individually, rather than removing all the children of a row that does not satisfy the condition. 8. Oracle returns the rows in the order shown in Figure 3. In the figure, children appear below their parents.
109
110
1 2 3 5 4 6 7 8 10 11 9 12
Figure 3: An example of the Oracle tree traversal order In SQL Server 2005, you can use a recursive common table expression (CTE) to retrieve hierarchical data. For more about information about the recursive CTE, see Recursive Queries Using Common Table Expression in SQL Server 2005 Books Online. To migrate an Oracle hierarchical query, follow these common rules: Use the START WITH condition in the anchor member subquery of the CTE. If there is no START WITH condition, the result of the anchor member subquery should consists of all root rows. Since the START WITH condition is processed before the WHERE condition, ensure that the anchor member subquery returns all necessary rows. This is sometimes needed to move some WHERE conditions from the CTE to the base query. Use the CONNECT BY condition in the recursive member subquery. The result of the recursive member subquery should consist of all child rows joined with CTE itself on the CONNECT BY condition. Use the CTE itself as the inner join member in the recursive subquery. Replace the PRIOR operator with the CTE recursive reference. The base query consists of the selection from the CTE, and the WHERE clause to provide all necessary restrictions. Emulate the LEVEL pseudocolumn with a simple expression as described in SQL Server 2005 Books Online. Emulate the sys_connect_by_path function with an expression that concatenates column values from recursive CTE references.
This approach makes hierarchical data retrieval possible. But the way to traverse trees is different in Oracle. To emulate how Oracle orders returned data, you can create additional expressions to use in the ORDER BY clause. The expression should evaluate some path from the root to the specific row by using a unique row number at each tree level. You can use the ROW_NUMBER function for this purpose. You can also add expressions based on the columns values to provide ORDER SIBLINGS BY functionality.
110
111
You can use GROUP BY and HAVING clauses only in the base query. SQL Server 2005 cannot detect the cycles in a hierarchical query. You can control the recursion level with the MAXRECURSION query hint. Note that SSMA does not support the following features: The CONNECT_BY_ROOT operator The NO_CYCLE parameter The CONNECT_BY_ISCYCLE and CONNECT_BY_ISLEAF pseudocolumns The SYS_CONNECT_BY_PATH function The ORDER SIBLINGS BY clause
Example: The following example code demonstrates how to migrate a simple hierarchical query: Oracle SELECT "NAME", "PARENT", LEVEL FROM COMPANY START WITH ("NAME" = 'Company Ltd') CONNECT BY ("PARENT" = PRIOR "NAME"); SQL Server WITH h$cte AS ( SELECT COMPANY.NAME, COMPANY.PARENT, 1 AS LEVEL, CAST(row_number() OVER( ORDER BY @@spid) AS varchar(max)) AS path FROM dbo.COMPANY WHERE ((COMPANY.NAME = 'Company Ltd')) UNION ALL SELECT COMPANY.NAME, COMPANY.PARENT, h$cte.LEVEL + 1 AS LEVEL, path + ',' + CAST(row_number() OVER( ORDER BY @@spid) AS varchar(max)) AS path FROM dbo.COMPANY, h$cte WHERE ((COMPANY.PARENT = h$cte.NAME)) ) SELECT h$cte.NAME, h$cte.PARENT, h$cte.LEVEL FROM h$cte ORDER BY h$cte.path Note The ROW_NUMBER() function evaluates the path column to provide Oracle nodes ordering.
Emulating Oracle Exceptions

This section describes problems and solutions for migrating Oracle exception mechanisms. The Oracle exception model differs from Microsoft SQL Server 2005 both in exception raising and exception handling. It is preferable to use the SQL Server exceptions model during Oracle PL/SQL code migration. At the same time, SSMA provides common emulation methods to cover almost all Oracle exception-model features.
111
112
Exception Raising
The Oracle exception raising model comprises the following features: The SELECT INTO statement causes an exception if not exactly one row is returned. The RAISE statement can raise any exception, including system errors. User-defined exceptions can be named and raised by name. The RAISE_APPLICATION_ERROR procedure can generate exceptions with a custom number and message.
If the SELECT statement can return zero, one, or many rows, it makes sense to check the number of rows by using the @@ROWCOUNT function. Its value can be used to emulate any logic that was implemented in Oracle by using the TOO_MANY_ROWS or NO_DATA_FOUND exceptions. Normally, the SELECT INTO statement should return only one row, so in most cases you dont need to emulate this type of exception raising. For example: Oracle BEGIN SELECT <expression> EXCEPTION WHEN NO_DATA_FOUND THEN <Statements> END SQL Server 2005 SELECT <variable> = <expression> FROM <table> IF @@ROWCOUNT = 0 BEGIN <Statements> END Also, PL/SQL programs can sometimes use user-defined exceptions to provide business logic. These exceptions are declared in the PL/SQL block's declaration section. In Transact-SQL, you can replace that behavior by using flags or custom error numbers. For example: Oracle declare myexception exception; BEGIN IF <condition> THEN
112
INTO <variable> FROM <table>;
113
RAISE myexception; END IF; EXCEPTION WHEN myexception THEN <Statements> END SQL Server 2005 BEGIN TRY IF <condition> RAISERROR (myexception, 16, 1) END TRY BEGIN CATCH IF ERROR_MESSAGE() = myexception BEGIN <Statements> END ELSE <rest_of_handler code> END CATCH If the user-defined exception is associated with some error number by using pragma EXCEPTION_INIT, you can handle the system error in the CATCH block as described later. To emulate the raise_application_error procedure and the system predefined exception raising, you can use the RAISERROR statement with a custom error number and message. Also, change the application logic in that case to support SQL Server 2005 error numbers. Note that SQL Server 2005 treats exceptions with a severity of less than 11 as information messages. To interrupt execution and pass control to a CATCH block, the exception severity must be at least 11. (In most cases you should use a severity level of 16.)
Exception Handling
Oracle provides the following exception-handling features:
113
114
The EXCEPTION block The WHEN THEN block The SQLCODE and SQLERRM system functions Exception re-raising
Transact-SQL implements error handling with a TRY..CATCH construct. To provide exception handling, place all trying statements into a BEGIN TRY END TRY block, while placing the exception handler itself into a BEGIN CATCH END CATCH block. TRY CATCH blocks also can be nested. To recognize the exception (WHEN THEN functionality), you can use the following system functions: error_number error_line error_procedure error_severity error_state error_message
You can use the error_number and error_message functions instead of the SQLCODE and SQLERRM Oracle functions. Note that error messages and numbers are different in Oracle and SQL Server, so they should be translated during migration. For example: Oracle BEGIN INSERT INTO <table> VALUES EXCEPTION WHEN DUP_VAL_ON_INDEX THEN <Statements> END SQL Server 2005 BEGIN TRY INSERT INTO <table> VALUES END TRY BEGIN CATCH
114
115
IF ERROR_NUMBER() = 2627 <Statements> END CATCH Unfortunately, SQL Server 2005 does not support exception re-raising. If the exception is not handled, it can be passed to the calling block by using the RAISERROR statement with a custom error number and appropriate message.
SSMA Exceptions Migration

Next, let's examine how SSMA provides a common approach to full emulation of Oracle exception functionality. Oracle exceptions are encoded into a character string according to the following rules: Predefined exceptions (exceptions declared in some system package and not assigned to any error number) are encoded this way: oracle:{<OWNER_NAME>|<PACKAGE_NAME>|<EXCEPTION_NAME>} Where: PACKAGE_NAME: Package name where the exception is declared in upper case. OWNER_NAME: The owner name of the package, in upper case. EXCEPTION_NAME: The exception name itself, in upper case.
User-defined exceptions names declared in modules such as stored procedures acquire local: prefix: local:oracle:{<OWNER_NAME>|<MODULE_NAME>}:<EXCEPTION_NAME>:N Where: OWNER_NAME: The owner name of the module where the exception is declared. MODULE_NAME: The name of the stored procedure where the exception is declared. N: An integer value that provides scope name uniqueness.
User-defined exception names declared in anonymous PL/SQL blocks (test statements) have additional PL\SQL keyword: local:PL\SQL:<EXCEPTION_NAME>:N Where N is the integer value that provides scope name uniqueness.
To support Oracle error numbers, system errors are stored in the following format: ORAXXXXXX
115
116
During migration SSMA performs the following steps: 1. All statements between BEGIN and EXCEPTION are enclosed with BEGIN TRY END TRY. 2. An exception handler is placed into BEGIN CATCH END CATCH. 3. Error numbers are translated to Oracle format by using the sysdb.ssma_oracle_get_oracle_exception_id() function. That function returns an exception identifier as a character string as described earlier. Each WHENTHEN statement is migrated to an IF statement that compares the exception identifier to constant exception names that are translated according to the same rules. 4. The exception handler for OTHERS, if any, is migrated as an alternative execution block after all handlers. 5. If there is no OTHERS exception handler, the exception is re-raised by the special UDF sysdb.ssma_oracle.ssma_rethrowerror that emulates re-raising using a custom error number. It also emulates a RAISE statement with no exception name. 6. To emulate predefined Oracle exceptions NO_DATA_FOUND and TOO_MANY_ROWS, the special stored procedure EXEC sysdb.ssma.db_error_exact_one_row_check @@ROWCOUNT is placed after all SELECT statements. The procedure checks the row count and raises an exception with the custom number 59999 and the message ORA+00100 or ORA-01422, depending on its value. 7. The number 59999 is used for all Oracle system, user-defined, or predefined exceptions. 8. The RAISE statement is migrated to the RAISERROR statement with an 59999 error number and the exception identifier as a message. The exception identified is formed as described earlier. 9. To emulate the raise_application_error procedure, there is the additional error number 59998. The procedure call is replaced by a RAISERROR call with error number 59998 and the following string as a message: ORA<error_number>:<message> For example: RAISERROR (59998, 16, 1,ORA-20000:test) 10. All exceptions are raised with severity level 16 to provide handling by a CATCH block. 11. sysdb.ssma.db_error_sqlcode UDF emulates the SQLCODE function. It returns an Oracle error number. 12. Either sysdb.ssma.db_error_sqlerrm_0 or sysdb.ssma.db_error_sqlerrm_1 emulates the SQLERRM function, depending on the parameters. 13. SSMA does not support using the SQLCODE and SQLERRM functions outside of an EXCEPTION block.
116
117
Migrating Oracle Cursors

This section describes problems and solutions for Oracle cursor migration. Keep in mind that a packaged cursor needs special handling during conversion. For details, see Emulating Oracle Packages. Oracle always requires that cursors be used with SELECT statements, regardless of the number of rows requested from the database. In Microsoft SQL Server 2005, a SELECT statement that is not enclosed within a cursor returns rows to the client as a default result set. This is an efficient way to return data to a client application. SQL Server 2005 provides two interfaces for cursor functions: When cursors are used in Transact-SQL batches or stored procedures, SQL statements can declare, open, and fetch from cursorsas well as positioned updates and deletes. When cursors from a DB-Library, ODBC, or OLEDB program are used, the SQL Server client libraries transparently call built-in server functions to handle cursors more efficiently.
Syntax
The following table shows cursor statement syntax in both platforms. Operation
Declaring a cursor
Oracle
CURSOR cursor_name [(cursor_parameter(s))] IS select_statement;
Microsoft SQL Server

DECLARE cursor_name CURSOR [LOCAL | GLOBAL] [FORWARD_ONLY | SCROLL] [STATIC | KEYSET | DYNAMIC | FAST_FORWARD] [READ_ONLY | SCROLL_LOCKS | OPTIMISTIC] [TYPE_WARNING] FOR select_statement [FOR UPDATE [OF column_name [,n]]]
Ref cursor type definition
TYPE type_name IS REF CURSOR [RETURN { {db_table_name | cursor_name | cursor_variable_name} % ROWTYPE | record_name % TYPE | record_type_name | ref_cursor_type_name}];
See below.
Opening a cursor
OPEN cursor_name
OPEN cursor_name
117
118
Operation
Oracle
[(cursor_parameter(s))];
Microsoft SQL Server
Cursor attributes
{ cursor_name | cursor_variable_name | :host_cursor_variable_name} % {FOUND | ISOPEN | NOTFOUND | ROWCOUNT}
See below.
SQL cursors
SQL % {FOUND | ISOPEN | NOTFOUND | ROWCOUNT | BULK_ROWCOUNT(index) | BULK_EXCEPTIONS(index).{ERROR_INDEX | ERROR_CODE}}
See below.
Fetching from cursor
FETCH cursor_name INTO variable(s)
FETCH [[NEXT | PRIOR | FIRST | LAST | ABSOLUTE {n | @nvar} | RELATIVE {n | @nvar}] FROM] cursor_name [INTO @variable(s)]
Update fetched row
UPDATE table_name SET statement(s) WHERE CURRENT OF cursor_name;
UPDATE table_name SET statement(s) WHERE CURRENT OF cursor_name
Delete fetched row
DELETE FROM table_name WHERE CURRENT OF cursor_name;
DELETE FROM table_name WHERE CURRENT OF cursor_name
Closing cursor Remove cursor data structures OPEN FOR cursors
CLOSE cursor_name;
CLOSE cursor_name DEALLOCATE cursor_name
N/A
OPEN {cursor_variable_name | :host_cursor_variable_name} FOR dynamic_string [using_clause]
See below.
Declaring a Cursor
Although the Transact-SQL DECLARE CURSOR statement does not support cursor arguments, it does support local variables. The values of these local variables are used in the cursor when it is opened. Microsoft SQL Server 2005 offers numerous additional capabilities in its DECLARE CURSOR statement.
118
119
The INSENSITIVE option defines a cursor that makes a temporary copy of the data to be used by that cursor. The temporary table answers all of the requests to the cursor. Consequently, modifications made to base tables are not reflected in the data returned by fetches made to that cursor. Data accessed by this cursor type cannot be modified. Applications can request a cursor type, and then execute a Transact-SQL statement that is not supported by server cursors of the type requested. SQL Server returns an error that indicates that the cursor type has changed, or, given a set of factors, implicitly converts a cursor. The following table shows the factors that trigger SQL Server to implicitly convert a cursor from one type to another. Step Conversion triggered by
1 2 3 4 5 Query FROM clause references no tables Query contains: select list aggregates GROUP BY UNION DISTINCT HAVING Query generates an internal work table, for example the columns of an ORDER BY are not covered by an index
Forward- Keysetonly driven

Becomes static Becomes static Becomes keyset Becomes static Becomes static
Go Dynamic to step
Becomes static Becomes static Becomes keyset Becomes keyset Done Done 5 5 Done
Query references remote tables in linked Becomes servers keyset Query references at least one table without a unique index. Transact-SQL cursors only. Becomes static
The SCROLL option allows backward, absolute, and relative fetches, and also forward fetches. A scroll cursor uses a keyset cursor model in which committed deletes and updates made to the underlying tables by any user are reflected in subsequent fetches. This is true only if the cursor is not declared with the INSENSITIVE option. If the READ ONLY option is chosen, updates are prevented from occurring against any row within the cursor. That option overrides the default capability of a cursor to be updated. The UPDATE [OF column_list] statement defines updatable columns within the cursor. If [OF column_list] is supplied, only the columns listed allow modifications. If a list is not supplied, all columns can be updated, unless the cursor is defined as READ ONLY. Note that the name scope for a SQL Server cursor is the connection itself. That differs from the name scope of a local variable. A second cursor with the same name as an existing cursor on the same user connection cannot be declared until the first cursor is deallocated. Following are descriptions of the SSMA algorithm of cursor conversion for several specific cases. If the cursor is declared in the local subprogram, SSMA converts it to: DECLARE cursor_name CURSOR LOCAL FOR select_statement SSMA puts this cursor declaration directly before the OPEN statement that opens the cursor and removes the RETURN clause.
119
120
Instead of the cursor declaration, SSMA generates a variable declaration. If the cursor is declared as a public packaged cursor, SSMA converts it into a global cursor: DECLARE cursor_name CURSOR FOR select_statement You can find more details in Emulating Oracle Packages. SSMA declares a local variable for each parameter with the following naming pattern: @CURSOR_PARAM_<cursor_name>_<parameter_name> The data type is converted according to the effective SSMA type mapping for local variables. SSMA removes a REF cursor definition and converts it to a variable declaration as follows: cursor_variable_declaration ::= cursor_variable_name type_name; Convert to: @cursor_variable_name CURSOR;
Opening a Cursor
Unlike PL/SQL, Transact-SQL does not support passing arguments to a cursor when it is opened. When a Transact-SQL cursor is opened, the result set membership and ordering are fixed. Updates and deletes that have been committed against the cursor's base tables by other users are reflected in fetches made against all cursors defined without the INSENSITIVE option. In the case of an INSENSITIVE cursor, a temporary table is generated. SSMA tests to see whether the cursor was declared with formal cursor parameters. For each formal cursor parameter, generate a SET statement before the cursor declaration to assign the actual cursor parameter to the appropriate local variable: SET @CURSOR_PARAM_<cursor_name>_<parameter_name> = actual_cursor_parameter If there is no actual parameter for the formal parameter, use a DEFAULT expression as declared in the cursor parameter declaration: SET @CURSOR_PARAM_<cursor_name>_<parameter_name> = expression
Fetching Data
Oracle cursors can move in a forward direction onlythere is no backward or relative scrolling capability. SQL Server 2005 cursors can scroll forward and backward with the fetch options shown in the following table. You can use these fetch options only when the cursor is declared with the SCROLL option.
120
121
Scroll option NEXT
Description Returns the result set's first row if this is the first fetch against the cursor; otherwise, moves the cursor one row in the result set. NEXT is the primary method to move through a result set. NEXT is the default cursor fetch. Returns the previous row in the result set. Moves the cursor to the first row in the result set and returns the first row. Moves the cursor to the last row in the result set and returns the last row. Returns the nth row in the result set. If n is a negative value, the returned row is the nth row counting backward from the last row of the result set. Returns the nth row after the currently fetched row. If n is a negative value, the returned row is the nth row counting backward from the cursor's relative position.
PRIOR FIRST LAST ABSOLUTE n
RELATIVE n
The Transact-SQL FETCH statement does not require the INTO clause. If return variables are not specified, the row is automatically returned to the client as a single-row result set. However, if your procedure must get the rows to the client, a noncursor SELECT statement is much more efficient. Issues SSMA recognizes the following FETCH formats. FETCH INTO <record>: SSMA splits the record into its components and fetches each variable separately. FETCH BULK COLLECT INTO: There is no solution for BULK COLLECT fetch implemented in SSMA Oracle 3.0. See the suggestions for manually emulating this FETCH in Migrating Oracle Collections and Records.
The @@FETCH_STATUS function is updated following each FETCH. This function resembles the PL/SQL CURSOR_NAME%FOUND and CURSOR_NAME%NOTFOUND variables. The @@FETCH_STATUS function is set to the value of 0 following a successful fetch. If the fetch tries to read beyond the end of the cursor, a value of -1 is returned. If the requested row was deleted from the table after the cursor was opened, the @@FETCH_STATUS function returns -2. The value of -2 usually occurs only in a cursor that was declared with the SCROLL option. That variable must be checked following each fetch to ensure the validity of the data. How SSMA Converts Cursor Attributes SSMA converts cursor attributes as follows: FOUND attribute: Converts to @@FETCH_STATUS = 0/ NOTFOUND attribute: Converts to @@FETCH_STATUS ISOPEN attribute: Converts as follows: For global cursors: (CURSOR_STATUS(global, N<cursor_name>) > -1) For local cursors: (CURSOR_STATUS(local, N<cursor_name>) > -1) For a cursor variable:
121
<> 0
122
(CURSOR_STATUS(variable, N@<cursor_variable_name>) > -1) ROWCOUNT attribute: To convert ROWCOUNT, SSMA does the following: 1. Generates a declaration of an INT variable with the name @v_<cursor_name | cursor_variable_name >_rowcount at the beginning of the block where cursor was declared (see Declaring a Cursor). 2. Before the OPEN statement for the cursor or cursor variable, puts variable initialization code: SET @v_<cursor_name | cursor_variable_name >_rowcount = 0 3. Immediately after the cursor FETCH statement, SSMA puts: IF @@FETCH_STATUS = 0 SET @v_<cursor_name | cursor_variable_name >_rowcount = @v_<cursor_name | cursor_variable_name >_rowcount + 1 4. SSMA converts cursor_name%ROWCOUNT to: @v_<cursor_name | cursor_variable_name >_rowcount How SSMA Converts SQL Cursor Attributes FOUND: Converts to (@@ROWCOUNT > 0) NOTFOUND: Converts to (@@ROWCOUNT = 0) ISOPEN: Converts to any condition that is always false, for example (1=2) ROWCOUNT: Converts to @@ROWCOUNT. For example: Oracle IF SQL%FOUND THEN ; MSSQL IF @@ROWCOUNT > 0 SQL Server does not support Oracles cursor FOR loop syntax, but SSMA can convert these loops. See the examples in the previous section. How SSMA Converts OPEN FOR Cursors The SSMA conversion option Convert OPEN-FOR statement for subprogram out parameters (see Figure 4) is used because there is an ambiguity when a REF CURSOR output parameter is opened in the procedure. The REF CURSOR might be fetched in the caller procedure (SSMA does not support this usage) or used directly by the application (SSMA can handle this if the option is set to Yes).
122
123
Figure 4: Setting the Convert OPEN-FOR statement for subprogram out parameters SSMA conversion option Generally, an OPEN-FOR statement is converted in the following way: If the OPEN-FOR statement is used for a local cursor variable, SSMA converts it to: SET @cursor_variable_name = CURSOR FOR select_statement If the OPEN-FOR statement is used for an output procedure parameter and the option is set to ON, its converted to: select_statement Which returns a result set to the client application. If the OPEN-FOR statement is used for an output procedure parameter and the option is set to OFF, SSMA generates the error Conversion of OPENFOR statement is disabled.
The OPEN-FOR-USING statement when it is used for a local cursor variable, is converted somewhat differently as in the following steps. 1. SSMA generates the following code: DECLARE @auxiliary_cursor_definition_sql$N NVARCHAR(max), @auxiliary_exec_param$N NVARCHAR(max) IF (cursor_status('variable', N'<cursor_variable_name>') > DEALLOCATE <cursor_variable_name> SET @auxiliary_exec_param$N = '[@auxiliary_paramN <datatype> [OUTPUT],] @auxiliary_tmp_cursor$N cursor OUTPUT' -2)
123
124
2. Then SSMA generates the following error message: OPEN ... FOR statement will be converted, but the dynamic string must be converted manually. 3. It adds the following line into the Attempted target code section: SET @auxiliary_cursor_definition_sql$N = ('SET @auxiliary_tmp_cursor = CURSOR LOCAL FOR ' + <dynamic_string>+ '; OPEN @auxiliary_tmp_cursor') SSMA uses integer value N as part of declared variable names to provide scope name uniqueness. Parameter @auxiliary_paramN is declared in @auxiliary_exec_param$N for every bind_argument of the using_clause. SSMA determines the arguments' datatype to declare the parameters. And it specifies OUTPUT in case of a bind_argument specified with an OUT or an IN_OUT option. 4. SSMA generates the following code: EXEC sp_executesql @auxiliary_cursor_definition_sql$N, @auxiliary_exec_param$N, [bind_argument [OUTPUT], ] cursor_variable_name OUTPUT Where bind_argument is the bind_argument from the using_clause. Specify OUTPUT for the bind arguments that were declared with OUTPUT specified in @auxiliary_exec_param$N. The OPEN-FOR-USING statement when it is used for an output procedure parameter and the Convert OPEN-FOR statement for subprogram out parameters option is set to ON: 1. SSMA generates the following code: DECLARE @auxiliary_cursor_definition_sql$N NVARCHAR(max), @auxiliary_exec_param$N NVARCHAR(max) SET @auxiliary_exec_param$N = '[@auxiliary_paramN <datatype> [OUTPUT]]' 2. Then it generates the following error message: 'OPEN ... FOR statement will be converted, but the dynamic string must be converted manually.' 3. SSMA puts the following line into the Attempted target code section: SET @auxiliary_cursor_definition_sql$N = ( <dynamic_string>) SSMA uses the integer value N as part of the declared variable names to provide scope name uniqueness. 4. The @auxiliary_paramN parameter is declared in @auxiliary_exec_param$N for every bind_argument of the using_clause. SSMA determines the data type of the argument to declare the parameters. It specifies OUTPUT if a bind_argument is specified with an OUT or an IN_OUT option. 5. SSMA generates the following code: EXEC sp_executesql @auxiliary_cursor_definition_sql$N, @auxiliary_exec_param$N [, bind_argument ]
124
125
Where bind_argument is the bind_argument from the using_clause.
CURRENT OF Clause
The CURRENT OF clause syntax and function for updates and deletes is the same in both PL/SQL and Transact-SQL. A positioned UPDATE or DELETE is performed against the current row within the specified cursor.
Closing a Cursor
The Transact-SQL CLOSE CURSOR statement closes the cursor but leaves the data structures accessible for reopening. The PL/SQL CLOSE CURSOR statement closes and releases all data structures. Transact-SQL requires the DEALLOCATE CURSOR statement to remove the cursor data structures. The DEALLOCATE CURSOR statement differs from CLOSE CURSOR in that a closed cursor can be reopened. The DEALLOCATE CURSOR statement releases all data structures associated with the cursor and removes the definition of the cursor. During conversion, SSMA adds a DEALLOCATE CURSOR statement. The source statement: CLOSE { cursor_name | cursor_variable_name | :host_cursor_variable_name} becomes two statements in SQL Server: CLOSE { cursor_name | @cursor_variable_name } DEALLOCATE { cursor_name | @cursor_variable_name }
Examples of SSMA 3.0 Conversion FOR Loop Cursor Conversion

Oracle CREATE OR REPLACE PROCEDURE db_proc_for_loop (mgr_param NUMBER) AS BEGIN DECLARE CURSOR emp_cursor IS SELECT empno, ename FROM emp WHERE mgr = mgr_param; BEGIN FOR emp_rec IN emp_cursor LOOP UPDATE emp SET sal = sal * 1.1; END LOOP;
125
126
END; END db_proc_for_loop; SQL Server CREATE PROCEDURE dbo.DB_PROC_FOR_LOOP @mgr_param int AS BEGIN BEGIN DECLARE @v_emp_cursor_rowcount int DECLARE @emp_rec xml DECLARE emp_cursor CURSOR LOCAL FOR SELECT EMP.EMPNO, EMP.ENAME FROM dbo.EMP WHERE EMP.MGR = @mgr_param SET @v_emp_cursor_rowcount = 0 OPEN emp_cursor WHILE 1 = 1 BEGIN DECLARE @emp_rec$empno float(53) DECLARE @emp_rec$ename varchar(max) FETCH emp_cursor INTO @emp_rec$empno, @emp_rec$ename
126
127
IF @@FETCH_STATUS = 0 SET @v_emp_cursor_rowcount = @v_emp_cursor_rowcount + 1 SET @emp_rec = sysdb.ssma_oracle.SetRecord_varchar(@emp_rec, N'ENAME', @emp_rec$ename) SET @emp_rec = sysdb.ssma_oracle.SetRecord_float(@emp_rec, N'EMPNO', @emp_rec$empno) IF @@FETCH_STATUS = BREAK UPDATE dbo.EMP SET SAL = EMP.SAL * 1.1 END CLOSE emp_cursor DEALLOCATE emp_cursor END END -1
Cursor with Parameters

Oracle CREATE OR REPLACE PROCEDURE AS CURSOR rank_cur (id_ NUMBER, sn CHAR) IS SELECT rank, rank_name FROM rank_table WHERE r_id = id_ AND r_sn = sn; BEGIN OPEN rank_cur (1, 'c'); OPEN rank_cur (2, 'd'); END; db_proc_cursor_parameters
127
128
SQL Server CREATE PROCEDURE dbo.DB_PROC_CURSOR_PARAMETERS AS BEGIN DECLARE @v_rank_cur_rowcount int DECLARE @CURSOR_PARAM_rank_cur_id_$2 float(53) SET @CURSOR_PARAM_rank_cur_id_$2 = 1 DECLARE @CURSOR_PARAM_rank_cur_sn$2 varchar(max) SET @CURSOR_PARAM_rank_cur_sn$2 = 'c' DECLARE rank_cur CURSOR LOCAL FOR SELECT RANK_TABLE.RANK, RANK_TABLE.RANK_NAME FROM dbo.RANK_TABLE WHERE RANK_TABLE.R_ID = @CURSOR_PARAM_rank_cur_id_$2 AND RANK_TABLE.R_SN = @CURSOR_PARAM_rank_cur_sn$2 SET @v_rank_cur_rowcount = 0 OPEN rank_cur DECLARE @CURSOR_PARAM_rank_cur_id_ float(53) SET @CURSOR_PARAM_rank_cur_id_ = 2 DECLARE @CURSOR_PARAM_rank_cur_sn varchar(max) SET @CURSOR_PARAM_rank_cur_sn = 'd'
128
129
DECLARE rank_cur CURSOR LOCAL FOR SELECT RANK_TABLE.RANK, RANK_TABLE.RANK_NAME FROM dbo.RANK_TABLE WHERE RANK_TABLE.R_ID = @CURSOR_PARAM_rank_cur_id_ AND RANK_TABLE.R_SN = @CURSOR_PARAM_rank_cur_sn SET @v_rank_cur_rowcount = 0 OPEN rank_cur END
Cursor Attributes Conversion

Oracle CREATE OR REPLACE PROCEDURE db_proc_cursor_attributes AS ID number; CURSOR Cur IS SELECT ID FROM rank_table; BEGIN IF NOT Cur%ISOPEN THEN OPEN Cur; END IF; LOOP FETCH Cur INTO ID; EXIT WHEN Cur%NOTFOUND; dbms_output.put_line(to_char(ID + Cur%ROWCOUNT)); END LOOP; CLOSE Cur; END; SQL Server CREATE PROCEDURE dbo.DB_PROC_CURSOR_ATTRIBUTES AS BEGIN
129
130
DECLARE @ID float(53), @v_Cur_rowcount int IF NOT CURSOR_STATUS('local', N'Cur') > BEGIN DECLARE Cur CURSOR LOCAL FOR SELECT RANK_TABLE.ID FROM dbo.RANK_TABLE SET @v_Cur_rowcount = 0 OPEN Cur END WHILE 1 = 1 BEGIN FETCH Cur INTO @ID IF @@FETCH_STATUS = 0 SET @v_Cur_rowcount = @v_Cur_rowcount + 1 IF @@FETCH_STATUS = BREAK PRINT CAST(@ID + CAST(@v_Cur_rowcount AS float(53)) AS varchar(max)) END CLOSE Cur -1 -1
130
131
DEALLOCATE Cur END
Simulating Oracle Transactions in SQL Server 2005

When migrating from Oracle to Microsoft SQL Server 2005, you must account for the differences in their default transaction management behavior. SSMA Oracle 3.0 can convert Oracles transaction-related statements, but you will find additional issues to consider, as described in this section. When the SSMA Convert transaction processing statements option is turned on, SSMA tries to convert the Oracle statements for transaction management (COMMIT, ROLLBACK, and SAVEPOINT), but it does not add any statement for opening a transaction. So, you must decide which transaction management model to use in your application. Since SQL Server 2005 now allows optimistic escalation mode, choose between a pessimistic and an optimistic concurrency model.
Choosing a Transaction Management Model

In Oracle, a transaction automatically starts when an insert, update, or delete operation is performed. An application must issue a COMMIT command to save changes to the database. If a COMMIT is not performed, all changes are rolled back or undone automatically. By default, SQL Server 2005 automatically performs a COMMIT statement after every insert, update, or delete operation. Because the data is automatically saved, you cannot roll back any changes. You can start transactions in SQL Server 2005 as autocommit, implicit, or explicit transactions. Autocommit is the default behavior; you can use implicit or explicit transaction modes to change the default behavior.
Autocommit Transactions
Autocommit transactions are the default mode for SQL Server 2005. Each individual Transact-SQL statement is committed when it completes. You do not have to specify any statements to control transactions.
Implicit Transactions
As in Oracle, an implicit transaction starts whenever an INSERT, UPDATE, DELETE, or other data manipulating function is performed. To allow implicit transactions, use the SET IMPLICIT_TRANSACTIONS ON statement. If this option is ON and there are no outstanding transactions, every SQL statement automatically starts a transaction. If there is an open transaction, no new transaction will start. The user must explicitly commit the open transaction with the COMMIT TRANSACTION statement for the changes to take effect and for all locks to be released.
Explicit Transactions
An explicit transaction is a grouping of SQL statements surrounded by BEGIN TRAN and COMMIT or ROLLBACK commands. Therefore, for the complete emulation of the Oracle transaction behavior, use a SET IMPLICIT_TRANSACTIONS ON statement.
131
132
Choosing a Concurrency Model

Consider changing your application's isolation level. In a multi-user environment, there are two models for updating data in a database: Pessimistic concurrency involves locking the data at the database when you read it. You exclusively lock the database record and don't allow anyone to touch it until you are done modifying and saving it back to the database. You have 100 percent assurance that nobody will modify the record while you have it checked out. Another person must wait until you have made your changes. Pessimistic concurrency complies with ANSI-standard isolation levels as defined in the SQL-99 standard. Microsoft SQL Server 2005 has four pessimistic isolation levels: READ COMMITTED READ UNCOMMITTED REPEATABLE READ SERIALIZABLE
Optimistic concurrency means that you read the database record but don't lock it. Anyone can read and modify the record at any time, so the record might be modified by someone else before you modify and save it. If data is modified before you save it, a collision occurs. Optimistic concurrency is based on retaining a view of the data as it is at the start of a transaction. This model is embodied in Oracle. The transaction isolation level that implements an optimistic form of database concurrency is called a row versioning-based isolation level.
Since SQL Server 2005 has completely controllable isolation-level models, you can choose the most appropriate isolation level. To control a row-versioning isolation level, use the SET TRANSACTION ISOLATION LEVEL command. SNAPSHOT is the isolation level that is similar to Oracle and does optimistic escalations.
Make Transaction Behavior Look Like Oracle

For complete transaction management emulation in SQL Server 2005 and using a row-versioning isolation level, set the ALLOW_SNAPSHOT_ISOLATION option to ON for each database that is referenced in the Transact-SQL object (view, procedure, function, or trigger). In addition, either each Transact-SQL object must be started with a SNAPSHOT isolation level or else this level must be set on each client connection. Alternatively, the autonomous block must be started with the READ COMMITTED isolation level with the READ_COMMITTED_SNAPSHOT database option set to ON.
Simulating Oracle Autonomous Transactions

This section describes how SSMA Oracle 3.0 handles autonomous transactions (PRAGMA AUTONOMOUS_TRANSACTION). These autonomous transactions do not have direct equivalents in Microsoft SQL Server 2005. When you define a PL/SQL block (anonymous block, procedure, function, packaged procedure, packaged function, database trigger) as an autonomous transaction, you isolate the DML in that block from the caller's transaction context. The block becomes an independent transaction started by another transaction, referred to as the main transaction. To mark a PL/SQL block as an autonomous transaction, you simply include the following statement in your declaration section:
132
133
PRAGMA AUTONOMOUS_TRANSACTION; SQL Server 2005 does not support autonomous transactions. The only way to isolate a Transact-SQL block from a transaction context is to open a new connection. To convert a procedure, function, or trigger with an AUTONOMOUS_TRANSACTION flag, you split it into two objects. The first object is a stored procedure containing the body of the converted object. It looks like it was converted without a PRAGMA AUTONOMOUS_TRANSACTION flag and is implemented as a stored procedure. The second object is a wrapper that opens a new connection where it invokes the first object. It is implemented via an original object type (procedure, function, or trigger). Use the xp_ora2ms_exec2 extended procedure and its extended version xp_ora2ms_exec2_ex, bundled with the SSMA 3.0 Extension Pack, to open new transactions. The procedure's purpose is to invoke any stored procedure in a new connection and help invoke a stored procedure within a function body. The xp_ora2ms_exec2 procedure has the following syntax: xp_ora2ms_exec2 <active_spid> int, <login_time> datetime, <ms_db_name> varchar, <ms_schema_name> varchar, <ms_procedure_name> varchar, <bind_to_transaction_flag> varchar, [optional_parameters_for_procedure] Where: <active_spid> [input parameter] is the session ID of the current user process. <login_time> [input parameter ] is the login time of the current user process. <ms_db_name> [input parameter] is the database name owner of the stored procedure. <ms_schema_name> [input parameter] is the schema name owner of the stored procedure. <ms_procedure_name> [input parameter] is the name of the stored proceduure. optional_parameters_for_procedure [input/output parameter] are the procedure parameters.
In general, you can retrive the active_spid parameter from the @@spid system function. You can query the login_time parameter with the statement: declare @login_time as datetime select @login_time=start_time from sys.dm_exec_requests where session_id=@@spid
We recommend that you use SSMA Extension Pack methods to retrieve the active_spid and login_time values before passing them to the xp_ora2ms_exec2 procedure. Use the following recommended general template to invoke xp_ora2ms_exec2:
133
134
DECLARE @spid int, @login_time datetime SELECT @spid = sysdb.ssma_ora.get_active_spid(), @login_time = sysdb.ssma_ora.get_active_login_time() EXEC master.dbo.xp_ora2ms_exec2_ex @spid, @login_time, <database_name>, <schema_name>, <procedure_name>, [parameter1, parameter2, ... ]
Simulating Autonomous Procedures and Packaged Procedures

As mentioned earlier, SSMA ignores the PRAGMA AUTONOMOUS_TRANSACTION flag when it converts procedures. We recommend naming that procedure differently from the original since it will not be invoked directly. You can implement the procedure wrapper body according to the following pattern: CREATE PROCEDURE [schema.] <procedure_name> <parameters list> AS BEGIN DECLARE @spid int, @login_time datetime SELECT @spid = sysdb.ssma_ora.get_active_spid(), @login_time = sysdb.ssma_ora.get_active_login_time() EXEC master.dbo.xp_ora2ms_exec2 @ spid, @ login _spid, <database_name>, <schema_name>, <procedure_name>$IMPL, [parameter1, parameter2, ... ] END The <procedure_name>$IMPL parameter is the name of the procedure containing the converted source code. Note that the parameters list that is passed to the xp_ora2ms_exec2 procedure should keep the IN/OUT options in the parameters for <procedure_name>$IMPL. Since the first PL-SQL statement in an autonomous routine begins a transaction, the procedure body should be begun with the set implicit_transactions on statement. The procedure body should be converted as the following pattern: CREATE PROCEDURE [schema.] <procedure_name>$IMPL <parameters list> AS BEGIN set implicit_transactions on <procedure_body> END
Simulating Autonomous Functions and Packaged Functions

The method to simulate autonomous functions resembles that for procedures. Make the wrapper method a function, and implement the function body via a stored
134
135
procedure. Add the additional parameter to the procedure's parameter list. Give the parameter a type corresponding to a function return value and an output direction. Implement the function wrapper body according to the following pattern: CREATE FUNCTION [schema.] <function_name> (<parameters list>) RETURNS <return_type> AS BEGIN DECLARE @spid int, @login_time datetime SELECT @spid = sysdb.ssma_ora.get_active_spid(), @login_time = sysdb.ssma_ora.get_active_login_time() DECLARE @return_value_variable <function_return_type> EXEC master.dbo.xp_ora2ms_exec2 @@spid,@login_time, <database_name>, <schema_name>, <function_name>$IMLP, [parameter1, parameter2, ... ,] @return_value_variable OUTPUT RETURN @return_value_variable END The function body will be transformed into the following procedure: CREATE PROCEDURE [schema.] <function_name>$IMPL <parameters list> , @return_value_argument <function_return_type> OUTPUT AS BEGIN set implicit_transactions on <function implementation> SET @return_value_argument = <return_expression> END The <return_expression> is an expression that a function uses in the RETURN operator
Simulation of Autonomous Triggers

For conversion of autonomous triggers, see Autonomous Transactions in Triggers.
Code Examples
Example 1 Oracle CREATE OR REPLACE PROCEDURE update_salary (emp_id IN NUMBER)
135
136
IS PRAGMA AUTONOMOUS_TRANSACTION; BEGIN UPDATE employees SET site_id = site_id * 2 where employee_id=emp_id; COMMIT; EXCEPTION WHEN OTHERS THEN ROLLBACK; END; SQL Server 2005 CREATE PROCEDURE dbo.UPDATE_SALARY @emp_id float(53) AS BEGIN DECLARE @active_spid INT, @login_time DATETIME SET @active_spid = sysdb.ssma_oracle.GET_ACTIVE_SPID() SET @login_time = sysdb.ssma_oracle.GET_ACTIVE_LOGIN_TIME() EXECUTE master.dbo.xp_ora2ms_exec2 @active_spid, @login_time, 'SYSTEM', 'DBO', 'UPDATE_SALARY$IMPL', @emp_id END CREATE PROCEDURE dbo.UPDATE_SALARY$IMPL @emp_id float(53) AS BEGIN SET IMPLICIT_TRANSACTIONS ON BEGIN TRY UPDATE dbo.EMPLOYEES SET SITE_ID = EMPLOYEES.SITE_ID * 2 WHERE EMPLOYEES.EMPLOYEE_ID = @emp_id IF @@TRANCOUNT > 0 COMMIT WORK END TRY BEGIN CATCH IF @@TRANCOUNT > 0 ROLLBACK WORK END CATCH END Example 2 Oracle CREATE OR REPLACE function fn_inc_value(var_name varchar2) return number
136
137
is PRAGMA AUTONOMOUS_TRANSACTION; i number(38); CURSOR cur_values IS SELECT value + 1 FROM t_values WHERE name = var_name; BEGIN OPEN cur_values; FETCH cur_values INTO i; if cur_values%NOTFOUND then i:=0; insert into t_values values(var_name,i); else update t_values set value=i where name = var_name; end if; CLOSE cur_values; COMMIT; return i; END; SQL Server 2005 CREATE FUNCTION dbo.FN_INC_VALUE (@var_name varchar(max)) RETURNS float(53) AS BEGIN DECLARE @active_spid INT, @login_time DATETIME SET @active_spid = sysdb.ssma_oracle.GET_ACTIVE_SPID() SET @login_time = sysdb.ssma_oracle.GET_ACTIVE_LOGIN_TIME() DECLARE @return_value_argument float(53) EXECUTE master.dbo.xp_ora2ms_exec2
137
138
@active_spid, @login_time, 'TEMPDB', 'DBO', 'FN_INC_VALUE$IMPL', @var_name, @return_value_argument OUTPUT
RETURN @return_value_argument END
CREATE PROCEDURE dbo.FN_INC_VALUE$IMPL @var_name varchar(max),@return_value_argument float(53) AS BEGIN SET IMPLICIT_TRANSACTIONS @i numeric(38), @v_cur_values_rowcount int DECLARE cur_values CURSOR LOCAL FOR SELECT T_VALUES.VALUE + 1 FROM dbo.T_VALUES WHERE T_VALUES.NAME = @var_name SET @v_cur_values_rowcount = 0 OPEN cur_values FETCH cur_values INTO @i IF @@FETCH_STATUS = 0 SET @v_cur_values_rowcount = @v_cur_values_rowcount + 1 IF @@FETCH_STATUS = BEGIN SET @i = 0 INSERT dbo.T_VALUES(NAME, VALUE) VALUES (@var_name, @i) END ELSE -1 ON DECLARE OUTPUT
138
139
UPDATE dbo.T_VALUES SET VALUE = @i WHERE T_VALUES.NAME = @var_name CLOSE cur_values DEALLOCATE cur_values IF @@TRANCOUNT > 0 COMMIT WORK SET @return_value_argument = @i END
Migrating Oracle Collections and Records

Unlike Oracle, Microsoft SQL Server 2005 supports neither records nor collections. When you migrate from Oracle to SQL Server 2005, therefore, you must apply substantial transformations to the PL/SQL code that uses records and collections. SSMA Oracle 3.0 does not convert collections. Therefore, this section describes manual migration activity. (The only exception is that SSMA supports record conversion to XML. See Implementing Records and Collections Via XML.)
Implementing Collections
To implement collections, you have four options: Option 1. Rewrite your code to avoid collections and records. Option 2. In some situations you have no choice but to use collections (or something similar, such as arrays). Option 3. The worst collection scenario is when you pass a collection as a parameter into a procedure or a function. Option 4. This option is a modification of Option 3. Instead of using temporary tables (which cannot be accessed from within function), you use permanent tables.
Option 1. Rewrite your code to avoid collections and records. In many cases, collections or records are not justified. Generally, you can perform the same tasks by using set-oriented operators, meanwhile gaining performance benefits and code clearness. In the PL/SQL code (from here and following we use the SCOTT demo scheme): declare type emptable is table of integer; emps emptable; i integer; begin select empno bulk collect into emps from Emp where deptno = 20; for i in emps.first..emps.last loop update scott.emp set sal=sal*1.2 where EmpNo=emps(i); end loop; end;
139
140
The corresponding Transact-SQL code looks like: update emp set sal=sal*1.2 where deptno = 20 Usually, nobody would write such awkward code in Oracle, but you may find something similar in, for example, proprietary systems. It might be a good opportunity to refactor the source code to use SQL where possible. Option 2. In some situations you have no choice but to use collections (or something similar such as arrays). Suppose you want to retrieve a list of employers IDs, and for each ID from the list execute a stored procedure to raise each salary. If the PL/SQL the source code looks like: declare type emptable is table of integer; emps emptable; i integer; begin select empno bulk collect into emps from Emp where deptno = 20; for i in emps.first..emps.last loop scott.raisesalary(Emp => emps(i),Amount => 10); end loop; end; The corresponding Transact-SQL code may look like: declare @empno int declare cur cursor local static forward_only for select empno from emp where deptno = 20 open cur fetch next from cur into @empno while @@fetch_status = 0 begin exec raisesalary @emp=@empno,@amount=10 fetch next from cur into @empno end deallocate cur Sometimes you need not only to run through a list and make an action for each record (as seen earlier), but you also want to randomly access elements in the list. In this situation it is useful to use table variables. The general idea is to replace a collection (integer-indexed array) with a table (indexed by its primary key). For the following PL/SQL code: declare type emptable is table of integer;
140
141
emps emptable; i integer; s1 numeric; s2 numeric; begin select empno bulk collect into emps from Emp; for i in emps.first+1..emps.last-1 loop select sal into s1 from scott.emp where empno = emps(i-1); select sal into s2 from scott.emp where empno = emps(i+1); update emp set sal=(s1+s2)/2 where EmpNo=emps(i); end loop; end; The corresponding Transact-SQL code may look like: declare @tab table(_idx_ int not null primary key, empno int) insert into @tab(_idx_,empno) select row_number() over(order by empno),empno from emp declare @first int,@last int,@i int,@s1 money,@s2 money select top 1 @first=_idx_ from @tab order by _idx_ asc select top 1 @last =_idx_ from @tab order by _idx_ desc set @i = @first+1 while @i < @last-1 begin select @s1 = sal from emp where empno = (select empno from @tab where _idx_=@i-1) select @s2 = sal from emp where empno = (select empno from @tab where _idx_=@i+1) update emp set sal = (@s1+@s2)/2 where empno = (select empno from @tab where _idx_=@i) set @i = @i +1 end In this example, the table variable @tab, indexed with an _idx_ field, represents our collection. Pay attention to the row_number() function in the select statement. If you do not plan to insert explicit values in the collection, you can avoid using row_number: declare @tab table(_idx_ int identity(1,1) not null primary key, empno int) insert into @tab(empno) select empno from emp Now the @tab variable is sequentially indexed starting from 1. If you are using a collection of %ROWTYPE, you can declare a table variable with an appropriate list of fields and use it as shown earlier.
141
142
By using table variables, you can emulate the functionality of almost any local collection, as shown in the following table. Task
Declaration
Collection
type emptable is table of integer; emps emptable;
Emulation with table variable

declare @emp table(_idx_ int not null primary key, empno int) or declare @emps table(_idx_ int identity(1,1) not null primary key, empno int) update @emp set empno = 12 where _idx_=@i if @@rowcount = 0 insert into @emps(_idx_,empno) values(@i,12)
Remarks
First declaration for manual indexing and second for automatic (by identity) indexing.
Set value into collection
emp(i) := 12;
You are trying to update the record with _idx_=@i. If it doesnt exist (@@rowcount=0), simply insert the needed data. Note: If you use an identity field as _idx_, you cannot insert an explicit value into the _idx_ field.
Get value from collection FIRST method
Empno = emp(i);
select @empno = empno from @emps where _idx_ = @i select @i_first = min(_idx_) from @emps or set @i_last=null select top 1 @i_first = _idx_ from @emps order by _idx_ asc Comment on set @i_last=null If the select statement does not return any row, @i_first will not change its value, keeping the previously stored value. So, first initialize this variable as null.
I_first := emp.FIRST;
LAST method
I_last := emp.LAST;
select @i_last = max(_idx_) from @emps or set @i_last=null select top 1 @i_last = _idx_ from @emps order by _idx_ desc
NEXT method
I_next := emp.NEXT(j);
select @i_last = min(_idx_) from @emps where _idx_ > @i
142
143
Task
PRIOR method DELETE method
Collection
I_prior := emp.PRIOR(j); emps.delete(i); emps.delete;

select @i_last = max(_idx_) from @emps where _idx_ < @i DELETE FROM @emps WHERE _idx_ = @i DELETE FROM @emps
Remarks
TRIM method
emps.trim; emps.trim(n);
declare @_idx_ int select top(@n) @_idx_= _idx_ from @emps order by _idx_ desc delete @emps where _idx_ >= @_idx_
emps.trim is
equivalent to
emps.trim(1).
EXISTS method COUNT method Bulk collect into
t.exists(i) i = t.COUNT; select empno bulk collect into emps from emp
exists(select * from @emps where _idx_ = @i) select @t_count = COUNT(*) FROM @emps INSERT INTO @emps (_idx_, empno) SELECT row_number() over(order by empno) as _idx_, empno from emp or INSERT INTO @emps (empno) SELECT empno from emp The
row_number()
function depends on @emps table declaration. For declaration with identity _idx_ column do not use row_number().
EXTEND method
t.extend; t.extend(n); t.extend(n, i);
SELECT @t_next_value = ISNULL(MAX(_idx_),0)+1 FROM @emps
INSERT INTO @emps (_idx_, empno) VALUE(@t_next_value, NULL) ---------------------------------SELECT @t_cur_value = ISNULL(MAX(_idx_),0) FROM @emps
WHILE @n <> 0 BEGIN @t_cur_value = @t_cur_value + 1
143
144
Task
Collection

INSERT INTO @emps (_idx_, empno) VALUE(@t_cur_value, NULL) SET @n = @n-1 END ---------------------------------SELECT @t_cur_value = ISNULL(MAX(_idx_),0) FROM @emps SELECT @v = empno FROM @emps where _idx_ = @i
Remarks
WHILE @n <> 0 BEGIN @t_cur_value = @t_cur_value + 1 INSERT INTO @emps (_idx_, empno) VALUE(@t_cur_value, @v) SET @n = @n-1 END FORALL INSERT INTO FORALL i IN 1..20 INSERT INTO emp(empno) VALUES (t(i)) INSERT INTO emp (empno) SELECT empno FROM @emps WHERE _idx_ between 1 and 20
FORALL UPDATE
FORALL i IN 6..10 UPDATE emp SET sal = sal * 1.10 WHERE empno = t(i);
UPDATE emp SET sal = sal * 1.10 FROM (SELECT * FROM @emps WHERE _idx_ between 6 and 10) as t_a INNER JOIN emp ON (emp.empno = t_a.empno)
FORALL DELETE
FORALL i IN 6..10 DELETE FROM emp WHERE empno = t(i);
DELETE FROM emp WHERE empno IN (SELECT empno FROM @t WHERE _idx_ between 6 and 10)
144
145
Option 3. The worst collection scenario is when you pass a collection as a parameter into a procedure or a function. You have two possible solutions. The first solution is similar to the solution that uses table variables. The main difference is that instead of a table variable you use a local temporary table (#tab, for example). The table will be visible in the procedure that created this table and in all subsequent procedures. The PL/SQL code Stored procedure: create procedure emp_raise(emps in emptable) i int; is begin for i in emps.first..emps.last loop raisesalary(Emp => emps(i),Amount => 10); end loop; end; The procedure call: declare type emptable is table of integer; emps emptable; begin select empno bulk collect into emps from scott.emp; emp_raise(emps); end; The Transact-SQL code The stored procedure: create procedure emp_raise as begin declare @empno int declare cur cursor local static forward_only for select empno from #emp open cur fetch next from cur into @empno while @@fetch_status = 0 begin exec raisesalary @emp=@empno,@amount=10 fetch next from cur into @empno end deallocate cur end
145
146
The procedure call: create table #emp(_idx_ int not null identity,empno int) insert into #emp(empno) select empno from emp exec emp_raise drop table #emp Instead of using a collection, you pass needed data to a stored procedure via a temporary table. Of course you miss useful things such as parameter substitution. (The name of the temporary table you create outside of the stored procedure must be the same name as the temporary table in the stored procedure.) That is, you do not cover situations in which different actual collections are passed to the procedure. But, unfortunately, you cannot access a temporary table from within SQL Server functions. Option 4. This option is a slight modification of Option 3. Instead of using temporary tables (which cannot be accessed from within function), you use permanent tables. Unlike temporary tables, you can access permanent tables and views from within functions. But be aware that you cannot use DML statements in functions, so this collection emulation is read-only. If you want to modify a collection from within a user-defined function, you must use another kind of emulation; you can not modify permanent tables from within UDF. (See Sample Functions for XML Record Emulation.) The only difference between Option 4 and Option 3 is that the table should be cleaned before use. The PL/SQL code declare type emptable is table of integer; emps emptable; i integer; s1 numeric; s2 numeric; begin select empno bulk collect into emps from Emp; for i in emps.first+1..emps.last-1 loop select sal into s1 from scott.emp where empno = emps(i-1); select sal into s2 from scott.emp where empno = emps(i+1); update emp set sal=(s1+s2)/2 where EmpNo=emps(i); end loop; end; The Transact-SQL code Create a table for collection emulation: create table emps_t(SPID smallint not null default @@SPID,_idx_ int not null,empno int null) go
146
147
create clustered index cl on emps_t(SPID,_idx_) go create view emps as select _idx_,empno from emps_t where spid = @@spid go The converted code: delete emps insert into emps(_idx_,empno) select row_number() over(order by empno),empno from emp declare @first int,@last int,@i int,@s1 money,@s2 money select top 1 @first=_idx_ from emps order by _idx_ asc select top 1 @last =_idx_ from emps order by _idx_ desc set @i = @first+1 while @i < @last-1 begin select @s1 = sal from emp where empno = (select empno from emps where _idx_=@i-1) select @s2 = sal from emp where empno = (select empno from emps where _idx_=@i+1) update emp set sal = (@s1+@s2)/2 where empno = (select empno from emps where _idx_=@i) set @i = @i +1 end Be aware that, unlike table variables, permanent tables are transaction-dependent, which may lead to unwanted lock contention. Pay attention when using this option; you cannot avoid using a row_number() function.
Implementing Records
Usually you use records to simplify your PL/SQL code. Instead of writing: declare empno number(4); ename varchar(10); job varchar(9); mgr number(4); hiredate date; sal number(7,2); comm number(7,2); deptno number(2); begin select * into empno,ename,job,mgr,hiredate,sal,comm,deptno from
147
148
scott.emp where empno = 7369; dbms_output.put_line(ename); end; You could write simple and clear code: declare emps scott.emp%rowtype; begin select * into emps from scott.emp where empno = 7369; dbms_output.put_line(emps.ename); end; Its perfect! But unfortunately SQL Server doesnt support records. Following are some options for working around this. Option 1. Declare a separate variable for each column as in the following code: declare @empno int,@ename varchar(10),@job varchar(9),@mgr int,@hiredate datetime,@sal numeric(7,2),@comm numeric(7,2),@deptno int select @empno=empno, @ename=ename, @job=job, @mgr=mgr, @hiredate=hiredate, @sal=sal, @comm=comm, @deptno=deptno from emp where empno = 7369 print @ename This is the same situation with passing records into procedures or functions; you should pass each variable into a procedure. The PL/SQL code declare emps scott.emp%rowtype; begin select * into emps from scott.emp where empno = 7369; raise_emp_salary(emps); end; The Transact-SQL code declare @empno int,@ename varchar(10),@job varchar(9),@mgr int,@hiredate datetime,@sal numeric(7,2),@comm numeric(7,2),@deptno int select @empno=empno, @ename=ename, @job=job, @mgr=mgr, @hiredate=hiredate, @sal=sal, @comm=comm, @deptno=deptno from emp where empno = 7369
148
149
exec raise_emp_salary @empno,@ename,@job,@mgr,@hiredate,@sal,@comm,@deptno Option 2 Collection of Records. Sometimes you use collections of records to hold lines from tables. Dealing with a collection is described in previous sections in this paper. Now you simply modify the table definition as in the following code: The PL/SQL code declare type emptable is table of scott.emp%rowtype; emps emptable; begin select * bulk collect into emps from emp; end; The Transact-SQL code declare @emp table (_idx_ int,empno int,ename varchar(10),job varchar(9),mgr int,hiredate datetime,sal numeric(7,2),comm numeric(7,2),deptno int) insert into @emp select row_number() over(order by empno),* from emp Note Using select * is not good practice.
Here is another common case usage scenariousing record with cursors. DECLARE CURSOR emp_cursor IS SELECT empno, ename FROM scott.emp; BEGIN FOR emp_rec IN emp_cursor LOOP raise_emp_salary(emp_rec); END LOOP; END; Or, alternatively DECLARE CURSOR emp_cursor IS SELECT empno, ename FROM scott.emp; emps emp_cursor%rowtype; BEGIN open emp_cursor; loop fetch emp_cursor into emps;
149
150
exit when emp_cursor%notfound; raise_emp_salary(emp_rec); end loop; close emp_cursor; END; Both samples could be converted by using the separate variable technique described earlier. declare emp_cursor cursor for select empno,ename from scott.emp declare @empno int,@ename varchar(128) open emp_cursor fetch next from emp_cursor into @empno,@ename while @@fetch_status = 0 begin exec raise_emp_salary @empno,@ename fetch next from emp_cursor into @empno,@ename end close emp_cursor deallocate emp_cursor For more information about cursor conversion, see Migrating Oracle Cursors.
Implementing Records and Collections Via XML

The most universal but most complex way to emulate collections or records is emulation via XML. With XML implementation, you can store records and collections in a database (for example, in an XML field in a table), and pass records and collections into stored procedures and user-defined functions. However, take into account that manipulation with XML (especially modifying) is relatively slow.
Implementing Records
For complex cases you can emulate records via XML. For example, you could emulate scott.emp%rowtype with the following XML structure: <row> <f_name>DEPTNO</f_name> <_val>20</_val> </row> <row> <f_name>SAL</f_name> <_val>800</_val> </row> <row> <f_name>HIREDATE</f_name>
150
151
<_val>Dec 17 1980 12:00:00:000AM</_val> </row> <row> <f_name>MGR</f_name> <_val>7902</_val> </row> <row> <f_name>JOB</f_name> <_val>CLERK</_val> </row> <row> <f_name>ENAME</f_name> <_val>SMITH</_val> </row> <row> <f_name>EMPNO</f_name> <_val>7369</_val> </row> To work with such a structure you need additional supplemental procedures and functions to simplify access to the data. (Examples of the modules provided by SSMA are at the end of this section.) Now you can rewrite your sample: DECLARE CURSOR emp_cursor IS SELECT empno, ename FROM scott.emp; emps emp_cursor%rowtype; BEGIN open emp_cursor; loop fetch emp_cursor into emps; exit when emp_cursor%notfound; raise_emp_salary(emp_rec); end loop; close emp_cursor; END; As the following Transact-SQL code: DECLARE @emps xml,@emps$empno int,@emps$ename varchar(max) DECLARE emp_cursor CURSOR LOCAL FOR SELECT EMP.EMPNO, EMP.ENAME FROM dbo.EMP
151
152
OPEN emp_cursor FETCH next from emp_cursor INTO @emps$empno, @emps$ename WHILE @@fetch_status = 0 begin SET @emps = sysdb.ssma_oracle.SetRecord_varchar(@emps, N'ENAME', @emps$ename) SET @emps = sysdb.ssma_oracle.SetRecord_float(@emps, N'EMPNO', @emps$empno) EXECUTE raise_emp_salary @emps FETCH next from emp_cursor INTO @emps$empno, @emps$ename END CLOSE emp_cursor DEALLOCATE emp_cursor The code here is slightly different from SSMA-generated code. It shows only basic techniques for working with XML records. (You fetch data from a cursor into separate variables, and then construct from it and an XML record.) To extract data back from XML you could use an appropriate function such as: set @ename = sysdb.ssma_oracle.GetRecord_varchar(@emps, N'ENAME')
Implementing Collections
The PL/SQL code DECLARE TYPE Colors IS TABLE OF VARCHAR2(16); rainbow Colors; BEGIN rainbow := Colors('Red', 'Yellow'); END; The Transact-SQL code, collection DECLARE @rainbow XML SET @rainbow = '<coll_row _idx_="1"> <row> <_val>Red</_val> </row> </coll_row> <coll_row _idx_="2"> <row> <_val>Yellow</_val> </row> </coll_row>' The Transact-SQL code, collection of records DECLARE @x XML SET @x = '<coll_row _idx_="1"> <row>
152
153
<f_name>record_field_1</f_name> <_val>value_1</_val> </row> </coll_row> <coll_row _idx_="2"> <row> <f_name>record_field_2</f_name> <_val>value_2</_val> </row> </coll_row> After these declarations you can modify a collection, record, or collection of records by using XQuery. You may find it useful to write wrapper functions to work with XML, such as GET and SET functions.
Sample Functions for XML Record Emulation

The Transact-SQL GET wrapper function for the varchar data type CREATE FUNCTION GetRecord_Varchar (@x XML, @column_name varchar(128)) RETURNS varchar(MAX) BEGIN DECLARE @v_x_value varchar(MAX) SELECT TOP 1 @v_x_value = T.c.value('(_val)[1]', 'varchar(MAX)') FROM @x.nodes('/row') T(c) WHERE T.c.value('(f_name)[1]', 'varchar(128)') = @column_name return(@v_x_value) END The Transact-SQL SET wrapper function for the varchar data type CREATE FUNCTION SetRecord_Varchar ( @x XML, @column_name varchar(128), @v varchar(max)) RETURNS XML AS BEGIN IF @x IS NULL SET @x = '' IF @x.exist('(/row/f_name[.=sql:variable("@column_name")])[1]') = 1 BEGIN if @v is not null BEGIN SET @x.modify( 'delete (/row[f_name=sql:variable("@column_name")])[1]
153
154
') SET @x.modify( 'insert (<row> <f_name>{sql:variable("@column_name")}</f_name> <_val>{sql:variable("@v")}</_val> </row>) into (/)[1] ' ) END else SET @x.modify( 'delete (/row[f_name=sql:variable("@column_name")] /_val[1])[1] ') END ELSE if @v is not null SET @x.modify( 'insert (<row> <f_name>{sql:variable("@column_name")}</f_name> <_val>{sql:variable("@v")}</_val > </row>) into (/)[1] ' ) RETURN(@x) END; A sample call DECLARE @x xml SET @x = dbo.SetRecord_varchar(@x, N'RECORD_FIELD_1', 'value_1') SET @x = dbo.SetRecord_varchar(@x, N'RECORD_FIELD_2', 'value_2') PRINT dbo.GetRecord_varchar(@x, N'RECORD_FIELD_2') For more information, see XQuery Against the xml Data Type in SQL Server 2005 Books Online.
154
155
Conclusion
This migration guide covers the differences between Oracle and SQL Server 2005 database platforms, and the steps necessary to convert an Oracle database to SQL Server. It explains the algorithms that SSMA Oracle uses to perform this conversion so that you can better understand the processes that are executed when you run SSMA the Convert Schema and Migrate Data commands. For those cases when SSMA does not handle a particular migration issue, approaches to manual conversion are included. For more information: SQL Server Migration Assistant for Oracle (SSMA for Oracle) on Microsoft.com For help on SSMA Oracle or if you have question about Oracle to SQL Server 2005 migration, write to [email protected]. Did this paper help you? Please give us your feedback. Tell us on a scale of 1 (poor) to 5 (excellent), how would you rate this paper and why have you given it this rating? For example: Are you rating it high due to having good examples, excellent screenshots, clear writing, or another reason? Are you rating it low due to poor examples, fuzzy screenshots, unclear writing?
This feedback will help us improve the quality of white papers we release. Send feedback.
155

SSMAOracle

Uploaded by

Copyright:

Available Formats

SSMAOracle

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SSMAOracle

Uploaded by

Copyright:

Available Formats

Guide to Migrating from Oracle to SQL Server 2005

SQL Server Technical Article

Guide to Migrating from Oracle to SQL Server 2005

2007 Microsoft Corporation. All rights reserved.

Guide to Migrating from Oracle to SQL Server 2005

Guide to Migrating from Oracle to SQL Server 2005

Guide to Migrating from Oracle to SQL Server 2005

Guide to Migrating from Oracle to SQL Server 2005

Guide to Migrating from Oracle to SQL Server 2005

Overview of Oracle-to-SQL Server 2005 Migration

Main Migration Steps

Microsoft Corporation 2007

Guide to Migrating from Oracle to SQL Server 2005

Conversion of Database Objects

Differences in SQL Languages

Guide to Migrating from Oracle to SQL Server 2005

Guide to Migrating from Oracle to SQL Server 2005

Data Migration Architecture of SSMA for Oracle

Guide to Migrating from Oracle to SQL Server 2005

Stored Procedures Interface

Guide to Migrating from Oracle to SQL Server 2005

Validation of the Results

Migrating Oracle Data Types

Guide to Migrating from Oracle to SQL Server 2005

Guide to Migrating from Oracle to SQL Server 2005

Numeric Data Types

Character Data Types

Guide to Migrating from Oracle to SQL Server 2005

Date and Time

Large Object Types

Guide to Migrating from Oracle to SQL Server 2005

Emulating Oracle System Objects

Converting Oracle System Views

Guide to Migrating from Oracle to SQL Server 2005

In this section, we describe ways to manually convert the following views:

Location of Generated System View Emulations for SSMA 3.0

Guide to Migrating from Oracle to SQL Server 2005

CREATE SYNONYM ssma_oracle.DBA_TRIGGERS FOR TEST_DATABASE.ssma_oracle.ALL_TRIGGERS

ALL_INDEXES System View

ALL_OBJECTS System View

ALL_SYNONYMS System View

ALL_TAB_COLUMNS System View

ALL_TABLES System View

ALL_CONSTRAINTS System View

ALL_SEQUENCES System View

Guide to Migrating from Oracle to SQL Server 2005

ALL_VEWS System View

ALL_USERS System View

ALL_SOURCE System View

GLOBAL_NAME System View

ALL_JOBS System View

V$SESSION System View

DBA_EXTENTS System View

Guide to Migrating from Oracle to SQL Server 2005

V$LOCKED_OBJECT System View

Guide to Migrating from Oracle to SQL Server 2005

DBA_FREE_SPACE system view

DBA_SEGMENTS system view

Guide to Migrating from Oracle to SQL Server 2005

Converting Oracle System Functions