***************************************************************
                 MICROSOFT SQL SERVER 6.5 and 
          MICROSOFT SQL SERVER WORKSTATION SYSTEM 6.5
                   SUPPLEMENTAL INFORMATION
***************************************************************

This file contains important information about installing
Microsoft(R) SQL Server(TM) 6.5.

For additional information about SQL Server 6.5, see "What's 
New in SQL Server 6.5" in SQL Server Books Online. Books Online 
contains the most up-to-date information available.

***************************************************************
INSTALLING OR UPGRADING SQL SERVER 6.5

Installing Microsoft SQL Server 6.5 requires approximately 96 MB
of disk space. Upgrading from SQL Server 6.0 requires 20 MB of
disk space and 2 MB of free space in the master database.
Upgrading from SQL Server 4.2 requires 65 MB of disk space and
9 MB of free space in the master database. The SETUP program
will automatically expand the master database and MASTER device
as required.

In all cases, the required disk space must be available on the
drive where SQL Server is located. The SETUP program checks
for required disk space using somewhat smaller values, so you
must manually confirm that enough disk space is available.

When upgrading from Microsoft SQL Server versions 6.0 or 4.2 to 
SQL Server 6.5, the "open databases" configuration option must 
be equal to or greater than the total number of databases on 
your system, including the master, model, tempdb, and pubs 
databases. If the "open databases" configuration option is less 
than the total number of databases on your system, the upgrade 
will fail. You can change the "open databases" configuration 
option using SQL Enterprise Manager or the sp_configure system 
stored procedure.

If you are upgrading from an earlier version of SQL Server and 
you have databases containing textual objects that rely on the 
setting SET QUOTED_IDENTIFIER ON, you should run SETUP.EXE from 
the command line using the following syntax:

setup /t SetQuotedId = ON

Textual objects include stored procedures, triggers, or views, 
and have corresponding rows in the SYSCOMMENTS table. For more 
information about running SETUP.EXE from the command line, see 
"Performing an Unattended Installation" in "SQL Server Setup 6.0."

***************************************************************
XP_SQLREGISTER EXTENDED STORED PROCEDURE

Syntax
xp_sqlregister

Remarks
Helps discover which Microsoft SQL Server version 6.5 servers 
have been installed on the network. xp_sqlregister gathers basic 
configuration information from the operating system, network, 
and SQL Server, and makes this information available to 
xp_sqlinventory. xp_sqlregister automatically executes each time 
SQL Server is started. For more information, see xp_sqlinventory 
in "What's New for SQL Server 6.5."

IMPORTANT
By default, SQL Server is installed in the LocalSystem account. 
The registration information cannot be transmitted over the 
network if SQL Server is running in the LocalSystem account. 

To configure SQL Server to execute in a domain user account

1.  From Windows NT, open Control Panel.
2.  Open the Services Application.
3.  Select the MSSQLServer service.
4.  Choose the Startup button.
5.  Under the Log On As option, select This Account, and type in 
    the account information.

***************************************************************
RUNNING SQLOLE65.SQL

Before you can administer a SQL Server 6.0 server from
SQL Enterprise Manager 6.5, you must run the SQLOLE65.SQL script 
on the SQL Server 6.0 server. SQLOLE65.SQL is an updated 
Transact-SQL script that creates SQL-DMO stored procedures for 
SQL Server 6.0 servers. (You must install these on a SQL Server 
6.0 server before SQL-DMO objects can connect to that server.)

The appropriate SQLOLE65.SQL file can be found in the platform-
specific distribution directory (\ALPHA, \I386, \MIPS, or \PPC)
containing the software compatible with the hardware platform's
processor architecture.

***************************************************************
USING MICROSOFT DISTRIBUTED TRANSACTION COORDINATOR

Microsoft Distributed Transaction Coordinator (MS DTC) addresses 
the challenges of processing transactions over a distributed set 
of software components that exist on a system of networked 
computers. MS DTC is fully integrated with Microsoft SQL Server 
and provides a transaction manager in SQL Enterprise Manager at 
each computer that manages distributed transactions.

For additional information about MS DTC, see "Guide to Microsoft 
Distributed Transaction Coordinator" in SQL Server Books Online.