Sahar Mosleh California State University San MarcosPage 1 Installing SQL server 2000

Sahar Mosleh California State University San Marcos Page 1

Installing SQL server 2000


Installing SQL Server 2000

• This chapter prepares you to install SQL Server 2000. This includes determining the computer hardware on which you will install SQL Server; determining which SQL Server 2000 setup configuration options to select. It also provides you with assistance in troubleshooting SQL Server 2000 installation problems.


Lesson 1: Planning to Install SQL Server 2000

• Once you have decided to install SQL Server 2000, you need to select the appropriate computer hardware for your SQL Server 2000 installation. It is important to understand the minimum hardware requirements for each of the SQL Server 2000 editions on each supported Windows operating system edition. You must recognize, however, that these minimum hardware requirements will be insufficient in many production environments to meet either actual current or anticipated future SQL Server requirements. This knowledge will assist you in selecting appropriate computer hardware to optimize SQL Server 2000 performance to meet current needs, as well as to help eliminate costly computer upgrade decisions later.


What Is the Minimum Hardware Required?

• In most SQL Server 2000 production environments, actual hardware requirements will exceed the minimum hardware requirements. However, it is still important to understand these minimum hardware requirements as a baseline. In addition, in some SQL Server 2000 desktop environments, meeting the minimum hardware requirements will be sufficient to meet the needs of these environments.


• The minimum amount of memory required varies depending upon the SQL Server 2000 edition and the Windows operating system edition used. Table 2.2 lists the recommended minimum memory requirements based on the SQL Server edition and the

Windows operating system edition used.


• Table 2.3 lists the amount of hard drive space required for the installation of various SQL Server 2000 components. These numbers assume that SQL Server must install all software required.


Exceeding Minimum Computer Hardware Requirements

• Table 2.4 describes the four primary areas in which you will probably exceed these minimum hardware requirements.


Deciding SQL Server 2000 Setup Configuration Options

• During the installation of SQL Server 2000, you must make a number of decisions in determining the configuration of your SQL Server 2000 installation such as:

• Determine the appropriate user account for the SQL Server and SQL Server Agent services

• Choose an authentication mode for SQL Server 2000

• Determine when to modify default collation settings

• Select the network libraries to use with SQL Server 2000

• Decide on a client licensing mode


Determining the Appropriate User Account for the SQL Server and SQL Server Agent Services

• Using a dedicated user account means creating a domain user account that is used solely for the SQL Server and SQL Server Agent services.

• Selecting a dedicated domain user account allows these SQL Server 2000 services to communicate with other SQL Server installations, access Microsoft Exchange Server, and access network resources (such as file shares) on other computers in your domain environment.

• In addition, you should generally use the same domain user account for all SQL Server installations that will need to communicate with each other. This will simplify the administration of all SQL Server 2000 computers in your domain.


• This domain user account should be configured with the Password Never Expires option.

• The domain user account you create needs certain special access rights on the local computer. These special access rights include the right to log on as a service, the right to access and change the SQL Server folder, the right to access and change database files, and read and write access to certain keys in the Windows registry.

• The SQL Server 2000 Setup program grants these rights automatically to the domain user account you specify


Creating a Dedicated Windows 2000 User Account

• To configure a dedicated domain user account :

1. Ensure that you are logged on to the SelfPacedSQL.MSFT domain controller as Administrator.

2. Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users And Computers. The Active Directory Users And Computers window appears.

3. In the console tree, expand SelfPacedSQL.MSFT. 4. Right-click Users, point to New, and then click User. The

New Object - User dialog box appears.

5. In the First Name text box, type SQLService.


Creating a Dedicated Windows 2000 User Account

6. In the User Logon Name text box, type SQLService , and then click Next.

7. In the Password and Confirm Password text boxes, type sql.

8. Select the Password Never Expires check box, and then click Next.

9. Click the Finish button.

10. In the console tree, click Users. The details pane displays a list of all users in the Users container.

11. Verify that the SQLService domain user account has been created.

12. Close Active Directory Users And Computers.


Choosing an Authentication Mode

• SQL Server 2000 supports two authentication modes, Windows Authentication Mode and Mixed Mode.

• The default authentication mode for SQL Server 2000 is Windows Authentication Mode. When this mode is used, the only users who can connect to SQL Server 2000 are users who have been previously authenticated by the Windows operating system. This is called Windows Authentication. This is used for most SQL Server 2000 environment.

• The alternative authentication mode is Mixed Mode. This means that SQL Server 2000 will use one of two methods of authentication. The first method is to rely on the Windows operating system to authenticate users. The second method is for SQL Server 2000 to authenticate users directly based on the submission of a user name and password to SQL Server 2000 by the client application attempting to gain access. This is called SQL Server Authentication


Determining Collation Settings

• The default collation for SQL Server 2000 is defined during setup. A collation is used to determine how non-Unicode character data is stored and also governs how SQL Server 2000 sorts and compares Unicode and non-Unicode data. A SQL Server 2000 collation consists of a Windows collation and a SQL collation.

• Note Unicode allows data from most languages to be recorded, but takes twice as much space as non-Unicode data. Non-Unicode data only supports 256 characters, and is specific to a particular language.

• Although this might initially seem complicated, determining the Windows collation to use for SQL Server 2000 is generally quite simple.


• We need to understand that SQL Server 2000 uses a SQL collation to match settings used in previous versions of SQL Server. This is necessary because earlier versions of SQL Server specified code page number, character sort order, and Unicode collation separately. A SQL collation specifies three collation attributes:

• The non-Unicode code page—Tells SQL Server 2000 how to store non-Unicode character data.

• The non-Unicode sort order—Tells SQL Server 2000 how to sort non-Unicode character data types, such as sensitivity to capitalization.

• The Unicode sort order—Tells SQL Server 2000 how to sort Unicode data types.


• The final step is to understand that SQL Server collations are settable at multiple levels. You set a default collation (which consists of a Windows collation and a SQL collation) for an instance of SQL Server 2000.

• This default collation is the collation setting for all system databases.

• The model database, all user databases, and all other SQL Server 2000 objects inherit this default collation setting, unless a different collation is specified for the database or object.

• In international environments, having different collations for different databases can solve numerous issues involving the use of multiple languages and character sets.


How To determine your Windows collation

1.Ensure that you are logged on to the SelfPacedSQL.MSFT domain controller as Administrator.

2.Click Start, point to Settings, and then click Control Panel. The Control Panel window appears.

3.Double-click the Regional Options icon. The Regional Options dialog box appears with the General tab selected.

4.In the Your Locale (Location) drop-down list, determine your Windows locale. English (United States) is the locale used by the author.

5.Click OK to close the Regional Options dialog box. Do not change your Windows locale.

6.Close the Control Panel window.


Selecting Network Libraries

• SQL Server 2000 uses network libraries to send network packets between clients and a server running SQL Server 2000.

• There are client-side network libraries and server-side network libraries. These client and server network libraries support specific underlying network protocols.

• For example, the TCP/IP sockets network library allows SQL Server 2000 to communicate using Windows sockets as the

• Interprocess communication (IPC) mechanism across the TCP/IP network protocol. The installation of these network protocols is part of your Windows operating system configuration and should be completed prior to installing SQL Server 2000.


• A server running SQL Server 2000 monitors all configured network libraries simultaneously for incoming communication from clients seeking to gain access.

• All additional network libraries are installed during setup, but are not configured for use, unless specified during a Custom setup.


• SQL Server 2000 clients initiate communication with a server running SQL Server 2000 using a specific network library.

• You can configure multiple network libraries on SQL Server 2000 clients, and you can define the order in which the Windows operating system will attempt to use each network library when connecting with SQL Server 2000.

• By default, all SQL Server 2000 clients running Windows 2000, Windows NT 4.0, Windows ME, or Windows 98 use the TCP/IP sockets as the primary network library and named pipes as the secondary network library.

• If you need to manually configure a client-side network library to communicate with a specific SQL Server installation, use the Client Network Utility from the Microsoft SQL Server program group (provided the client software has been installed on the computer).


• The SQL Server 2000 client software handles the complexities of establishing a connection with a server running SQL Server 2000 automatically. The network name of the computer on which the SQL Server 2000 instance is running (and instance name if applicable) is all that is needed to establish the connection, assuming matching network libraries exist.

• Note If a SQL Server 2000 client needs to connect to a named instance of SQL Server 2000, TCP/IP sockets, named pipes, or NWLink IPX/SPX must be used. Named instances are covered in Lesson 4 of this chapter.


Deciding on a Client Licensing Mode

• SQL Server 2000 supports two client licensing modes: per processor and per seat.

• With per-processor licensing, you need a license on the server running SQL Server 2000 for each processor on the computer. If this client licensing mode is selected, no additional licenses are needed for any clients connecting to this installation of SQL Server 2000. This client licensing mode is intended to be most cost-effective for installations with large numbers of users, particularly anonymous Internet users.

• With per-seat licensing, each client connecting to an installation of SQL Server 2000 must have a separate Client Access License (CAL). This client licensing mode is intended to be most cost-effective for installations with a small to medium number of defined users connecting to more than one server.


Running the SQL Server 2000 Setup Program

• After you have selected your SQL Server 2000 edition, and installed the Windows operating system you have decided to use, you are ready to install SQL Server 2000 by running the SQL Server 2000 Setup program. This lesson covers running the SQL Server 2000 Setup program interactively to install an instance of SQL Server 2000 on the local computer

• The easiest way to begin is to simply insert the SQL Server 2000 compact disc into the CD-ROM drive. From the initial dialog box, you can install SQL Server 2000, Analysis Services, or English Query by clicking on SQL Server 2000 Components


• The initial dialog box presents a number of additional options, including providing access to the setup/upgrade portion of Books Online, the Release Notes, and SQL Server Web site at Microsoft.

• Double-clicking on Autorun.exe in the root of the CD-ROM also accesses this initial dialog box. After clicking SQL Server 2000 Components, click Install Database Server to start the SQL Server 2000 Setup program. See Figure 2.1.


Understanding Installation Types

• After you choose to create a new instance of SQL Server 2000 on your local computer.

• you can select Client Tools Only, Server and Client Tools, or Connectivity Only.

• Choose Server and Client Tools when you need to install a server running SQL Server 2000, as well as connectivity software and client management tools. Selecting this option allows you to install SQL Server 2000 in its entirety with all available tools and components.




Selecting a Setup Type

• When you select an installation of Server and Client Tools, you can select to install a Typical, Minimum, or Custom setup.

• The default location for program and data files for each of these setup types is \Program Files\Microsoft SQL Server. If this default location is low on available hard drive space, consider moving the program and data files to another location.

• Click Browse to specify a new location for program files and for data files. They do not need to be in the same location. See Figure 2.4.

• If you select Typical or Minimum, you are presented with these three additional choices. The SQL Server 2000 Setup program makes all other choices for you.



• Table 2.5 lists the components installed with each setup type




Installing a Default Instance of SQL Server 2000

• In this practice you install a default instance of SQL Server 2000, using the Microsoft SQL Server 2000 Evaluation Edition.

1. Ensure that you are logged on to the SelfPacedSQL.MSFT domain controller as Administrator.

2. Insert the SQL Server 2000 compact disc into the CD-ROM drive. The Microsoft SQL Server 2000 Evaluation Edition page appears.

3. Click SQL Server 2000 Components, and then click Install Database Server. The Welcome page for the Microsoft SQL Server Installation Wizard appears.

4. Click Next. The Computer Name page appears with Local Computer selected.

5. Click Next. The Installation Selection page appears with Create A New Instance Of SQL Server, Or Install Client Tools selected.

6. Click Next. The User Information page appears.

7. Type your name in the Name text box (if it does not already appear there), and then click Next. The Software License Agreement page appears displaying the 120-day Evaluation License for Microsoft SQL Server 2000.


8.Click the Yes button. The Installation Definition page appears with Server And Client

Tools selected.

9.Click Next. The Instance Name page appears with the Default check box selected.

10.Click Next. The Setup Type page appears with Typical selected.

11.Click Next. The Services Accounts dialog box appears with Use The Same Account For Each Service. Auto Start SQL Server Service. selected. Use A Domain User Account is also selected.

12.In the Username text box, type SQLService.

13.In the Password text box, type sql.

14.In the Domain text box, verify SelfPacedSQL appears, and then click Next. The Authentication Mode page appears with Windows Authentication Mode selected.

15.Click Next. The Start Copying Files page appears.

16.Click Next. The SQL Server 2000 Setup program will start installing SQL Server 2000 beginning with the MDAC. When the SQL Server 2000 Setup program is complete, the Setup Complete page will appear.

17.Click the Finish button.


Using Default, Named, and Multiple Instances of SQL Server 2000

• SQL Server 2000 supports the installation of multiple instances (or copies) of SQL Server 2000. This capability allows you to have sets of system and user databases that are independent of each other. This capability allows you to work with earlier versions of SQL Server already installed on your computer, to test development software, and to operate instances of SQL Server 2000 independent of each other


