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 141Note The DEPT view was added to the HR schema to demonstrate this point.The EMP_DETAILS_VIEW can be created under the HR schema using thefollowing command:CREATE VIEW hr.EMP_DETAILS_VIEW ASSELECTe.employee_id,e.job_id,e.manager_id,e.department_id,d.location_id,l.country_id,e. first_name,e.last_name,e.salary,e.commission_pct,d.department_name,j.job_title,l.city,l.state_province,c.country_name,r.region_nameFROM hr.employees e INNER JOIN hr.departments dON e.department_id = d.department_idINNER JOIN hr.locations lON d.location_id = l.location_idINNER JOIN hr.countries cON l.country_id = c.country_idINNER JOIN hr.regions rON c.region_id = r.region_idINNER JOIN hr.jobs jON j.job_id = e.job_id;The WITH READ ONLY clause will have to be en<strong>for</strong>ced by ensuring only SELECTprivilege is given to users.9. Create functions, stored procedures, and packages.The following command can be used to get a listing of all functions defined by theschema owner, HR:SELECT object_name, object_typeFROM dba_objectsWHERE owner = 'HR'AND object_type IN ('FUNCTION', 'PROCEDURE', 'PACKAGE', 'PACKAGE BODY')The output retuned is:OBJECT_NAME OBJECT_TYPEADD_JOB_HISTORY PROCEDURESECURE_DML PROCEDUREThe source code of each of these objects can be extracted from the data dictionaryusing the command: