Installing SQL Server 2000
Now that you have a general understanding of the different variations of SQL Server 2000, it’s time to install. Again, for this example, I am installing the Standard Edition.
- Insert the SQL Server installation CD into your CD-ROM drive. After a few moments, the autorun installation welcome screen will appear.
- Click on SQL Server 2000 Components. From the list of options that appears, click on (for now) the Install Database Server option.
- The installation wizard will begin. Click on Next.
- The next screen asks you to enter the name of the computer on which you want to install an instance of SQL Server 2000. Select the Local Computer option.
- Click on Next. In the dialog box that appears, select Create a New Instance of SQL Server.
- The next two dialog boxes ask you to enter your name and company (if applicable) and accept the standard Microsoft licensing agreement. You are then presented with the screen, which asks you to pick the type of installation. For this installation, chose Server and Client Tools.
- The next screen asks you to provide an instance name. Provide a descriptive title, then click on Next.
- As with most standard software installations, SQL Server 2000 now prompts you for the type of custom installation you prefer. Leave the default setting as Typical, but note the space requirements and the other installation options.
- You are next asked to provide information on the service accounts used to access SQL Server. For this dialog box, leave the default setting as Domain User Account, but go ahead and enter some type of password that satisfies the usual requirements—easy for you to remember, hard for others to guess. Don’t leave the password blank because that will make you an easy target for unauthorized access.
- Just a few steps left! Select Mixed Mode and be sure to enter a password for the SA (system administrator).
- Click on Next. The installation wizard will tell you it has enough information to proceed with the installation. Click on Next. After a few moments, you will see a confirmation screen telling you that the setup is complete. Click on Finish and reboot your server. (You might be asked to do this, but if not, you should go ahead and reboot anyway.)
Understanding Security: Working with Windows Services
SQL Server 2000 runs as a Windows service, which in a nutshell means that if there is any problem with SQL Server, Windows can take care of it without a great deal of human intervention.
You can set specific SQL Server configuration options by navigating through the Services option, under Administrative Tools. (Note that this only works on Windows NT, 2000, and XP because services don’t exist on Windows 9x operating systems.) This Services option is in the Administrative Tools Control Panel applet.
Now take a look at configuring SQL Server service properties. This will help you gain a further understanding of how SQL Server operates within the Windows operating system, and it will lead into a more complete discussion of the security options that are available for your use.
- In the Start menu, select Settings, Control Panel.
- Double-click on the Administrative Tools icon, and then double-click on the Services icon.
- In the screen that opens, scroll down and select MSSQLSERVER.
- Once you’ve selected MSSQLSERVER, right-click and select Properties from the drop-down menu that appears. The MSSQLSERVER Properties dialog box will appear.
- Click on the Log On tab.
The Log On tab is a good place to begin the discussion of security issues within SQL Server 2000. There are two options to log on to SQL Server.
- Local System account. This simple account was designed to allow you to log on solely to a local account/local installation of SQL Server. Using this account, there is no way that you could log in to a remote server. In a way, this is a neat method of ensuring the instance of SQL Server with which you are working (in other words, you must be working on a local system account).
- Domain account. When you log on to SQL Server utilizing a domain account, the service will verify with the Windows security model to ensure that the user name and password you entered are indeed valid. Note that if you are on a network instead of a local machine, your user name will have a prefix of DOMAINUSERNAME. In order for you to log on to the service in this fashion, the Window security model will verify that the domain account information you’ve provided matches a valid user name and password in the Windows Domain Controller.
Regardless of whether your SQL Server installation is on a remote server or a local machine, it’s probably a good idea to use the domain account setting.That way, the Windows security model (and your user name and password) can help secure the account. Of course, if you are working on a local machine, this might not be as big of an issue, but it is still probably a good idea. Also, in a network environment you might have to ask your system administrator to give you full administrative rights to SQL Server. (The user name should be able to alter the registry, so in essence you need to be made an administrator of your own machine.)
It is not recommended to use your own domain account as a service account. If you must use a domain account, then create one that has the sole purpose of a SQL service account. Also, if you use your own account and you change the password of your account, you must then go back into the Services control panel and change it—it will not automatically change.
I’ll talk more about security and account issues a bit later in the chapter. For now, take a moment to review the Recovery tab in the MSSQLSERVER Properties dialog box.
Did you know?
Most providers forget that web hosting is, and always was, a service, not a product. You must be very carefull when you are searching for a reliable and an affordable company in order to host your new website.