• When you install SQL Server 2000, you have the option to define the installation as the default instance or as a named instance. A named instance simply means that you define a name for an instance during installation and that you access that instance using this name. You can only have one default instance, but you can have many named instances. A default instance can be an installation of SQL Server 6.5, SQL Server 7.0, or SQL Server 2000. A named instance can only be an installation of SQL Server 2000.

• When you run the SQL Server 2000 Setup program, it will detect whether a default instance already exists on the computer. If a default instance is not detected, the Setup program allows you to choose to install a default or a named instance. To install a named instance, clear the Default check box. See Figure 2.11.



• If a default instance already exists, you have several choices depending upon the version of SQL Server that is installed as the default instance. Upgrading from earlier versions of SQL Server is covered in Chapter 4.

• If the default instance is a SQL Server 2000 installation, you can install a named instance of SQL Server 2000.

• If the default instance is a SQL Server 7.0 installation, you can choose to upgrade the default instance to SQL Server 2000 or install a named instance of SQL Server 2000.

• If the default instance is a SQL Server 6.5 installation, you

can install SQL Server 2000 as the default instance or as a named instance.


Using Multiple Instances of SQL Server 2000 Effectively and Appropriately

• Using multiple instances of SQL Server 2000 increases administration overhead and causes a duplication of components.

• These additional instances of the SQL Server and SQL Server Agent services require additional computer resources, namely memory and processing capacity. Running multiple databases in a single instance will provide superior performance compared to running a similar number of databases in multiple instances.

• Using multiple instances is appropriate when testing multiple versions of SQL Server on the same computer.

• .Using multiple instances is also particularly appropriate when different customers each require their own system and user databases along with full administrative control of their particular instance.


Understanding Shared Components Between Instances

• Table 2.6 lists the components that are shared between all instances when you install multiple instances of SQL Server. These components are shared regardless of whether the default instance is SQL Server 6.5, SQL Server 7.0, or SQL Server 2000.


Understanding Unique Components Between Instances

• When you install multiple instances of SQL Server 2000 (or SQL Server 2000 and either SQL Server 6.5 and 7.0), system and user databases are unique and completely independent of each other.

• There is no direct connection between system or user databases in one instance and system and user databases in another instance

• Each instance has its own SQL Server and SQL Server Agent services. For the default instance, the names of these services are MSSQLServer and SQLServerAgent. For named instances, the names of these services are MSSQL$instancename and SQLAgent$instancename.

• The database engine for each instance is configured completely independently of any other instance. Jobs on one instance have no knowledge of and do not interact with jobs on any other instance.



Working with Default and Named Instances of SQL Server 2000

• Each instance of SQL Server 2000 listens on a unique set of network addresses.

• The default instance listens on the same network address as earlier versions of SQL Server. Therefore, client applications using client connectivity components from earlier versions of SQL Server can connect to SQL Server 2000 without an upgrade of those connectivity components.

• However, in order to connect to named instances, client applications must use the SQL Server 2000 connectivity components, or the client connectivity components must be configured to connect to alternate addresses appropriate to the particular named instance involved.

• The SQL Server 2000 connectivity components allow client applications to automatically detect the network libraries and network addresses required to connect to default or named instances. The only information that must be provided by the client application is the name of the computer, and the instance name if applicable.


Performing Unattended and Remote Installations of SQL Server 2000

• SQL Server 2000 supports unattended installations of SQL Server 2000, as well as installations of SQL Server 2000 on remote computers. Each of these installation options uses the same underlying structure. This lesson teaches how to use the SQL Server 2000 Setup program to perform each of these types of installations


Performing an Unattended Installation of SQL Server 2000

• Performing an unattended installation of SQL Server 2000 has been made very simple with SQL Server 2000. The process involves running a batch file that calls a setup initialization (ISS) file. The .ISS file contains all setup entries for the options you require for your SQL Server 2000 installation. The command-prompt syntax for performing an unattended setup and calling a setup initialization file is as follows:

• Start /Wait D:\X86\Setup\Setupsql.exe k=SMS -s -m -SMS -f1 "C:\Setup.iss"

• Note The preceding command must be entered as a single line. Change the drive letter, if required, to refer to your CD-ROM drive


Creating Setup Initialization Files for SQL Server 2000

• There are three ways to create setup initialization files for SQL Server 2000 unattended installations. First, the SQL Server 2000 Setup program provides an option in the Advanced Options page to record an unattended .ISS file. If you select this option, you then proceed through the interactive Setup program and select the installation options you want. See Figure 2.12. These options are then recorded in this .ISS file and stored in the \Winnt folder.

