Installing Microsoft SQL Server 6.5 Developer Edition On Windows NT
Workstation 4.0 sp3 -
a brief Howto.
(Hope some one finds this useful:)
First I'm not a plagarist i referenced the following documents:
Here a the steps i took
Get network up and running:
SQL Server is dependent on network functionality - even for the set-up
it needs to use named-pipe/mailslot functionality. These usually require
a network card to be present. If you don't have a network card
then go to control panel/networks, choose add adapter and then add the
Microsoft loopback adapter - which is just a dummy driver, no hardware
involved. This needs to have working network protocol(s) bound to it.
Let whichever protocols you have use default parameters, EXCEPT for
tcp-ip. If you are using this then do NOT specify dhcp assigned address,
use 192.168.1.1 as the IP address and 255.255.255.0 as the subnet mask.
This is a standard RFC1918 non-routed IP address so shouldn't clash with
any dial-up address you may be given by an ISP.
1.Run Setup.exe from the SQL Server 6.5 folder for your
processor type, usually \Sql65\I386, to start the Setup
2.When the Welcome dialog appears, click Continue to
open the Enter Name and Organization dialog.
3.Complete the Name, Company, and, optionally, the
Product ID text boxes (see fig. 22.1), and then click
Continue to open the Verify Name and Company dialog.
Entering user and organization names.
4.Confirm your entries and click Continue to open the
Microsoft SQL Server 6.5 - Options dialog. If this is a new
installation, select Install SQL Server and Utilities (see fig.
22.2). Otherwise, select Upgrade SQL Server. Click
Continue to open the Choose Licensing Mode dialog.
Specifying a new installation of SQL Server 6.5 and its
steps 5. 6. 7. omited for they apply only to the
server product install.
8.Select the local volume on which to install SQL Server and
accept the default installation folder, unless you have a
reason for doing otherwise (see fig. 22.6). Click Continue
to open the MASTER Device Creation dialog.
Specifying the local disk volume and the installation
folder for SQL Server.
9.You can place the master device on a different volume
and/or in a different folder, if you want. It's recommended
that you specify a size of at least 50M for the master
device (Master.dat file) of a production SQL Server
installation (see fig. 22.7). Click Continue to open the SQL
Server Books Online dialog.
Setting the volume and folder for the master device.
10.Microsoft provides SQL Server's documentation in a
searchable Books Online format, similar to a help file.
Unless you have another SQL Server installation with
Books Online installed, select the Install on Hard Disk
option (see fig. 22.8). Click Continue to display the
Installation Options dialog.
Options for installing the SQL Server 6.5 online
11.Mark the Auto Start SQL Server at Boot Time and Auto
Start SQL Executive at Boot Time check boxes (see fig.
22.9). Autostarting SQL Server is especially important if
you use SQL Server for logging Internet Information Sever
(note i follow the above steps to the letter)
12. - 13 (omited not importent to actually getting it running
on your pc.)
14.The default network protocol for SQL Server is named
pipes, which is sufficient for most Windows NT Server
installations. To change or add network protocols, click
the Networks button in the Installation Options dialog to
open the Select Network Protocols dialog. You can add
multiple protocols by marking the protocol name in the
Install/Uninstall Networks list (see fig. 22.12). After making
your selection, click OK to close the dialog.
Changing or specifying additional network protocols.
15.Click Continue in the Installation Options dialog to open
the SQL Executive Log On Account dialog.
16.SQL Executive, a service for automating execution of
SQL Server processes, needs a login account to start
during the boot process. The default is the domain
Administrator account (see fig. 22.13), which must
previously have been granted Log On as a Service rights.
If you don't want to assign a user account for SQL
Executive at this point, select the Install to Log On as a
Local System Account option. Click Continue to begin
(i made sure of this for my install - give the Administrator
right to log in as a service.)
17. not important
Starting SQL Server and SQL Executive
Before you can configure SQL Enterprise manager for your
newly installed SQL Server system, you must start SQL
Server 6.5. To start SQL Server and SQL Executive after
installation without rebooting Windows NT, do the following:
1.From the Start menu choose Programs, Microsoft SQL
Server 6.5, and SQL Service Manager to open the SQL
Service Manager window.
2.The Server drop-down list box displays the name of the
local SQL Server. Select MSSQLServer from the
Services drop-down list and double-click Start/Continue to
start SQL Server 6.5 (see fig. 22.15, left).
3.Select SQLExecutive from the Services list and
double-click Start/Continue to start SQL Executive (see
fig. 22.15, right).
Starting SQL Server 6.5 and SQL Executive with the SQL
Before you can use SQL Enterprise Manager with your newly
installed server and any other SQL Server 6.x server(s)
previously installed, you must register the server(s) with SQL
Enterprise Manager by following these steps:
1.From the Start menu choose Programs, Microsoft SQL
Server 6.5 Utilities, and SQL Enterprise Manager. Click
OK to close the Tip of the Day dialog, if it appears.
2.If you're running SQL Enterprise Manager for the first
time, the Register Server dialog appears automatically.
Otherwise, choose Register Server from the Server menu
to open the Register Server dialog.
3.In the Server combo box, type the name of the Windows
NT server on which the SQL Server you want to register
resides. If you installed SQL Server for integrated or
mixed security (Trusted Connection), accept the default
Use Trusted Connection option (see fig. 22.18).
Otherwise, select Use Standard Security and type your
administrator account (usually sa, the default account) in
the Login ID text box and your password (empty if you
haven't yet set a password for the sa account) in the
Password text box.
(3 IS VERY VERY IMPORTANT IT IS THE STEP THAT I MISSED
I GAVE ARBITRARY NAMES TO THE SERVER NO! NO! NO!)
If anyone feels that i have missed something or i should clarify
a point please replay and let me know what i missed