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 333What can be confusing with SQL Server is the presence of several system and usercreated“databases” inside a SQL Server database. Hence the term database systemhas been coined here to mean an occurrence of <strong>Oracle</strong> or SQL Server. MultipleDatabase Systems (Instances)In <strong>Oracle</strong>, multiple database systems can be created on a single server and the creationis independent of the software installation (using the CREATE DATABASE SQLcommand). The same is not true with SQL Server. The initial database system (default ornamed) is created as part of the software installation. The software distribution is alsoneeded to create additional database systems. For in<strong>for</strong>mation on working with namedand multiple instances of SQL Server 2000, refer tohttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_runsetup_2xmb.asp.The following components are shared between all of the instances running on the samecomputer:● There is only one SQL Server 2000 program group (Microsoft SQL Server) on thecomputer, and only one copy of the utility represented by each icon in the programgroup. There is only one copy of SQL Server Books Online.● The versions of the utilities in the program group are from the first version of SQLServer installed on the computer.● There is only one copy of the MSSearchService that manages full-text searchesagainst all of the instances of SQL Server on the computer.● There is only one copy each of the English Query and Microsoft SQL Server 2000Analysis Services servers.● The registry keys associated with the client software are not duplicated betweeninstances.● There is only one copy of the SQL Server development libraries (include and .libfiles) and sample applications.Extending out to the client tier, the <strong>Oracle</strong> clients and SQL Server clients connect todatabases in similar, albeit proprietary, protocols: Transparent Network Substrate (TNS)<strong>for</strong> <strong>Oracle</strong> and Tabular Data Stream (TDS) <strong>for</strong> SQL Server. Figure A.2 compares theuser-instance-database interaction paths.