• SQL Server 2000 is not actually installed during this process.

This .ISS file can later be used as is, or can be modified by any text editor. SQL Server 2000 Books Online provides detailed information regarding each entry in an ISS file.



• The second way to create a setup initialization file is to use one of the three .ISS files provided on the SQL Server 2000 compact disc (in the root directory). You can use these files as is, or you can modify them using any text editor. Microsoft has provided the following files


• The third way to create a setup initialization file is to modify the Setup.iss file that is automatically recorded each time you install SQL Server 2000.

• This file is placed in the \Winnt directory. This file is a complete record of the choices you made when you installed SQL Server 2000.

• In order to use this file, you must modify it using any text editor and add the [SdFinish-0] section. Refer to any of the setup initialization files on the SQL Server 2000 compact disc or use SQL Server 2000 Books Online for examples of how to complete this section. This corresponds to the Setup Complete dialog box in the interactive setup.


Performing an Unattended Installation of a Named Instance of SQL Server 2000

• Ensure that you are logged on to the SelfPacedSQL.MSFT domain controller as Administrator. • Insert the SQL Server 2000 compact disc into the CD-ROM drive. The Microsoft SQL Server 2000

Evaluation Edition page appears. • Click SQL Server 2000 Components, and then click Install Database Server. The Welcome page for the

Microsoft SQL Server Installation Wizard appears. • Click Next. The Computer Name page appears with Local Computer selected. • Click Next. The Installation Selection page appears with Create A New Instance Of SQL Server, Or Install

Client Tools selected. • Select Advanced Options and then click Next. The Advanced Options page appears with Record

Unattended .ISS File selected. • Click Next. The User Information page appears with your name in the Name text box. • Click Next. The Software License Agreement page appears displaying the 120-day Evaluation License for

Microsoft SQL Server 2000. • Click the Yes button. The Installation Definition page appears with Server And Client Tools selected. • Click Next. The Instance Name page appears with the Default check box grayed out. • In the Instance name text box, type MyNamedInstance, and then click Next. The Setup Type page appears

with Typical selected. • Click Next. The Services Accounts page appears with Use The Same Account For Each Service. Auto Start

SQL Server Service. selected. Use A Domain User Account is also selected. • In the Username text box, type SQLService. • In the Password text box, type sql.


• In the Domain text box, verify that SelfPacedSQL appears, and then click Next. The Authentication Mode page appears with Windows Authentication Mode selected.

• Click Next. The Setup Information page appears. • Click Next. • Click Per Seat for 1 device and then click Continue. The Setup Complete page appears stating that the

unattended installation file is ready to be created. • Click the Finish button. • Using Windows Explorer, locate the Setup.iss file in C:\Winnt. • Right-click Setup.iss, point to Open With, and then click Notepad. • Review the entries and then close Setup.iss. • Right-click the Windows 2000 taskbar and then click Task Manager. The Windows Task Manager dialog box

appears. • Click the Performance tab to observe the CPU Usage and MEM Usage bar graphs during the installation. • Click Start and then click Run. The Open dialog box appears. • In the Open drop-down combo box, type start /wait d:\x86\setup\setupsql.exe k=SMS -s -m -SMS -f1 "c:\

winnt\setup.iss". These paths assume that your CD-ROM drive is D: and that your Windows 2000 installation is C:\Winnt. If your paths are different, change the pathnames accordingly.

• Click OK. A command-prompt window appears and an unattended installation of a named instance of SQL Server 2000 commences. Setup is complete when the command-prompt window closes. This should take between five and ten minutes. If the command-prompt window closes very quickly, you have typed the command incorrectly.

• Close the Windows Task Manager dialog box when setup is complete.


Performing a Remote Installation of SQL Server 2000

• SQL Server 2000 supports performing an installation of SQL Server 2000 onto a remote computer by running the SQL Server 2000 Setup program on the local computer and identifying the computer on which you want SQL Server 2000 to be installed. The remote computer is specified on the Computer Name page during installation. See Figure 2.13.


• The Setup program must be able to establish a connection to this remote computer. You must be logged on using a domain user account that has permission to access the remote computer. After the SQL Server 2000 Setup program establishes a connection to this remote computer, you must specify a logon account that has permission to install SQL Server 2000 on the remote computer, namely an account with full administrative permissions on the remote computer. You must also specify a target path for the installation files and a source path for the setup files. You enter this information on the Remote Setup Information page during installation. See Figure 2.14.


