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 341Security ArchitectureThe database has security mechanisms such as logins, privileges, and roles to providecontrol over privileges to connect to the database, access schema objects, andmanipulate their structure and data. Both <strong>Oracle</strong> and SQL Server utilize a layeredapp roach to security, from logins to roles to system (statement) and object privileges.LoginsBoth <strong>Oracle</strong> and SQL Server provide logins <strong>for</strong> authorized users to connect to thedatabase. In <strong>Oracle</strong>, the login is called user or username, and in SQL Server, it is calledlogin identifier or simply login. Any operation the user can per<strong>for</strong>m is controlled by theprivileges granted to the login.AuthenticationBoth <strong>Oracle</strong> and SQL Server allow authentication by the operating system or by thedatabase (server). In SQL Server, the operating system mode is called WindowsAuthentication Mode and the database mode is called SQL Server Authentication Mode.SQL Server can operate in either Windows authentication mode or Windows and SQLServer authentication mode.PasswordsThe features and functionality related to passwords, such as complexity, aging, or lockout, that exist with <strong>Oracle</strong> logins, can only be found in Windows logins and not SQLServer authenticated logins.Privileges<strong>Oracle</strong> and SQL Server have a similar model to secure schema objects and applicationdata and system objects and metadata from unauthorized users. This is achieved bycreating two sets of privileges: system (statement) privileges (permissions) and objectprivileges (permissions). Privileges can be assigned to users and roles using the GRANTstatement and removed using the REVOKE statement. Roles are used to grant privilegesto users, but indirectly, are discussed next.Roles<strong>Oracle</strong> provides predefined roles, the most familiar being CONNECT, RESOURCE, DBA,and so on. Similarly, SQL Server has several predefined roles with specific permissions.There are two types of predefined roles: fixed server roles and fixed database roles. Both<strong>Oracle</strong> and SQL Server offer user-defined roles.For more in<strong>for</strong>mation on the privileges available in SQL Server and their management,refer to http://msdn.microsoft.com/library/default.asp?url=/library/enus/adminsql/ad_security_94dv.asp.For in<strong>for</strong>mation on creating user-defined roles in SQL Server, refer tohttp://msdn.microsoft.com/library/default.asp?url=/library/enus/adminsql/ad_security_6x5x.asp.Microsoft SQL Server 2000 SP3 Security Features and Best Practices is available at:http://www.microsoft.com/sql/techinfo/administration/2000/security/securityWP.asp. Itprovides a detailed account of SQL Server security model and best practices.