Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

<strong>Solution</strong> <strong>Guide</strong> <strong>for</strong> <strong>Migrating</strong> <strong>Oracle</strong> on UNIX to SQL Server on Windows 133@name_in_db='HR'3. Gra nt privileges to create objects in the database.Priv ileges can be granted to the schema owner to create objects in a databaseusing either the CREATE permissions or the db_owner fixed database role.a.b.Grant complete authority on the database.The following command can be used to grant the db_owner role:EXEC sp_addrolemember@rolename='db_owner',@membername='HR'Grant privileges to create objects only.The following commands can be executed to only grant permission to createobjects:GRANT CREATE FUNCTION TO HRGRANT CREATE PROCEDURE TO HRGRANT CREATE TABLE TO HRGRANT CREATE VIEW TO HR4. Create sequences.While sequences cannot be migrated to SQL Server, in<strong>for</strong>mation about theseq uences in the <strong>Oracle</strong> database should be extracted first. Because sequencesare migrated to IDENTITY columns in tables, the in<strong>for</strong>mation about sequences isrequired to appropriately define tables (in the next step).The following command extracts the required in<strong>for</strong>mation on sequences.SELECT sequence_name, min_value, max_value, increment_byFROM dba_sequencesWHERE sequence_owner = 'HR'The following output is obtained:SEQUENCE_NAME MIN_VALUE MAX_VALUE INCREMENT_BYDEPARTMENTS_SEQ 1 9990 10EMPLOYEES_SEQ 1 999999999999999999999999999 1LOCATIONS_SEQ 1 9900 100The three sequences in the HR schema are assumed to be used to populate thecolumns DEPARTMENTS.DEPARTMENT_ID, EMPLOYEES.EMPLOYEE_ID andLOCATIONS.LOCATION_ID, respectively.5. Create tables.There are two options <strong>for</strong> how to migrate tables. Option one is to create tables in aspecific order based on the <strong>for</strong>eign key constraints (parent tables first). Option twois to create tables in any order, leaving out the <strong>for</strong>eign key constraints and thenadding them after all the tables have been created.a. Obtain a list of tables.If option one is followed, the dependenci es between tables and the right orderin which to create the tables is required. There are several scripts available(mostly PL/SQL-based) to produce such a list. Tables without anydependencies <strong>for</strong>m the first level, and other levels are <strong>for</strong>med based on thenesting of the dependencies.Note None of the available scripts will work when there are interdependenciesbetween tables that <strong>for</strong>m a closed loop. The following script shows suchcircular dependencies thatmake these scripts not viable.