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

138 Developing: Databases — <strong>Migrating</strong> SchemasBEFORE INSERT OR UPDATE OR DELETE ON employeesEMPLOYEES CREATE TRIGGER update_job_historyAFTER UPDATE OF job_id, department_id ON employeesFOR EACH ROWThe equivalent syntax <strong>for</strong> SQL Server can be generated with the aid of Table 6.24.The commands <strong>for</strong> creating the secure_ employees and update_job_historytriggers will convert as:7.CREATE TRIGGER secure_employeesON employeesINSTEAD OF INSERT, UPDATE, DELETEAS…GOCREATE TRIGGER update_job_historyON employeesAFTER UPDATEAS…GOIF (UPDATE(job_id) or UPDATE(department_id))Create indexes.All indexes related to constraints should have been created in Substep 5.b. Thisstep covers the indexes that are not related to any constraints.The following query can be used to retrieve in<strong>for</strong>mation on indexes in <strong>Oracle</strong> thatare not related to any constraints. This query will work only in <strong>Oracle</strong> 9i becausethe data dictionary be<strong>for</strong>e this release of <strong>Oracle</strong> does not have the columns used inthis query.SELECT i.table_name, i.index_name, c.column_name, i.uniqueness,i.tablespace_name, i.pct_freeFROM dba_indexes i, dba_ind_columns cWHERE i.table_name = c.table_nameAND i.index_name = c.index_nameAND i.owner = c.index_ownerAND i.owner = 'HR'AND (i.owner, i.index_name) NOT IN(SELECT index_owner, index_nameFROM dba_constraintsWHERE owner = 'HR'AND index_name IS NOT NULL)ORDER BY i.table_name, i.index_name, c.column_positionThe output obtained has been <strong>for</strong>matted as follows:TABLE_NAME INDEX_NAMECOLUMN_NAMEUNIQUENESSTABLESPACE_NAMEPCT_FREEDEPARTMENTSDEPT_LOCATION_IX LOCATION_ID NONUNIQUEINDX 10EMPLOYEES EMP_DEPARTMENT_IXINDX 10EMPLOYEES EMP-JOB-IXINDX 10DEPARTMENT_IDJOB_IDNONUNIQUENONUNIQUE