• The SQL Server 2000 Setup program records all of your installation choices into a Setup.iss file. It then copies all necessary files to the remote computer and performs an unattended setup on the remote computer using this Setup.iss file. To the administrator running the Setup program, installing SQL Server 2000 on a remote computer is substantially the same as installing SQL Server 2000 on the local computer using the interactive Setup program.


Troubleshooting a SQL Server 2000 Installation

• The SQL Server 2000 Setup program is designed to detect potential problems during installation and prompt the administrator to solve them during installation. This includes shutting down certain programs that interfere with installation, detecting insufficient disc space, and restarting the computer if certain files are locked. The Setup program will display informational messages as necessary during setup and wait for the problem to be solved by the administrator. However, problems can still occur during an installation of SQL Server. This lesson covers where to look to find the source of these errors. This includes reviewing all relevant log files and accessing SQL Server 2000 troubleshooter information online.


Reviewing SQL Server 2000 Setup Program Log Files

• The SQL Server 2000 Setup program generates several informational files that may be used in isolating problems relating to a failed setup. These are the Sqlstp.log, the Setup.log, and the SearchSetup.log files. Any text editor can read these files. The Sqlstp.log file is located in the \Winnt or \Windows folder and logs errors encountered during the configuration portion of the Setup program. The Setup.log file is also located in the \Winnt or \Windows folder and logs the completion or failure of setup, and records any relevant information. The SearchSetup.log file is located in the \Winnt\Temp folder and logs errors encountered during the configuration of the Microsoft Search service. These three files are primarily useful for Microsoft Product Support; however, reviewing them might give you some clue regarding where setup is failing.


Accessing SQL Server 2000 Troubleshooting Information Online

• Microsoft's Product Support Services (PSS) provides online troubleshooters that are designed to help you resolve problems you might encounter when installing an edition of SQL Server 2000. The online troubleshooter leads you through a series of questions to attempt to isolate the problem and provide you with up-to-date information regarding solving the problem. These troubleshooters cover a wide range of problems, not just problems related to setup. These online troubleshooters are available from the Microsoft Web site at http://Support.Microsoft.com/Support/SQL/Tshooter.asp. The Microsoft Web site, MSDN, and TechNet also contain Knowledge Base articles that contain up-to-date information regarding SQL Server 2000 setup problems.


Reviewing the SQL Server Error Log and the Windows Application Log

• The SQL Server 2000 error log is frequently the most useful place to look for error messages related to SQL Server 2000 setup problems.

• .Each instance of SQL Server 2000 has its own log file. A new log file is created each time SQL Server 2000 starts.

• For the default instance, the current log file is \Program Files\Microsoft SQL Server\Mssql\Log\Errorlog. For a named instance, the current log file is \Program Files\Microsoft SQL Server\Mssql$InstanceName\Log\Errorlog. You can view these logs using SQL Server Enterprise Manager or any text editor.


• The Windows application log in Event Viewer is also a useful place to look for error messages related to SQL Server 2000 setup problems.

• The Windows application log records information, warning, and error messages related to applications running on the Windows operating system.

• Information in the Windows application log combined with information in the SQL Server 2000 error log, each of which time-stamps all recorded events, can help you narrow down and isolate the probable cause of problems.

• You can isolate SQL Server events in the Event Viewer application log by clicking on the View menu, pointing to Filter Events, and then selecting MSSQLSERVER in the Source list.

• Note It is useful to become familiar with the pattern of information in each of these logs when SQL Server 2000 has been installed successfully to quickly differentiate events that indicate a problem.



• Ensure that you are logged on to the SelfPacedSQL.MSFT domain controller as Administrator.

• Using Windows Explorer, locate the Errorlog file in the C:\Program Files\Microsoft SQL Server\Mssql\Log folder.

• Right-click Errorlog and then click Open With. The Open With dialog box appears.

• Click Notepad and then click OK. The contents of the current error log appear in Notepad. Review the entries related to the startup of SQL Server 2000. Become familiar with typical entries.

• Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.



• In the console root, click Application. In the details pane, the contents of the Application Log appear. Review the entries related to the startup of SQL Server 2000. Become familiar with typical entries. Notice that entries for both of your SQL Server 2000 instances appear here.

• Close Windows Explorer, Notepad, and Event Viewer

Documents

Sahar Mosleh California State University San MarcosPage 1 Installing SQL server 2000