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 149database to which they have been migrated. The following statement can beused to see the schemas on which the user OE has been granted privileges.SELECT ownerFROM dba_tab_privsWHERE grantee = 'OE'UNIONSELECT ownerFROM dba_col_privsWHERE grantee = 'OE'The output of the statement is as follows:OWNERHRSYSIn Chapter 6, the HR schema was migrated to the HRDATA database inSQL Server. SYS is the data dictionary owner, which translates to masterdatabase in SQL Server. However, because the data dictionary is dividedbetween the master database and the application (user-created) databases,<strong>for</strong> an application user, an account in the master database may not benecessary and should be created after proper scrutiny of the securityrequirements.The following commands can be used to create a user <strong>for</strong> the OE login in theHRDATA database:Use HRDATAEXEC sp_grantdbaccess@loginame='OE',@name_in_db='OE'2.Create roles through which the privileges will be granted to users.Only those roles that are granted to users and schemas that are being migratedwill be created in SQL Server. Also, the role has to be created in each of thedatabases with the application schema as the owner.The following statement can be used to retrieve the roles that have been grantedto the user OE:SELECT granted_role, admin_optionFROM dba_role_privsWHERE grantee = 'OE'The following is the output <strong>for</strong> the OE user:3.GRANTED_ROLECONNECTRESOURCEADMIN_OPTIONNONOThe CONNECT and RESOURCE roles are both system roles. No application rolesare in use <strong>for</strong> this schema. Hence all system and object privileges will be granteddirectly to the user. If you want to introduce roles in SQL Server, it should beper<strong>for</strong>med at this point.Grant privileges and/or roles to the user.The roles that were identified in Step 2 are granted here.The CONNECT role gives the user the capability to connect to the <strong>Oracle</strong>database. In SQL Server, the same privileges are inherently granted when thelogin and user accounts are created. The RESOURCE role gives the capability tocreate objects in the database. Thereis no role in SQL Server that provides the