Contents for Microsoft SQL Server Setup Help

 Introduction

 Prerequisites

 Procedures for...

 More About...


Contents-All SQL Server Setup Topics
Contents for Microsoft SQL Server Setup Help

 Introduction

 Setup Overview

 Prerequisites

 Hardware Platforms

 Hardware and Software Requirements

 File Systems

 Server Names

 SMS Version

 Procedures for...

 Creating a User Account for the MSSQLServer Service and SQL Executive

 Installing SQL Server

 Installing Alongside SQL Server 4.2

 Installing a Standalone Server

 Preparing to Upgrade

 Running the CHKUPG65.EXE Utility

 Upgrading from SQL Server 4.2

 Upgrading from an Earlier SQL Server 6.x Release

 Upgrading from SQL Server for OS/2

 Installing or Upgrading SQL Workstation

 Installing or Upgrading 32-bit Client Software

 Changing Network Support

 Using an Alternate Named Pipe

 Setting Server-Enforced Encryption

 Adding a Language

 Rebuilding the Master Database

 Setting Server Options

 Setting Security Options

 Removing SQL Server

 More About...

 The SQL Executive User Account

 Installing

 Upgrading

 Keywords

 Reserved Words

 Character Sets

 Sort Orders

 Client Utilities

 Network Support

 ODBC Support

 Server Installation Paths

 Client Installation Paths

 Languages

 The MASTER Device

 Remote Setup

 Books Online

 Choose Licensing Mode


Contents for Microsoft SQL Server Setup Help

 Introduction

 Setup Overview

 Prerequisites

 Procedures for...

 More About...


Contents for Microsoft SQL Server Setup Help

 Introduction

 Prerequisites

 Hardware Platforms

 Hardware and Software Requirements

 File Systems

 Server Names

 SMS Version

 Procedures for...

 More About...


Contents for Microsoft SQL Server Setup Help

 Introduction

 Prerequisites

 Procedures for ...

 Creating a User Account for the MSSQLServer Service and SQL Executive

 Installing SQL Server

 Installing Alongside SQL Server 4.2

 Installing a Standalone Server

 Preparing to Upgrade

 Running the CHKUPG65.EXE Utility

 Upgrading from SQL Server 4.2

 Upgrading from an Earlier SQL Server 6.x Release

 Upgrading from SQL Server for OS/2

 Installing or Upgrading SQL Workstation

 Installing or Upgrading 32-bit Client Software

 Changing Network Support

 Using an Alternate Named Pipe

 Setting Server-Enforced Encryption

 Adding a Language

 Rebuilding the Master Database

 Setting Server Options

 Setting Security Options

 Removing SQL Server

 More About...


Contents for Microsoft SQL Server Setup Help

 Introduction

 Prerequisites

 Procedures for...

 More About...

 The SQL Executive User Account

 Installing

 Upgrading

 Keywords

 Reserved Words

 Character Sets

 Sort Orders

 Client Utilities

 Network Support

 ODBC Support

 Server Installation Paths

 Client Installation Paths

 Languages

 The MASTER Device

 Remote Setup

 Books Online

 Choose Licensing Mode


Setup Overview

The SQL Server setup program can install new SQL Server software, upgrade the software of an existing installation, install selected components, change selected configuration options, or remove a SQL Server installation.

Server components can be installed on computers running the Windows NT Server operating system. 32-bit client components can be installed on computers running the Windows NT Workstation, Windows NT Server, or Windows 95 operating systems. The Windows NT Server and Windows NT Workstation operating systems must be version 3.51 or later. Earlier versions of Windows NT are not supported.

This setup program can do more than just install the software. After a SQL Server server installation has been accomplished, setup can be used to:

Change network options.

Add a language.

Rebuild the master database and optionally change the character set and sort order.

Set Server and Security options.

Remove SQL Server.

Other setup programs are provided on the SQL Server 6.5 distribution CD that can install client software on computers running the Windows or Windows for Workgroups operating systems. For computers running the MS-DOS operating system, files are provided on the SQL Server 6.5 distribution CD, which can be copied into a directory (in the path) on the client.


Hardware Platforms

Microsoft SQL Server 6.5 can be installed on computers that are based on these microprocessor architectures:

Alpha AXP microprocessors

Intel 32-bit x86-based microprocessors (such as the 80486 or the Pentium)

MIPS microprocessors

Power PC microprocessors

For more information about supported hardware, see the Windows NT Hardware Compatibility List provided with your Windows NT software.


Hardware and Software Requirements

To install the Microsoft SQL Server 6.5 server software on a Windows NT-based computer, you must have the following hardware and software:

Computer

Refer to the Windows NT Hardware Compatibility List for the processor architecture that corresponds to the SQL Server platform you are installing (Intel, Alpha AXP, MIPS, or Power PC).

For example, if you are installing SQL Server for the Intel platform, your choices are any of the 32-bit Intel x86-based microprocessors, such as the 80486 or the Pentium.

Minimum memory

16 MB is required and additional memory is recommended.

If the server will be configured to participate in data replication as either a distribution server or a combined publication/distribution server, it must have at least 32 MB of memory, of which at least 16 MB must be assigned to SQL Server.

Disk drive space

Installing Microsoft SQL Server version 6.5 requires approximately 96 MB of disk space, plus 1 to 15 MB for SQL Server Books Online. Upgrade requirements are as follows:

Upgrading from	Disk space required for  SQL Server 6.5	Free space  required in the  master database	Disk space required for SQL Server  Books Online
New installation	56 MB	25 MB	1 MB if run from CD. 15 MB installed.
SQL Server 6.0	20 MB	2 MB	1 MB if run from CD. 15 MB installed.
SQL Server 4.2x	65 MB	9 MB	1 MB if run from CD. 15 MB installed.
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.

The setup program will automatically expand the master database and the master device as required.

When upgrading to SQL Server 6.5 from version 6.0 or 4.2x, 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 by using SQL Enterprise Manager or the sp_configure system stored procedure.

Compatibility Between SQL Server 6.5 and SQL Server 6.0

SQL Server version 6.5 affects version 6.0 in the following ways:

SQL Server 6.0 can be upgraded to 6.5.

SQL Server 6.0 backups can be loaded into 6.5.

SQL Server 6.5 backups can be loaded into version 6.0 by using Microsoft SQL Server 6.0 Service Pack 3, which is available separately from Microsoft.

SQL Server 6.0 and 6.5 cannot be run side by side.

If you have not SQL Server 6.0 used reserved words in your code, SQL Server applications can remain unchanged.

Upgrades from 6.0 will replace current system files.

Note  Earlier versions of Microsoft SQL Server must be shut down before installing or upgrading to version 6.5. Also, before an upgrade, stop replication and make sure the log is empty. It is recommended that the system administrator's default database be set to MASTER.

Operating system

Microsoft SQL Server 6.5 software must be installed on a computer running the Microsoft Windows NT Server operating system, version 3.51 or later. Earlier versions of Windows NT are not supported.

Microsoft SQL Workstation 6.5 software can be installed on computers running the Windows NT Server or Windows NT Workstation operating systems, version 3.51 or later. Earlier versions of Windows NT are not supported.

Note  SQL Server 32-bit client software can be installed on computers running the Windows NT Server, Windows NT Workstation, or Windows 95 operating systems. On Windows 95 systems, you must have an AUTOEXEC.BAT file in which setup can set the path; setup will not create the file for you.

Network software

SQL Server runs on the Windows NT platform by using the built-in network software. Unless Banyan VINES or DEC PATHWORKS is used, additional network software is not required. Full support for Novell NetWare clients is provided via NWLink.

Network adapter

SQL Server runs on any of the network adapters supported by Windows NT. (If you're running a standalone SQL Server, you do not need a network adapter.) For information about supported network adapters, see the manuals for Windows NT.

Note  Microsoft SQL Server 6.5 is not recommended for installation on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), because these computers perform the resource-intensive tasks of maintaining and replicating the network accounts database and performing network login authentications.


File Systems

Server performance is not affected by the file system used (FAT or NTFS). Your choice of file system should be decided by factors other than performance.

The FAT file system allows dual booting with computers running MS-DOS.

The NTFS file system has security and recovery advantages. If you do not need to dual boot Windows NT with MS-DOS, NTFS is recommended.

SQL Server can be installed on a compressed NTFS volume but at a performance penalty.

For information about choosing the appropriate file system, see your manuals for Windows NT.


Server Names

The server name used by SQL Server is taken from the computer's name. Before installing Microsoft SQL Server on a server computer, make sure that the server's computer name is a valid SQL identifier.

The first character can be alphabetic or an underscore (_). Characters following the first character can include letters, numbers, or the symbols #, $, or _. No embedded spaces are allowed.

If other characters are used in the computer name, rename the computer before installing SQL Server. For instructions on renaming computers, see your documentation for Windows NT. Also, if the renamed computer is a member of a Windows NT Server domain, contact your network administrator to have the new computer name added to the domain.


SMS Version

Microsoft SQL Server 6.5 is compatible with Microsoft Systems Management Server (SMS) version 1.1. However, it is not compatible with version 1.0. During an installation or an upgrade, if SMS version 1.0 is detected the SQL Server setup program displays a warning message.


Creating a User Account for the MSSQLServer Service and SQL Executive

During SQL Server installation, the setup program asks you to provide the domain, username, and password of a Windows NT user account, which it then assigns to SQL Executive. SQL Server setup installs the MSSQLServer service to run under the LocalSystem account, not under a user account.

On Windows NT 3.51-based systems, to take advantage of SQL Server features that require the SQL Server service to access the network (such as replicating data to an ODBC subscriber or generating web pages), you must set up the MSSQLServer service to log on under a user account.

Before installing SQL Server, use the User Manager application (included as part of Windows NT Server) to create a user account that you will assign to SQL Executive. This will usually be a domain user account (although it can be a user account on the local server). It should be reserved for use by SQL Executive (users should not use it to log on).

This user account must belong to the Administrators local group on the SQL Server computer. In addition, it is a good idea to have the Password Never Expires option selected, be granted the Log On As A Service right on the SQL Server computer, have all logon hours allowed (although this is only necessary for domain accounts, because this option does not apply to accounts on the local server).

Several SQL Servers can share the same user account. In fact, when setting up replication it is a good idea for a publication server and all its subscription servers to share the same account.

During SQL Server installation, if you do not know (or have not yet created) this Windows NT user account, you can choose to complete the installation without specifying a user account. The setup program will install SQL Executive by using the computer's LocalSystem account. You can later use the Services application in Control Panel (or the Services command in Server Manager) to assign an appropriate user account to SQL Executive. Note, however, that if SQL Executive is assigned the LocalSystem account, it runs in the security context of that account and can be prevented from accomplishing many connectivity-related tasks.

After installation, you can modify SQL Server to run under a different user account. For example, to explicitly control SQL Server permissions to access resources on other computers, run SQL Server under a domain user account. You can change account assignments by using the Control Panel Services application.

To set up the MSSQLServer service to log on under a different 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.

Note  The account under which MSSQLServer service logs on must meet the same requirements as the account under which SQL Executive logs on. For convenience, run the MSSQLServer service and the SQL Executive service under the same user account.

During an upgrade from SQL Server version 4.2 or SQL Server 6.0 to SQL Server 6.5, you are prompted for user account information in the same manner as for a new SQL Server 6.5 installation.

For information about creating Windows NT user accounts, granting advanced user rights, setting password expiration, and managing group memberships, see your manuals for Windows NT or the User Manager online Help.

Note  After you have assigned a domain user account to SQL Executive, if a condition later occurs where you start SQL Executive and the server cannot for any reason access a domain controller, then the logon attempt will fail and SQL Executive will not start. You can start it by running the Services application from Control Panel (or by using the Services command from Server Manager) and assigning the LocalSystem account to SQL Executive. However, remember that if SQL Executive is assigned the LocalSystem account, it runs in the security context of that account and can be prevented from accomplishing many connectivity-related tasks.

See Also

MSSQLServer and SQL Executive Requirements


MSSQLServer and SQL Executive Requirements

The requirements for MSSQLServer service and SQL Executive accounts can be set by using the Windows NT User Manager application:

The account must be a member of the Administrators local group.

The account must have the Password Never Expires attribute.

The password for the Windows NT user account must not be changed or allowed to expire.

The account must be granted the following advanced User Rights:

Log on as a service

Act as part of the operating system

Replace a process level token

Increase quotas

See Also

Installing SQL Server

The SQL Executive User Account

Help Contents


Installing SQL Server

Before you start the setup program, you must log on to the system by using a username that has administrative privileges. (However, this is a requirement only when installing server components; you can install the client components by using any valid username.)

Note  Earlier versions of Microsoft SQL Server should be shut down before installing or upgrading to version 6.5. Also, before upgrading, stop replication and make sure that the log is empty.

The SQL Server 6.5 CD contains four separate setup directories, one for Intel-based computers (the \I386 directory), one for MIPS®-based computers (the \MIPS directory), one for Alpha AXP-based computers (the \ALPHA directory), and one for Power PC-based computers (the \PPC directory). You must install SQL Server from the directory containing the software compatible with your hardware platform. You cannot use a different processor architecture's setup program to install SQL Server.

To install Microsoft SQL Server 6.5

1.	From the SQL Server CD, open the appropriate platform subdirectory and run setup. Complete each dialog box that appears.

2.	If you are installing the software on a remote computer, when the Options dialog box appears, choose the Remote button, complete the Remote Setup dialog box, and then choose the OK button.

If you are installing the software on the local computer, skip step 2.

3.	From the Options dialog box, select the Install SQL Server and Utilities option, and then choose the Continue button.

4.	Follow the on-screen instructions. If necessary, you can choose the Help button or press F1 to access the setup program's online Help.

Note  When you perform a new installation on a remote computer, the setup program configures the remote SQL Server as if the computer has 16 MB of memory. If this default is not correct, use SQL Enterprise Manager or the sp_configure system procedure on the remote SQL Server to change the setting of the memory configuration option. For information about setting the memory configuration option, see the Microsoft SQL Server Transact-SQL Reference or the Microsoft SQL Server Administrator's Companion.

After the server is installed there are several configuration tasks can perform, such as setting server configuration parameters, setting security parameters, and registering the server and adding it to a server group. For more information, see the Microsoft SQL Server Administrator's Companion.

See Also

Installing

Remote Setup


Installing Alongside SQL Server 4.2

Earlier versions of Microsoft SQL Server must be shut down before installing version 6.5.

SQL Server 6.5 and SQL Server 4.2 can be installed alongside each other on the same server. Both can be run simultaneously. SQL Server 6.5 will be treated as a new installation and will not incorporate any configuration settings from the existing SQL Server 4.2 installation.

When a side-by-side installation is performed, each SQL Server version must be installed in its own directory tree. In many cases, SQL Server 4.2 has been installed under the \SQL root directory (the old default) and SQL Server 6.5 is installed under the \MSSQL root directory. The default directory for SQL Server 6.0 is \SQL60. If SQL Server 6.0 exists, only the upgrade options for version 6.5 will be available.

Because both SQL Server 4.2 and SQL Server 6.5 use the same default named pipe, neither SQL Server 6.5 nor SQL Server 4.2 must be configured to use an alternate named pipe . For SQL Server 4.2, an alternate named pipe can be set by editing the Windows NT Registry. For SQL Server 6.5, an alternate named pipe can be set by using the setup program Change Network Support option. (It is not necessary to use the Registry Editor.)

Note that if you change the named pipe a server listens on, clients that will connect to the server by using named pipes must also be set up to connect to that server by using the new pipe name.

If you install other Net-Libraries, make sure they are configured by using names and parameters that do not duplicate those used by the SQL Server 4.2 installation.

To install SQL Server 6.5 while retaining an existing SQL Server 4.2 installation

1.	Shut down the version 4.2 server.

2.	Start setup, then complete each dialog box that appears.

3.	If you are installing the software on a remote computer, when the Options dialog box appears, choose the Remote button, complete the Remote Setup dialog box, and then choose the OK button.

If you are installing the software on the local computer, skip this step.

4.	From the Options dialog box, select the Install SQL Server and Utilities option, then choose the Continue button.

When performing a side-by-side installation, do not select the Upgrade SQL Server option.

5.	Follow the on-screen instructions until the installation is complete.

6.	After SQL Server 6.5 is installed and you have rebooted the computer, change the default named pipe for one of the SQL Server installations on that computer.

The default named pipe a server listens on is \\.\pipe\sql\query. For SQL Server 4.2, an alternate named pipe can be set by editing the Windows NT Registry. For SQL Server 6.5, an alternate named pipe can be set by using the setup program Change Network Support option. (For version 6.5, it is not necessary to use the Registry Editor.)

For example, you might change the version 4.2 server to use \\.\pipe\sql42\query, but leave the version 6.5 server with the default, \\.\pipe\sql\query.

7.	As necessary, set up clients to use the alternate named pipe.

Because you have changed the named pipe one of the SQL Servers listens on, clients that connect to that server by using named pipes must be configured to connect by using the new pipe name. For Windows NT-, Windows 95-, and Windows-based computers, you can set the alternate pipe name by using the Advanced window of the SQL Server Client Configuration Utility. Use different server names for the different pipes the client connects to.

For example, you might set up clients to use terrier for \\terrier\pipe\sql\query and terrier42 for \\terrier\pipe\sql42\query.

Utilities such as SQL Performance Monitor will connect to the server that is using the default named pipe.

See Also

Using an Alternate Named Pipe

Help Contents


Installing a Standalone Server

The procedure for installing SQL Server software on a standalone computer (one that does not have a network adapter) is nearly the same as the standard installation procedure, except all network and remote setup options are unavailable.

Important: If the setup program is unable to start the network, it assumes you are installing on a standalone computer. If you are installing SQL Server on a computer with a network adapter and the setup program is unable to start the network, exit the setup program, correct your network problem, and then restart the setup program.

See Also

Installing SQL Server

Help Contents


Preparing to Upgrade

Before you begin an upgrade:

Back up all your databases (including the master database).

If any databases are set to read-only, run sp_dboption and set the read only option to FALSE.

Run the CHKUPG65.EXE utility, which checks that database status is acceptable, that all necessary comments exist in syscomments, and that there are no keyword conflicts. CHKUPG65.EXE creates a report file. Review the report and take any action the report indicates is necessary to prepare the existing installation for an upgrade.

Check that there is adequate physical disk space to perform the upgrade.

At least 65 MB of free disk space is required to upgrade from SQL Server 4.2 to SQL Server 6.5. SQL Server 6.5 requires a total of 90 MB of disk space and up to an additional 15 MB for SQL Server Books Online.

The master database must have at least 9 MB free disk space, but if that much space is not available the setup program automatically alters the master database to increase the space allocated to it. If necessary, setup also increases the size of the MASTER device (as long as adequate disk space is available).

Check that applications that could be using any of the SQL Server DLLs are not running on the server that you are going to upgrade. (These applications include SQL Server, SQL Monitor, and SQL Server client applications such as isql, SQL Administrator, and SQL Object Manager.) Also check that Microsoft Word for Windows and Microsoft Visual C++ are not running or any of the applications that use the Microsoft Visual C++ runtime library (MSVCRT20.DLL).

In general, make sure no applications are running on the server you are upgrading.

Log on to the system under a user account that has administrative privileges.

See Also

Running the CHKUPG65.EXE Utility

Upgrading from SQL Server 4.2

Help Contents


Running the CHKUPG65.EXE Utility

Before you begin an upgrade, run the CHKUPG65.EXE utility, which checks that database status is acceptable, that all necessary comments exist in syscomments, and that there are no keyword conflicts. CHKUPG65.EXE writes this information to an output file. Review the report and take any action the report indicates is necessary to prepare the existing installation for an upgrade.

To check a SQL Server 4.2 installation prior to upgrading

From the directory containing the applications compatible with your hardware platform's processor architecture (Intel, Alpha AXP, or MIPS), run the CHKUPG65.EXE utility. This is the utility syntax:

chkupg [/Usa] [/Ppassword] [/Sservername] /ofilename

where

password

Is the SA password. If no password is provided, NULL is assumed.

servername

Is the name of the server being upgraded. If no servername is provided, the local server is assumed.

filename

Is the name of the output file. It must be a fully qualified filename, including the drive and directory on that server where the output file will be placed.

For example:

chkupg /Usa /P /S /oc:\sql\install\myreport.out

After running CHKUPG65.EXE, read its output file by using any text editor.

If the CHKUPG65.EXE output file indicates that the database is set to read-only, run sp_dboption and set the read only option to FALSE. For information about sp_dboption, see the Microsoft SQL Server Transact-SQL Reference.

If the CHKUPG65.EXE output file shows that some text in syscomments is missing or altered, drop and re-create the related objects, then run CHKUPG65.EXE again to verify that the necessary text exists in syscomments. (You cannot upgrade all objects from SQL Server 4.2 systems to SQL Server 6.5 if you have deleted data from the text column in the syscomments table. The setup program uses the comments in syscomments to upgrade database objects.)

If the CHKUPG65.EXE output file indicates conflicts with SQL Server 6.5 keywords, change the conflicting database or database object name, and alter the applications that access those objects so that they use the new names. Keyword conflicts can be resolved either before or after the server is upgraded. Keyword conflicts will not cause an upgrade to fail. For a list of keywords, see Keywords.

CHKUPG65.EXE reports both on keywords implemented in SQL Server 6.5 and words that are reserved for future use but are not yet implemented. Reserved words are compatible with SQL Server 6.5 but can be expected to cause future conflicts. Reserved words are indicated in the output file by this notation:

[SQL-92 keyword]

CHKUPG65.EXE only checks and reports on the current SQL Server 4.2x system. It does not correct incompatibilities, change read-only databases, add comments to syscomments, or take any other corrective action.

When you run setup and perform an upgrade from SQL Server 4.2 to SQL Server 6.5, one of the first things setup does is to run CHKUPG65.EXE automatically and inform you if a problem exists. Although setup runs CHKUPG65.EXE automatically, it is recommended that you first run CHKUPG65.EXE separately.

See Also

Keywords

Reserved Words

Preparing to Upgrade

Upgrading from SQL Server 4.2


Upgrading from SQL Server 4.2

Microsoft SQL Server 4.2 on a Windows NT-based computer can be upgraded to SQL Server 6.5.

To upgrade Microsoft SQL Server 4.2 to SQL Server 6.5

1.	Accomplish the upgrade prerequisites described in:

Preparing to Upgrade

Running the CHKUPG65.EXE Utility

2.	Shut down the 4.2 server.

3.	From the directory containing the software compatible with your hardware platform's processor architecture (Intel, Alpha AXP, MIPS, or PPC), run SETUP.EXE and follow the on-screen instructions.

Note  If you are upgrading from an earlier version of SQL Server and you have databases that contain 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

For more information about running SETUP.EXE from the command line, see Performing an Unattended Installation in SQL Server Setup 6.0.

4.	If you are installing the software on a remote computer, when the Options dialog box appears, choose the Remote button, complete the Remote Setup dialog box, and then choose the OK button.

If you are installing the software on the local computer, skip this step.

5.	From the Options dialog box, select the Upgrade SQL Server option, and then choose the Continue button.

6.	Follow the on-screen instructions. If necessary, you can choose the Help button or press F1 to access the setup program online Help.

Regardless of what networks you've configured SQL Server to listen on, the setup program always uses named pipes when connecting to the server during an upgrade. (Named pipes work between Windows NT-based computers no matter what network transport the computers are running.)

Important: If the DBLibrary software on the computer from which the setup program was started is configured to use an IPC mechanism other than named pipes, the setup program temporarily changes the default network to named pipes. If in the rare case that setup terminates unexpectedly without restoring the original default network value, you might need to reset this value yourself by using the SQL Server Client Configuration Utility. In addition, if you've been starting SQL Server on an alternate pipe or have disabled named pipes altogether, you must temporarily reconfigure SQL Server to listen on the standard pipe (\\.\pipe\sql\query) before beginning the upgrade.

After completing the upgrade and rebooting your server computer, check your Windows NT search path (path) to be sure that the \MSSQL\BINN directory precedes any \SQL\BIN or \SQL\BINP directories used for earlier releases of SQL Server. If the server computer has multiple versions of SQL Server components, checking the system search path ensures that the current Windows NT-based version is the one that will run.

To check your Windows NT search path

From an operating-system prompt, type:

path

After the server is upgraded there are several configuration tasks you may need to perform, such as setting server configuration parameters, setting security parameters, and registering the server and adding it to a server group. For more information, see the Microsoft SQL Server Administrator's Companion.

See Also

Preparing to Upgrade

Running the CHKUPG65.EXE Utility


Upgrading from an Earlier SQL Server 6.x Release

If you are upgrading from an earlier SQL Server 6.x installation, from the directory containing the software compatible with your hardware platform's processor architecture, run the setup program.

Note  If such that if you have databases that contain 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

For more information about running SETUP.EXE from the command line, see Performing an Unattended Installation in SQL Server Setup 6.0.

Upgrade SQL Server and Utilities is the only installation option available. It is not necessary to run the CHKUPG65.EXE utility.

See Also

Upgrading from SQL Server 4.2

Help Contents


Upgrading from SQL Server for OS/2

A Microsoft SQL Server 4.2 for OS/2 server can be upgraded to Microsoft SQL Server 6.5 by first upgrading the operating system to Windows NT Server 3.51 and then running the SQL Server setup program to upgrade the SQL Server files.

To upgrade a Microsoft SQL Server for OS/2 system to SQL Server 6.5

1.	Back up all of your databases (including the master database).

2.	Upgrade the operating system.

If you will be installing SQL Server 6.5, upgrade the OS/2 operating system to the Windows NT Server version 3.51. If you will be installing SQL Workstation 6.5, upgrade to the Windows NT Workstation version 3.51. Earlier releases of Windows NT are not supported.

For operating system upgrade information, see your manuals for Windows NT.

3.	From the i386 directory containing the software compatible with the Intel processor architecture, run the SQL Server 6.5 setup program and follow the on-screen instructions.

4.	From the Options dialog box, select the Upgrade SQL Server option, and then choose the Continue button.

5.	Follow the on-screen instructions. If necessary, you can choose the Help button or press F1 to access the setup program online Help.

See Also

Upgrading from SQL Server 4.2


Installing or Upgrading SQL Workstation

Microsoft SQL Workstation 6.5 has the same features and functionality as Microsoft SQL Server, except that it is a single-user licensed product that supports a maximum of 15 simultaneous database connections. SQL Workstation is primarily intended to be used as a development platform.

To install, upgrade, test, configure, or remove SQL Workstation, follow the instructions provided for SQL Server.

See Also

Installing SQL Server

Upgrading from SQL Server 4.2

Help Contents


Installing or Upgrading 32-bit Client Software

The following procedure explains how to install and upgrade Microsoft SQL Server client software on computers running the Windows NT Server, Windows NT Workstation, or Windows 95 operating sytems. You can run the setup program from a local drive or from a network drive. Remember that while running setup you can choose the Help button or press F1 to access the online Help for the setup program.

Note  You do not need to install SQL Server client utilities on a computer that already has the SQL Server server components installed on it, because the client utilities are automatically installed with the server components.

To install client software on a Windows NT-based computer

1.	From the directory containing the software compatible with your hardware platform processor architecture, run SETUP.EXE and complete each dialog box that appears.

2.	If you are installing the software on a remote computer, when the Options dialog box appears, choose the Remote button, complete the Remote Setup dialog box, and then choose the OK button.

If you are installing the software on the local computer, skip this step.

3.	From the Options dialog box, select the Install Utilities Only option, and then choose the Continue button.

The Install Client Utilities dialog box appears.

4.	Complete the Install Utilities dialog box.

In the Drive box, select the drive on which to install the client utilities.

In the Directory box, type the name of the root directory in which to install the client utilities. The default is \MSSQL.

The Utilities To Be Installed list displays all the available utilities and a check box for each. By default, all utilities are selected for installation. Clear the check box for each utility you do not want to install.

Choose the Continue button. The SQL Server Books Online dialog box appears.

5.	Complete the SQL Server Books Online dialog box, and choose the Continue button.

6.	When the installation is finished the Completed dialog box appears. Choose the Reboot button.

Once the computer reboots, the SQL Server graphical client utilities can be accessed and used from the Microsoft SQL Server 6.5 program group.

When installing client utilities on a Windows 95-based computer an AUTOEXEC.BAT must exist to receive updated path information for the SQL Server root directory. If it does exist, it will be updated. The old AUTOEXEC.BAT file is saved as AUTOEXEC.nnn, where nnn is a number from 001 to 099.

To install client software on a Windows 95-based computer

1.	From the i386 directory, run SETUP.EXE and complete each dialog box that appears.

2.	When the Install or Remove Client Utilities dialog box appears, select the Install Utilities Only option and then choose the Continue button.

The Install Client Utilities dialog box appears.

3.	Complete the Install Utilities dialog box and choose the Continue button.

The SQL Server Books Online dialog box appears.

4.	Complete the SQL Server Books Online dialog box, and choose the Continue button.

5.	When the installation is complete, the Completed dialog box appears.

To upgrade an existing client installation on a 32-bit computer

Make certain that no SQL Server client components are running on the computer, then perform the same steps as for a new installation.

See Also

Client Utilities

Remote Setup


Changing Network Support

To change network support options

1.	If you are changing the network support on a remote computer, choose the Remote button from the Options dialog box, complete the Remote Setup dialog box, and then choose the OK button.

If you are changing the network support on the local computer, begin with step 2.

2.	From the Options dialog box, select the Change Network Support option.

3.	Choose the Continue button.

The Select Network Protocols dialog box appears.

4.	Select which networks to support on the server. (Note that the setup program preselects any networks for which server Net-Libraries have already been installed. If you deselect a network, the setup program removes the Net-Library from your configuration.)

5.	Choose the OK button.

6.	Follow the on-screen instructions.

See Also

Network Support

Remote Setup


Setting Server-Enforced Encryption

The Multi-Protocol Net-Library supports optional encryption for both data exchange and user password authentication when communicating over trusted (integrated security) connections. Encryption can be either set at each client or enforced for all clients by the server. Server-enforced encryption automatically encrypts all communication between clients by using the client-side Multi-Protocol Net-Library and the server listening on the server-side Multi-Protocol Net-Library.

To configure a server to enforce encryption

1.	To set encryption for a remote server, choose the Remote button from the Options dialog box, complete the Remote Setup dialog box, and then choose the OK button.

If you are setting encryption for the local server, begin with step 2.

2.	From the Options dialog box, select the Change Network Support option, then choose the Continue button.

The Select Network Protocols dialog box appears.

3.	Select Multi-Protocol, then choose the OK button.

The Multi-Protocol Encryption dialog box appears.

4.	Select the Enable Encryption box.

5.	Choose the Continue button.

Server-enforced encryption is supported only by the Multi-Protocol Net-Library. Note that if Net-Libraries for other protocols are also loaded by the server, incoming connections over those Net-Libraries will not use encryption.

See Also

Help Contents


Using an Alternate Named Pipe

By default, a SQL Server listens on the \\.\pipe\sql\query named pipe. You have the option of changing this.

To specify an alternate named pipe for the server to listen on

1.	If you are changing the named pipe for a remote server, choose the Remote button from the Options dialog box, complete the Remote Setup dialog box, and then choose the OK button.

If you are changing the named pipe for the local server, begin with step 2.

2.	From the Options dialog box, select the Change Network Support option, then choose the Continue button.

The Select Network Protocols dialog box appears.

3.	Select the Named Pipes option, then choose the OK button.

The Named Pipe Name dialog box appears.

4.	In the Named Pipe Name box, type the new pipe name. For example:

\\.\pipe\mssql\query

5.	Choose the Continue button.

All clients attempting connect over named pipes to the SQL Server 6.5 installation must be configured to connect by using the alternate named pipe. For Windows NT-, Windows 95- and Windows-based computers, this configuration can be set up using the Advanced window of the SQL Server Client Configuration Utility.

If both SQL Server 4.2 and SQL Server 6.5 have been installed on the same server, you must assign different server names for the different pipes. For example terrier for \\.\pipe\sql\query and terrier60 for \\.\pipe\mssql\query.

See Also

Help Contents


Adding a Language

You can add another language at any time by running SQL Setup and choosing the Add Language option. It is not necessary to perform a full installation.

To install an additional language on the server

1.	Start SQL Setup, and follow the on-screen instructions until the Microsoft SQL Server 6.5 Options dialog box appears.

2.	From the Options dialog box, select the Add Language option.

The Select Language dialog box appears.

3.	In the Language Name box, type the name of the language.

4.	In the SA Password box, type the password to use when installing the language file.

5.	To set this alternate language as the default language for SQL Server, choose the check box for Default Language.

6.	Choose Continue.

The SQL Server Path dialog box appears.

7.	In Path box, type the full path (drive letter, path, and filename).

8.	Choose Continue.

See Also

Languages

Remote Setup


Languages

Microsoft SQL Server is available in both United States English and localized versions. All versions include system messages in United States English. Localized versions also include system messages that have been translated into another language.


Rebuilding the Master Database

The setup program can be used to rebuild the master database. It rewrites the master database and resets the configuration values on its existing device. During the rewrite process you can also change the server's character set and sort order.

Rebuild the master database only when it is absolutely necessary. Rebuilding the master database completely rewrites the master database, destroys all information added since SQL Server was first installed, and renders all other databases unusable. If you rebuild the master database, you must reload the database from the most recent dump, and then reapply any changes not included in the dump.

When rebuilding the master database, you have the option of changing the character set or sort order. Because the sort order is used to construct all indexes, including system indexes, all databases must be rebuilt if you change the sort order. The setup program rebuilds the master database for you, but you must rebuild all other databases yourself. The following procedure includes the steps required to rebuild your databases.

If you must rebuild the master database or change the character set or sort order, follow this procedure.

To rebuild the master database

1.	If you are changing the character set or the sort order, back up all databases. If not, skip to step 4.

2.	Put all data definition language (DDL) commands in batch files. You will use the batch files to recreate the structure of your databases after changing the sort order. (SQL Enterprise Manager can help with this step.)

3.	Use the bcp (bulk copy) utility to copy data out of your tables.

Include all database objects. Also copy out lists of users.

4.	Back up the entire SQL Server directory tree and any disk devices that you have created in other directories.

5.	Start the setup program and follow the on-screen instructions until the SQL Server Setup Options dialog box appears.

6.	If you are rebuilding the master database on a remote computer, choose the Remote button, complete the Remote Setup dialog box, and then choose the OK button.

7.	From the SQL Server Setup Options dialog box, select the Rebuild Master Database option.

8.	Choose the Continue button.

The setup program asks for confirmation, and then prompts you for any additional information required.

9.	Provide the information as requested until the master database rebuild is complete.

10.	If you changed the character set or sort order, recreate all databases using the batch files created in step 2, and then copy the data back into your databases by using bcp.

Note  The files MASTER.DA@ and MASTER.AL@ are stored in the \MSSQL\INSTALL directory. When installing SQL Server or rebuilding the master database, one of these two files is used. When the default sort order and character set are selected during an installation or a master database rebuild, MASTER.DA@ is expanded and copied onto the server, replacing MASTER.DAT. When an alternate character set and/or sort order is selected, MASTER.AL@ is expanded, copied onto the server, and several SQL scripts are run. Because of this, selecting the default character set and sort order results in a rapid master database rebuild. Choosing an alternate character set or sort order can result in a somewhat longer rebuild time.

Because of the introduction of one-way encrypted passwords in SQL Server 6.5, changing the sort order has an impact on the use of passwords. For information, see Appendix A, "Character Sets and Sort Orders," in Microsoft SQL Server Setup.

See Also

The MASTER Device

Remote Setup


master Database

The master database is the system database that keeps track of user accounts, remote user accounts, remote servers, environment variables, system error messages, system databases, database storage allocation, devices, and active locks.


Setting Server Options

You can set a number of server options by using the Select Server Options dialog box.

To set server options

1.	If you are setting server options on a remote computer, choose the Remote button from the Options dialog box, complete the Remote Setup dialog box, and then choose the OK button.

If you are setting server options on the local computer, skip this step.

2.	From the Options dialog box, select Set Server Options, then choose Continue.

The Select Server Options dialog box appears.

3.	Review and/or change the server options.

For information about each option, see the topics following this procedure.

4.	When the options are set, choose Change Options.

The changes become effective the next time SQL Server is started.

For information about each server option, choose one of the following topics:

 Root Directory

 Master Database Path

 Error Log Path

 Auto Start Server At Boot Time

 Auto Start Executive At Boot Time

 Auto Start Mail Client

 Windows NT Event Logging

 SQL PerfMon Integration

 Direct Response Mode

 On Demand Mode

 xp_cmdshell Impersonates Client

 Enabling SNMP Support

 Parameters

 Tape Support

 Mail Login


Setting Security Options

The SQL Server setup program offers several options for configuring login security. For example, SQL Server provides a way to integrate SQL Server login security with Windows NT security so that authorized users do not have to maintain separate SQL Server login passwords and can bypass the login process of SQL Server. In addition, integrated security lets SQL Server applications take advantage of Windows NT security features, including encrypted passwords, password aging, domain-wide user accounts, and Windows-based user administration.

To set security options

1.	If you are setting security options on a remote computer, choose the Remote button from the Options dialog box, complete the Remote Setup dialog box, and then choose the OK button.

If you are setting security options on the local computer, skip this step.

2.	From the Options dialog box, select Set Security Options, then choose Continue.

The Set Security Options dialog box appears.

3.	Review and/or change the security options.

For information about each option, see the topics following this procedure.

4.	When the options are set, choose OK.

The changes become effective the next time SQL Server is started.

For more information about each security option, choose one of the following topics:

 Standard

 Windows NT Integrated

 Mixed

 Default Login

 Default Domain

 Set Hostname to User Name

 Successful Logins

 Failed Logins

 Map _

 Map $

 Map #


Removing SQL Server

When you remove a SQL Server installation, the setup program deletes all SQL Server entries from the Windows NT Registry. It also gives you the option to automatically delete the SQL Server directory tree from the root down. (If you choose this option, after setup has performed the SQL Server removal you must manually delete the SQL Server root directory and a few remaining files. This is because setup cannot delete itself.)

To remove a SQL Server installation

1.	From the Microsoft SQL Server 6.5 program group, start the setup program.

2.	Follow the on-screen instructions until the Options dialog box appears.

3.	If you are removing the software from a remote computer, choose the Remote button, complete the Remote Setup dialog box, and then choose the OK button.

4.	From the Options dialog box, select the Remove SQL Server option.

5.	Choose the Continue button.

The Remove SQL Server dialog box appears.

6.	To remove SQL Server files from your hard disk, select the Remove Files From check box. Note that if the master database file (MASTER.DAT) exists in a non-default location, it will not be removed.

7.	Choose the Resume button.

See Also

Remote Setup


The SQL Executive User Account

Usually, SQL Executive is started and run as a Windows NT service. This integration with the Windows NT Service Control Manager allows SQL Executive to be started and stopped as a service, either locally or remotely.

Windows NT services run in the security context of the user account to which they are assigned. The default is for the system to assign the LocalSystem account to services. However, services can have a Windows NT user account assigned to them by using the Services application in the Control Panel.

Before you install SQL Server, create a Windows NT user account that can be assigned to the SQL Executive service. This will enable the service to accomplish connectivity-related tasks, such as performing replication or running scheduled tasks that involve other servers.

During SQL Server installation, the setup program prompts you to provide the domain, username, and password of a Windows NT user account, which it then assigns to SQL Executive and the MSSQLServer service as its user account. (The setup program always assigns SQL Server the LocalSystem account, although you can change this after installation by using the Services application in Control Panel.)

See Also

Creating a User Account for the MSSQLServer Service and SQL Executive

Help Contents


Installing

The files MASTER.DA@ and MASTER.AL@ are stored in the \MSSQL\INSTALL directory. When installing SQL Server one of these two files is used. When the default sort order and character set are selected during an installation, MASTER.DA@ is expanded and copied onto the server, replacing MASTER.DAT.

When an alternate character set and/or sort order is selected, MASTER.AL@ is expanded, copied onto the server, and several SQL scripts are run. Because of this, selecting the default character set and sort order results in a rapid installation (in most cases, 5 to 10 minutes or less). Choosing an alternate character set or sort order can result in a somewhat longer installation time (but less than 30 minutes).

When you perform a new installation, the setup program:

Installs the SQL Server files on your hard disk.

Runs SQL Server scripts and utilities to update configuration information and create system databases, tables, and procedures.

Registers SQL Server with the Windows NT Service Control Manager.

Updates the Windows NT Registry.

Creates a Program Manager program group for SQL Server that contains icons for SQL Server and the SQL Server tools.

Grants SQL Server system administrator privileges to all members of the server's Administrators local group.

See Also

Installing SQL Server


Upgrading

A Microsoft SQL Server 4.2 server on a Windows NT-based computer can be upgraded to SQL Server 6.5 by running the setup program and choosing the upgrade option. Also, a Microsoft SQL Server 4.2 for OS/2 server can be upgraded to Microsoft SQL Server 6.5 first by upgrading the operating system to Windows NT Server, and then by running the SQL Server setup program to upgrade the SQL Server files. Upgrades from SQL Server 1.x are no longer supported.

Because of improvements to the system (such as new system tables and datatypes), an upgrade is a one-way operation and cannot be reversed. Once a version 4.2 database has been upgraded to version 6.5 it cannot be used again with SQL Server 4.2.

Before upgrading a Microsoft SQL Server 4.2 server, run the CHKUPG65.EXE utility, which checks that database status is acceptable, that all necessary comments exist in syscomments, and that there are no keyword conflicts.

The setup program cannot upgrade from one processor version to another (for example, from Intel- to MIPS-based computers). Also, it is not possible to dump a database in one processor architecture and load it in another. Even if the operation appears to succeed, serious problems will subsequently result. For example, you cannot dump a database from an Alpha AXP-based computer and load it into an Intel-based computer. Nor should you copy your MASTER.DAT from an Intel-based computer to a MIPS- or Alpha AXP-based computer and run setup to upgrade it. However, you can use SQL Transfer Manager to transfer data from one architecture to another.

Note  SQL Server 6.5 detects and prevents attempts to load a dump from a different SQL Server 6.5 processor architecture, but it cannot prevent an attempt to load a dump from a different SQL Server 4.2 processor architecture because that information is not recorded by a SQL Server 4.2 level database dump.

Most applications written to work with SQL Server 4.2 should work unmodified with SQL Server 6.5. However, because new keywords have been added that may conflict with existing applications, this is not true in all cases. For a list of new keywords, see the Microsoft SQL Server Transact-SQL Reference. Corrections to the behavior of subqueries may also affect applications that depended on the old behavior.

Note  For information about language, statement, query, and other compatibility issues between SQL Server 6.5 and SQL Server 4.2 databases, see the compatibility information provided in the Microsoft SQL Server Transact-SQL Reference.

See Also

Upgrading from SQL Server 4.2


Keywords

The following are SQL Server keywords. Keywords new for SQL Server 6.5 are in bold type.

ADD	EXIT	PRIVILEGES
ALL	FETCH	PROC
ALTER	FILLFACTOR	PROCEDURE
AND	FLOPPY	PROCESSEXIT
ANY	FOR	PUBLIC
AS	FOREIGN	RAISERROR
ASC	FROM	READ
AUTHORIZATION	FULL	READTEXT
AVG	GOTO	RECONFIGURE
BEGIN	GRANT	REFERENCES
BETWEEN	GROUP	REPEATABLE
BREAK	HAVING	REPLICATION
BROWSE	HOLDLOCK	RESTRICT
BULK	IDENTITY	RETURN
BY	IDENTITY_INSERT	REVOKE
CASCADE	IDENTITYCOL	RIGHT
CASE	IF	ROLLBACK
CHECK	IN	ROWCOUNT
CHECKPOINT	INDEX	RULE
CLOSE	INNER	SAVE
CLUSTERED	INSENSITIVE	SCHEMA
COALESCE	INSERT	SCROLL
COMMIT	INTERSECT	SELECT
COMMITTED	INTO	SERIALIZABLE
COMPUTE	IS	SESSION_USER
CONFIRM	ISOLATION	SET
CONSTRAINT	JOIN	SETUSER
CONTINUE	KEY	SHUTDOWN
CONTROLROW	KILL	SOME
CONVERT	LEFT	STATISTICS
COUNT	LEVEL	SUM
CREATE	LIKE	SYSTEM_USER
CROSS	LINENO	TABLE
CURRENT	LOAD	TAPE
CURRENT_DATE	MAX	TEMP
CURRENT_TIME	MIN	TEMPORARY
CURRENT_TIMESTAMP	MIRROREXIT	TEXTSIZE
CURRENT_USER	NOCHECK	THEN
CURSOR	NONCLUSTERED	TO
DATABASE	NOT	TRAN
DBCC	NULL	TRANSACTION
DEALLOCATE	NULLIF	TRIGGER
DECLARE	OF	TRUNCATE
DEFAULT	OFF	TSEQUAL
DELETE	OFFSETS	UNCOMMITTED
DESC	ON	UNION
DISK	ONCE	UNIQUE
DISTINCT	ONLY	UPDATE
DISTRIBUTED	OPEN	UPDATETEXT
DOUBLE	OPTION	USE
DROP	OR	USER
DUMMY	ORDER	VALUES
DUMP	OUTER	VARYING
ELSE	OVER	VIEW
END	PERM	WAITFOR
ERRLVL	PERMANENT	WHEN
ERROREXIT	PIPE	WHERE
ESCAPE	PLAN	WHILE
EXCEPT	PRECISION	WITH
EXEC	PREPARE	WORK
EXECUTE	PRIMARY	WRITETEXT
EXISTS	PRINT
For more information about keywords see the Microsoft SQL Server Transact-SQL Reference.

See Also

Running the CHKUPG65.EXE Utility

Reserved Words


Reserved Words

The following are reserved words. Reserved words are compatible with SQL Server 6.5 but can be expected to cause conflicts in the future.

ABSOLUTE	EXTERNAL	OVERLAPS
ACTION	EXTRACT	PAD
ALLOCATE	FALSE	PARTIAL
ARE	FILE	POSITION
ASSERTION	FIRST	PRESERVE
AT	FULL	PRIOR
BOTH	GET	RELATIVE
CASCADED	GLOBAL	RETAINDAYS
CAST	HOUR	RIGHT
CATALOG	IMMEDIATE	ROWS
CHAR_LENGTH	INITIALLY	SECOND
CHARACTER	INNER	SESSION
CHARACTER_LENGTH	INPUT	SIZE
COLLATE	INTERVAL	SPACE
COLLATION	JOIN	SQLSTATE
COLUMN	LAST	TIME
CONNECT	LEADING	TIMESTAMP
CONNECTION	LEFT	TIMEZONE_HOUR
CONSTRAINTS	LOCAL	TIMEZONE_MINUTE
CORRESPONDING	MATCH	TRAILING
DATE	MINUTE	TRANSLATE
DAY	MONTH	TRANSLATION
DEFERRABLE	NAMES	TRUE
DEFERRED	NATIONAL	UNKNOWN
DESCRIBE	NATURAL	USAGE
DESCRIPTOR	NCHAR	USING
DIAGNOSTICS	NEXT	VALUE
DISCONNECT	NO	VOLUME
DOMAIN	OCTET_LENGTH	WRITE
END_EXEC	OUTER	YEAR
EXCEPTION	OUTPUT	ZONE
EXPIREDATE
For more information about keywords and reserved words see the Microsoft SQL Server Transact-SQL Reference.

See Also

Running the CHKUPG65.EXE Utility

Keywords

Help Contents


Sort Orders

A sort order is a set of rules that determines how SQL Server collates and presents data in response to database queries. The sort order determines the order in which data is presented in response to SQL Server statements that use GROUP BY, ORDER BY, and DISTINCT. The sort order also determines how certain queries are resolved, such as queries that use WHERE and DISTINCT.

Important: You must select the correct sort order when you install SQL Server. If you need to change sort orders after you have installed SQL Server, you must rebuild the databases and reload the data.

SQL Server offers several sort orders. The default is dictionary order, case-insensitive.

 Binary order

 Dictionary order, case-sensitive

 Dictionary order, case-insensitive

 Dictionary order, case-insensitive, uppercase preference

 Dictionary order, case-insensitive, accent-insensitive

 Strict compatibility with version 1.x case-insensitive databases

 Alternate sort orders

 Scandinavian sort orders

 Custom

Note  Additional character sets and sort orders are being developed for international users and may be included in those listed by the setup program.

See Also

Installing SQL Server

Rebuilding the Master Database


Client Utilities

Microsoft SQL Server includes several client utilities used for specific database and network tasks. The client utilities are always installed on the server during a new installation, but they can also be installed on a Windows NT-based workstation independent of the server software.

When you install the client software independent of the server software, setup always installs the client support libraries, such as DB-Library. Other utilities, however, are optional. The optional utilities are:

 BCP

 ISQL and ISQL/w

 SQL Enterprise Manager

 SQL Security Manager

 Configuration Diagnostics

Note  When a new installation is performed, SQL Administrator, SQL Object Manager, and SQL Tape Utility are no longer installed, because SQL Enterprise Manager makes those tools unnecessary.

When an existing SQL Server installation is upgraded, setup removes the SQL Tape Utility but leaves SQL Administrator and SQL Object Manager in place and automatically runs upgrade scripts (OBJECT60.SQL and ADMIN60.SQL) that make that SQL Server compatible with the existing SQL Administrator and SQL Object Manager utilities.

See Also

Installing or Upgrading 32-bit Client Software


BCP

The bcp utility is used to copy data to or from an operating-system file.


ISQL/w

Both versions of the isql utility (isql and ISQL/w) can be installed. They are used to enter Transact-SQL commands and procedures.


SQL Enterprise Manager

SQL Enterprise Manager is a new graphical application that supports enterprise-wide system administration. SQL Enterprise Manager allows for easy configuration and management of SQL Server and SQL Server objects. It provides a powerful scheduling engine, administrator alert capability, drag-and-drop control of data migration and other operations across multiple servers, and a built-in interface for replication.


SQL Security Manager

SQL Security Manager is used to manage user accounts for SQL Servers by using security integration with Windows NT.


Configuration Diagnostics

There are three configuration diagnostics utilities. The SQL Server application in the Windows NT Control Panel is used to determine which version of DB-Library is installed on a client and to set up SQL Server connection information on a client. The makepipe and readpipe utilities are used to test if network named pipes are working.


SQL Transfer Manager

SQL Transfer Manager provides an easy, graphical way to transfer the objects and data from a Microsoft-based SQL Server or a non-Microsoft-based SQL Server to a Windows NT-based Microsoft SQL Server. (For example, transferring data from Microsoft SQL Server installed on an Intel-based computer to Microsoft SQL Server installed on a different processor architecture.)

You can also use SQL Transfer Manager to transfer data from a server with one sort order to a server with a different sort order.


Network Support

Microsoft SQL Server uses network libraries known as Net-Libraries to pass network packets back and forth between clients and a SQL Server. The Net-Libraries, implemented as dynamic-link libraries (DLLs), perform the network operations required to communicate by using a specific protocol. SQL Server includes a set of server Net-Libraries that enable simultaneous connections from clients running named pipes or other interprocess communication (IPC) mechanisms.

By default, SQL Server is configured to support named pipes connections and uses \\.\\pipe\sql\query as the default named pipe.

You cannot change Net-Library configurations during an upgrade. The existing Net-Library configurations are carried over and can be modified after upgrade by using SQL Setup from the Microsoft SQL Server 6.5 program group.

 NWLink IPX/SPX

 TCP/IP Sockets

 Banyan VINES

 AppleTalk ADSP

 DECnet

 Multi-Protocol

 User provided

See Also

Changing Network Support


ODBC Support

The SQL Server 6.5 setup program automatically installs the ODBC SQL Server driver and adds the ODBC Driver Manager as an application in Control Panel for Windows NT-based computers.


Server Installation Paths

The default SQL Server root directory is C:\MSSQL, although during installation the setup program allows you to change the root directory. The directory name must conform to the FAT 8.3 naming convention, even if the directory is installed on an NTFS volume. Specifically, do not use spaces in the directory name.

The following list shows the directories created under the SQL Server root directory during installation:

Directory	Contains
BIN	MS-DOS-  and Windows-based client executable files and Windows dynamic-link library (DLL) files
BINN	Windows NT-based client and server executable files, and online Help files
CHARSETS	Character set and sort order files
DATA	Database devices
DLL	Dynamic-link library files
INSTALL	Installation scripts and output files
LOG	Error log files
REPLDATA	Used by replication as the working directory for the distribution database
SAMPLES	Sample files
SYMBOLS	Files and libraries that can be used to generate stack dumps and traces on computers running Windows NT 3.51 or later versions


Client Installation Paths

The default SQL Server client root directory is C:\MSSQL, although during installation the setup program allows you to change the root directory. The directory name must conform to the FAT 8.3 naming convention, even if the directory is installed on an NTFS volume. Specifically, do not use spaces in the directory name.

The following table lists the directories created under the root directory during the installation of client utilities.

Directory	Contains
BIN	MS-DOS- and Windows-based client executable files, and Windows dynamic-link library (DLL) files
BINN	Windows NT-based client executable files
DLL	Dynamic-link library files
HELP	Help files


Languages

Microsoft SQL Server is available in both United States English and localized versions. All versions include system messages in United States English. Localized versions also include system messages that have been translated into another language.

When you install a localized version of SQL Server, the setup program automatically installs the localized messages and date/time formats. If you have more than one alternate language, use the setup program to install the localized messages and date/time formats for each language. The setup program lets you determine the default language. DBLibrarybased applications use the country settings established by using the International application in the Windows NT Control Panel.

To add an additional language, run setup and choose the Add Language option. It is not necessary to perform a full installation. To find out which languages have been installed, use the sp_helplanguage system procedure.

To change the default language for SQL Server, use the SET LANGUAGE statement. To set the default language for a specific user, use the sp_defaultlanguage system procedure.

See Also

Adding a Language


The MASTER Device

When you install Microsoft SQL Server, the setup program creates the MASTER device, which is used to store the master, model, and tempdb system databases and transaction logs, and the pubs sample database (optional). The default location of the MASTER device is C:\MSSQL\DATA\MASTER.DAT, but you can change the location as appropriate.

The default (and minimum) MASTER device size is 25 MB. If you have sufficient disk space, consider making the MASTER device even larger (this can save you time later if your need for space grows).

See Also

Rebuilding the Master Database


Remote Setup

You can use the SQL Server setup program to install the software on a remote computer. When you install the software on a remote computer, the setup program prompts you for the following:

 Remote Server Name

 SQL Installation Drive

 Windows NT Installation Drive

 Master Database Installation Drive

 Remote Logical Drive

After you have installed the software on the remote computer, you can use the SQL Service Manager to start and stop the remote SQL Server.


Books Online

During installation or upgrade, the setup program gives you the option of installing the SQL Server Books Online and adding the Books Online icon to the SQL Server 6.5 program group. By choosing this icon you can access SQL Server documentation.

You have the choice of installing SQL Server Books Online to run from the hard disk or to run from the CD. You can also choose not to install Books Online.

If you install SQL Server Books Online to run from the hard disk, approximately 15 MB of available hard disk space is required. If you install SQL Server Books Online to run from the CD, approximately 1 MB of available hard disk space is required to install the Browser (the EXE and DLL files necessary to run Books Online).


Choose Licensing Mode

From the Choose Licensing Mode dialog box, select a licensing mode and then choose Continue.

Microsoft SQL Server 6.5 (a Microsoft Back Office server product) requires a Server License and a Client Access License for each client computer that accesses the server. You must acquire these licenses before using the product. A Server License is provided with the server software. Client Access Licenses are purchased separately.

Client Access Licenses can be used in one of two licensing modes. The choice of modes offers you the flexibility to choose the option that best meets your needs:

Per Seat. Each computer or workstation that will be accessing or otherwise using any SQL Server (by using either Microsoft-provided client software or third-party software) requires a Client Access License.

Per Server. You specify a maximum number of simultaneous user connections for the server. An equal number of Client Access Licenses are required for that server.

During installation of a server, you must choose between these two licensing modes. Before the setup program can proceed, you must make your selection and then accept the terms of the license agreement.

If you are unsure which licensing mode to choose, select the Per Server option. After installation of a server, you are permitted to convert from Per Server mode to Per Seat mode at no additional cost. This is a one-time, one-way conversion option. It is not necessary to notify Microsoft if you elect to make this change. To change licensing mode to Per Seat after installation, use the Licensing application in Control Panel. For more information, see the online Help for the Licensing application.

You are not legally permitted to change the licensing mode from Per Seat to Per Server.

To review the licensing agreement, see the Client License Access Agreement or the online Help for the Licensing application in Control Panel.

See Also

Server License for Microsoft Server Products

Node-based Client Access

Increasing Client Access Licenses After Server Installation


Per Seat Mode

Under the Per Seat licensing mode, each client computer requires a Client Access License to connect to any Microsoft SQL Server 6.5 computer for data access purposes. Once a client computer is licensed, it may be used to access any Microsoft SQL Server computer at no additional charge.

If you select the Per Seat licensing mode, any number of licensed computers can be used to connect at the same time to any Microsoft SQL Server. You must purchase a separate Client Access License for each computer even if you use client data access software from Microsoft, from a third-party vendor, or from any other client software supported by Windows NT Server.

The Per Seat option is often the most economical one for networks in which clients tend to connect to more than one server.

To review the Per Seat licensing agreement, see the Client License Access Agreement or the online Help for the Licensing application in Control Panel.


Per Server Mode

Under the Per Server licensing mode, each Client Access License is assigned to a particular database server and allows one client to connect to that server for data access. You must have at least as many Client Access Licenses dedicated to that server as the maximum number of client computers that are connected to that server at one time.

If you select the Per Server option, during server installation you will specify the number of Client Access Licenses (corresponding to the maximum number of concurrent client connections) that you have purchased for that server.

Note  When a server reaches the maximum number of concurrent connections, Microsoft SQL Server 6.5 displays an error message and will not allow another computer to connect until at least one currently connected client disconnects.

This mode of licensing is available for Microsoft SQL Server 4.21a or later. The Per Server option is often the most economical one for networks in which clients tend to connect to only one occasional-use or special-purpose server.

To review the Per Server licensing agreement, see the Client License Access Agreement or the online Help for the Licensing application in Control Panel.


Node-based Client Access

Node-based client access permits all data access connections originating from a single client (one unique workstation and/or computer) to be counted against a single Client Access License. Both client licensing modes provide support for node-based client access.

Beginning with version 6.5, Microsoft SQL Server client access software supports this model. This capability is available for both ODBC and DB-Library and allows Microsoft SQL Server 6.5 to automatically detect multiple data access connections originating from the same networked client. When this occurs, those connections are then counted against a single Client Access License. Application coding changes are not required to take advantage of this new node-based client access capability.

When counting Client Access Licenses, SQL Server takes advantage of this new data access client capability whenever possible. However, there are two client configurations in which clients will be counted on a per individual connection basis:

Earlier versions of client access software

Because these clients do not support node-based data access, SQL Server cannot detect multiple connections originating from the same node. Each connection counts as one client.

Non-Microsoft client access software

Data access software from other vendors may not support node-based data access. If it does not, each connection counts as one client.


Increasing Client Access Licenses After Server Installation

Client Access Licenses can be added at any time.

If a SQL Server is licensed by using the Per Server mode, after you purchase the additional licenses they must be applied to that server. Use the Licensing application in Control Panel to increase the number of users to equal the total number of Client Access Licenses purchased for that server.


Per Seat Licensing

With per seat licensing, each computer or workstation that will be accessing or otherwise using any SQL Server (using either Microsoft-provided client software or third-party software) requires a Client Access License.

Microsoft License Agreements

Server License for Microsoft Server Products

See Also

Choose Licensing Mode


Per Server Licensing

With per server licensing, you specify a maximum number of simultaneous user connections for the server. An equal number of Client Access Licenses are required for that server.

Microsoft License Agreements

Server License for Microsoft Server Products

See Also

Choose Licensing Mode


Enter Name and Organization

Use this dialog box to register this copy of SQL Server.

 Name

 Company

 Product ID


Name

Enter your name, or the name of a user who is responsible for using or administering this server. This entry is required.


Company

Enter the name of your company or other organization. This entry is optional.


Product ID

This is an identifier provided on the software's CD box. Although this is an optional entry, it is recommended that you enter the product ID, because it is used for product support purposes.


Verify Name and Organization

Review your entries for Name, Organization, and Product ID.

To accept the entries

Choose Continue.

To change an entry

Choose Change.


Options

Use the Options dialog box to select one of the SQL Server setup options. For more information, choose one of the following buttons.

 Install SQL Server and Utilities

 Upgrade SQL Server

 Install Utilities Only

 Change Network Support

 Add Language

 Rebuild Master Database

 Set Server Options

 Set Security Options

 Remove SQL Server

 Continue Button

 Remote Button

 Exit Button

See Also

Installing

Running the CHKUPG65.EXE Utility

Upgrading

Remote Setup


Set Server Options

Select this option to change SQL Server installation options.


Set Security Options

Select this option to set or change the SQL Server security options: login security mode, login auditing options, and login mappings.


Continue Button

Accepts the current selections or values in this dialog box and proceeds to the next step.


OK Button

Accepts the current selections or values in this dialog box and proceeds to the next step.


Back Button

Discards changes to any selections or values in this dialog box and returns to the previous settings.


Exit Button

Cancels the installation, upgrade, or reconfiguration and exits the setup program.


Install SQL Server and Utilities

Select this option to install all the SQL Server software, including the client utilities. This option is not available for upgrades from SQL Server 6.0.


Upgrade SQL Server

Select this option to upgrade SQL Server to the current version.

SQL Server 4.2 and SQL Server 6.0 systems can be upgraded to SQL Server 6.5. Upgrades from SQL Server version 1.x are not supported. Because of improvements to the system (such as new system tables and datatypes), an upgrade from SQL Server 4.2 or SQL Server 6.0 to SQL Server 6.5 cannot be reversed. You can install SQL Server 6.5 alongside SQL Server 4.2, but SQL Server 6.0 can be updated only.

Back up all databases (including the master database) before upgrading Microsoft SQL Server. Also run CHKUPG65.EXE, review its report, and take any action the report indicates is necessary to prepare the existing installation for an upgrade.


Install Utilities Only

Select this option to install client utilities. This option is not available for upgrades from SQL Server 6.0.


Change Network Support

Select this option to change the server Net-Library configuration. If you are running SQL Server using the Windows NT Integrated security mode, you cannot change network support options. If you need to add an additional network, you must first reset the security mode to Standard or Mixed.


Add Language

Select this option to install an alternate language.


Rebuild Master Database

Select this option to rebuild the master database. When necessary, this option can also be used to change the character set and sort order.


Remove SQL Server

Select this option to remove the SQL Server directory tree from the hard disk and to remove all SQL Server entries from the Windows NT Registry.


Remote

Choose this button to display a dialog box used to enter information about the remote computer on which to install the software (for remote installations only).


Installation Options

Use the Installation Options dialog box to configure the listed installation options. For more information, choose one of the following buttons.

 Sets button

 Orders button

 Networks button

 Auto Start SQL Server at boot time

 Auto Start SQL Executive at boot time

See Also

Installing


Sets

Choose this button to display a dialog box used to change the default character set. The default character set is ISO.


Orders

Choose this button to display a dialog box used to change the default sort order. The default sort order is dictionary order, case-insensitive.


Networks

Choose this button to display a dialog box used to select which server Net-Libraries to install.


Auto Start SQL Server at boot time

Select this option if you want SQL Server to start automatically whenever you start (boot) the server computer.


Auto Start SQL Executive at boot time

Select this option if you want SQL Executive to start automatically whenever you start (boot) the server computer.


Character Sets

Use the Character Sets dialog box to choose which character set to install. The default character set is ISO. It is critical that you select the correct character set when you first install SQL Server. If you need to change character sets after you've installed SQL Server, you must rebuild the databases and reload the data.

For more information, choose one of the following buttons.

 ISO Character Set (Default)

 850 Multilingual

 437 US English

 932 Japanese

 936 Chinese (simplified)

 949 Korean

 950 Chinese (traditional)

 1250 Central European

 1251 Cyrillic

 1253 Greek

 1254 Turkish

 1255 Hebrew

 1256 Arabic

 1257 Baltic

 Custom

Note  Additional character sets and sort orders are being developed for international users and may be included in those listed by the setup program.

When upgrading an earlier SQL Server installation, setup installs the new program files but does not change the installed character set.

See Also

Installing SQL Server

Rebuilding the Master Database

Help Contents


Character Set

The selected character set determines the types of characters that SQL Server recognizes in the databases. A character set is a set of 256 letters, numbers, and symbols specific to a country or a language. The printable characters of the first 128 values are the same for all character sets. The last 128 characters, sometimes referred to as extended characters, are different.

You must use the same character set for both the client and the server or your results might be unpredictable. However, if your databases use only the first 128 characters of a character set (for example, if you do not use characters with diacritical marks), it makes no difference which character set you use because the first 128 characters are the same for all character sets.


ISO Character Set (Default)

Select this option to install the ISO 8859-1 character set. This is the default character set. It is  compatible with the ANSI characters used by the Microsoft Windows and Windows NT operating systems.

ISO 8859-1 is also known as the Latin 1 or the ANSI character set. It is the default character set. It is compatible with the ANSI characters used by the Windows NT and Windows operating systems.

The ISO 8859-1 character set might be appropriate if you intend to use Windows NT- and Windows-based clients exclusively, or if you need to maintain exact compatibility with a SQL Server environment for UNIX or VMS.


850 Multilingual

Select this option to install code page 850. This character set includes all characters for most languages of European, North American, and South American countries. Use this character set when you have MS-DOS-based client applications that use extended characters.


437 US English

Select this option to install code page 437, the United States English character set. This character set includes many graphics characters not usually stored in databases.

Code page 437 is the most commonly used character set in the United States. If you have character-based applications that depend upon extended characters for graphics, use this character set. Otherwise, use ISO 8859-1, which provides more compatibility with languages other than United States English.

You can find out if you need to use code page 437 for specific applications by changing the Windows NT configuration to use ISO 8859-1 and then running the application. If the application looks the way you expect it to, use ISO 8859-1. If the application looks unusual, use code page 437. For information about setting the code page in your Windows NT configuration, see the Windows NT documentation.


932 Japanese

Select this option to install code page 932, the Japanese character set. This character set includes all characters for most languages of Japan. Use this character set when you have MS-DOS-based client applications that use extended characters.


936 Chinese (simplified)

Select this option to install code page 936, the simplified Chinese character set. For traditional Chinese, use character set 950. Use this character set when you have MS-DOS-based client applications that use extended characters. This character set includes all characters for PRC and Singapore Chinese.


949 Korean

Select this option to install code page 949, the Korean character set. This character set includes all characters for most languages of Korea. Use this character set when you have MS-DOS-based client applications that use extended characters.


950 Chinese (traditional)

Select this option to install code page 950, the traditional Chinese character set. This character set includes all characters for Taiwan and Hong Kong Chinese. Use this character set when you have MS-DOS-based client applications that use extended characters. For simplified Chinese, use character set 936.


1250 Central European

Select this option to install code page 1250, the Central European character set.


1251 Cyrillic

Select this option to install code page 1251, the Cyrillic character set.


1253 Greek

Select this option to install code page 1253, the Greek character set.


1254 Turkish

Select this option to install code page 1254, the Turkish character set.


1255 Hebrew

Select this option to install code page 1255, the Hebrew character set.


1256 Arabic

Select this option to install code page 1256, the Arabic character set.


1257 Baltic

Select this option to install code page 1257, the Baltic character set.


Select Sort Orders

Use the Select Sort Orders dialog box to choose which sort order to install. The default is dictionary order, case-insensitive. For more information, choose one of the following buttons.

 Dictionary order, case-insensitive

 Binary order

 Dictionary order, case-sensitive

 Dictionary order, case-insensitive, uppercase preference

 Dictionary order, case-insensitive, accent-insensitive

 Strict compatibility with version 1.x case-insensitive databases

 Alternate sort orders

 Scandinavian sort orders

 Custom

Note  Additional character sets and sort orders are being developed for international users and may be included in those listed by the setup program.


Sort Order

A sort order is a set of rules that determines how SQL Server collates and presents data in response to database queries. The sort order determines the order in which data is presented in response to SQL Server statements involving GROUP BY, ORDER BY, and DISTINCT. The sort order also determines how certain queries are resolved, such as queries involving WHERE and DISTINCT.


Binary order

Binary is the simplest and fastest sort order option. The collating sequence for this sort order is based on the numeric value (0 through 255) of the characters in the installed character set. Using the binary sort order, ZYXWV sorts before abcde because the character Z precedes the character a in all character sets. Sorting for extended characters (such as characters with diacritical marks) depends on the installed character set.

If you want the data to sort in a more conventional order, choose one of the dictionary sort orders. Remember, however, that dictionary sort orders come with a tradeoff in performance.


Dictionary order, case-sensitive

With this sort order, uppercase and lowercase characters are treated as not equivalent, and characters with diacritical marks are treated as unique from all other characters (including their corresponding uppercase or lowercase characters).

Uppercase characters are sorted before their corresponding lowercase characters. Uppercase characters with diacritical marks are sorted before their corresponding lowercase characters. Characters with diacritical marks are sorted after characters without diacritical marks. Characters with diacritical marks are sorted in the order they appear in the character set.


Dictionary order, case-insensitive

This is the default sort order. Uppercase and lowercase characters are treated as equivalent, and characters with diacritical marks are treated as unique from all other characters (except their corresponding uppercase or lowercase characters).

Uppercase characters are not given sorting preference over their corresponding lowercase characters (they can appear before or after them). Uppercase characters with diacritical marks are not given sorting preference over their corresponding lowercase characters (they can appear before or after them). Characters with diacritical marks are sorted after characters without diacritical marks. Characters with diacritical marks are sorted in the order they appear in the character set.


Dictionary order, case-insensitive, uppercase preference

With this sort order, characters with diacritical marks are treated as unique from all other characters (except their corresponding uppercase or lowercase characters).

Uppercase characters are sorted before their corresponding lowercase characters. Uppercase characters with diacritical marks are sorted before their corresponding lowercase characters. Characters with diacritical marks are sorted after characters without diacritical marks. Characters with diacritical marks are sorted in the order they appear in the character set.


Dictionary order, case-insensitive, accent-insensitive

With this sort order, uppercase and lowercase characters are treated as equivalent, and characters with diacritical marks are treated as equal to their counterparts without diacritical marks.

Lowercase characters are paired with their corresponding uppercase characters (for example, a and A) and are sorted before any corresponding uppercase character with a diacritical mark (for example, Ä).


Strict compatibility with version 1.x case-insensitive databases

This sort order applies only to code page 850. It is provided for strict compatibility with SQL Server version 1.x case-insensitive databases. It uses dictionary sort order with case insensitivity and no uppercase preference for the first 128 characters of the character set and Binary sort order for the remaining 128 characters. Using this sort order choice, A and a are sorted and grouped together, but à and Ä are sorted as unique characters according to their binary values in the installed character set.

This option offers no advantage over other sort orders other than strict compatibility with earlier releases of SQL Server. Unless you have case-insensitive databases set up for earlier releases of SQL Server that use extended characters and you require the upgraded version to have exactly the same, less functional, sort order semantics, you should choose another sort order.


Alternate sort orders

Alternate sort orders differ from the other sort orders as follows:

For the case-sensitive option, all uppercase variants of a character are sorted before any equivalent lowercase variants. (This is in contrast to the standard case-sensitive option in which the uppercase and lowercase pairings are maintained for each distinct character.)

Ø and the ø sort at the end of the character set.

Ñ is sorted distinctly from N.


Scandinavian sort orders

The Scandinavian sort orders differ from the other sort orders because the extended characters (Ø, Å, Ä, and Ö) are sorted after Z.


Custom

SQL Server can install custom sort orders from files as they become available. By convention, a sort order definition file uses the extension .SRT, but it is allowed to have any legal filename.

Select this option to install a custom sort order from a definition file that you provide.


Select Network Protocols

Use the Select Network Protocols Networks dialog box to choose which Net-Libraries to install on the server. For more information, choose one of the following buttons.

 Named Pipes

 Multi-Protocol

 NWLink IPX/SPX

 TCP/IP Sockets

 AppleTalk ADSP

 Banyan VINES

 DECnet

 User provided


Net-Libraries

Microsoft SQL Server uses network libraries, known as Net-Libraries, to pass network packets back and forth between clients and SQL Server. The Net-Libraries, implemented as dynamic-link libraries (DLLs), perform the network operations required to communicate by using a specific protocol.

SQL Server includes a set of server Net-Libraries that enable simultaneous connections from clients running named pipes or other interprocess communication (IPC) mechanisms. The default sets up SQL Server to listen on named pipes.


Named Pipes

Named pipes are the default Net-Library installed by setup. The default named pipe name is \\.\pipe\sql\query.

Note  The setup program uses named pipes connections during installation or upgrade. Do not deselect the Named Pipes option during an installation or an upgrade. If you want to disable Named Pipes on a server, do so by running setup from the Microsoft SQL Server 6.5 program group after completion of the installation or upgrade.


Multi-Protocol

The Multi-Protocol Net-Library takes advantage of the powerful remote procedure call (RPC) facility of Windows NT. Unlike other Net-Libraries, Multi-Protocol Net-Library need only be selected as an option from the Select Network Protocols dialog box; it does not require the entry of any configuration parameters. The Multi-Protocol Net-Library:

Communicates over most IPC mechanisms supported by Windows NT. (Note that for SQL Server 6.5, only TCP/IP Windows Sockets, NWLink IPX/SPX, and Named Pipes are tested and supported.)

Allows the use of integrated security over all protocols that RPC supports (including Novell Windows-based clients using SPX or IPXODI).

Supports encryption for both user password authentication and data.

Offers performance comparable to native IPC Net-Libraries for most applications.


NWLink IPX/SPX

This Net-Library allows SQL Server to communicate by using the NWLink IPX/SPX protocol.

If you set up SQL Server to listen on NWLink IPX/SPX, the setup program prompts you for the service name in which to register SQL Server on the Novell network. The default service name is the computer name of the server computer.


TCP/IP Sockets

This Net-Library allows SQL Server to communicate by using standard Windows Sockets as the IPC method across the TCP/IP protocol.


AppleTalk ADSP

For Intel-, MIPS-, and Alpha AXP-based computers, server-side AppleTalk (ADSP) Net-Libraries are provided for use with Microsoft SQL Server. The server-side AppleTalk Net-Library allows Apple Macintosh-based clients to connect to SQL Server by using native AppleTalk (as opposed to TCP/IP).


Banyan VINES

SQL Server supports Banyan VINES Sequenced Packet Protocol (SPP) as the IPC method across Banyan VINES IP network protocol. Banyan VINES support for Windows NT-based clients and servers is available only for SQL Server on the Intel platform; it is not currently available on the MIPS or Alpha AXP platforms.

Note  Before you can configure SQL Server to listen on Banyan VINES, you must install the Banyan VINES software (available from Banyan).


DECnet

For Intel-, MIPS-, and Alpha AXP-based computers, server-side DECnet sockets Net-Libraries provide connectivity with Pathworks networks by allowing clients running on VMS to connect to Microsoft SQL Server via DECnet sockets.


User provided

SQL Server permits the installation and use of user-provided Net-Libraries.

Note  The user provided choice is not available when performing a new SQL Server installation. It is only available when running setup to modify the configuration of an existing installation.


Named Pipe Name

By default, a SQL Server listens on the \\.\sql\query named pipe. You can change this option. To specify an alternate named pipe for a server to listen on, in the Named Pipe Name box, type the new name (for example, \\.\mssql\query), then choose the Continue button.

Note  If you change the named pipe a server listens on, clients that connect to the server using named pipes must also be set up to connect by using the server name and the new pipe name.


Multi-Protocol Encryption

The Multi-Protocol Net-Library supports optional encryption for both data exchange and user password authentication when communicating over trusted (integrated security) connections. Encryption can be either set at each client or enforced for all clients by the server. Server-enforced encryption automatically encrypts all communication between clients by using the client-side Multi-Protocol Net-Library and the server listening on the server-side Multi-Protocol Net-Library.

To configure the server to enforce encryption

1.	Select the Enable Encryption box.

2.	Choose the Continue button.

Server-enforced encryption is supported only by the Multi-Protocol Net-Library.

Note  If Net-Libraries for other protocols are also loaded by the server, incoming connections over those Net-Libraries will not use encryption.


TCP/IP Port Number

Type the TCP/IP port number for SQL Server to listen on when accepting connections from TCP/IP sockets clients.

If the socket_number is not specified, the Net-Library uses 1433, the official Internet Assigned Number Authority (IANA) socket number for Microsoft SQL Server.

See Also

Network Support


Novell Bindery Service Name

Type the Novell Bindery service name in which to register SQL Server on the Novell network. (The default service name is the computer name of the server computer.)

See Also

Network Support


Banyan VINES

To configure SQL Server to listen on Banyan VINES, type the StreetTalk PC-based service name in the Service Name box, and choose the Continue button.

A service name has the form servicename@group@org, where servicename is the StreetTalk PC-based service name used by SQL Server, group is the group, and org is the organization. The service name used by SQL Server must first be created by using the MSERVICE program included with your VINES software.

Note  Before you can configure SQL Server to listen on Banyan VINES, you must install the Banyan VINES software (available from Banyan).

See Also

Network Support


DECnet

Type the DECnet object ID you want SQL Server to listen on when accepting connections from clients under this Net-Library, and then choose the Continue button.

The value of the DECnet object ID is set by your System Administrator; it should not conflict with other services on the system listening on DECnet sockets. The object ID can be either numeric or alphanumeric. To specify a numeric ID, preface it with a number sign (#). For example:

#150

To specify an alphanumeric value, type the ID of your choice. For example:

SQL1

For detailed information about object IDs, see your VMS documentation.

See Also

Network Support


AppleTalk

Type the AppleTalk service object name. The AppleTalk service object name is set by your System Administrator who might want to use the machine name of the system for consistency. For example:

ACCOUNTING1

Note  It is not necessary to enter the AppleTalk zone because the local zone is used when registering the service.

See Also

Network Support


User-Provided Net-Library Destination Path

Type the full path in which to copy the user-provided Net-Library file.


Network Address

Type the network address to listen on when accepting connections from clients under the user-provided Net-Library.

See Also

Network Support


Rebuild Master Database

Use the Rebuild Master Database dialog box to rebuild the master database.

Note  Rebuild the master database only when it is absolutely necessary. Rebuilding the master database completely rewrites the master database, destroys all information added since SQL Server was first installed, and renders all other databases unusable. If you rebuild the master database, you must reload the database from the most recent dump, and then reapply any changes not included in the dump.

For more information, choose one of the following buttons.

 Sets

 Orders

See Also

The MASTER Device

Help Contents


master database

The master database is the system database that keeps track of user accounts, remote user accounts, remote servers, environment variables, system error messages, system databases, database storage allocation, devices, and active locks. The default space allocated to the master database is 15 MB.


SQL Server Installation Path

Use this dialog box to determine where the SQL Server software will be installed. For more information, choose one of the following buttons.

 Drive

 Directory


Drive

Select the drive on which to install the SQL Server software. (The default SQL Server drive is C.)


Directory

Type the name of the directory in which to install the SQL Server software. The default SQL Server root directory is \MSSQL.

If you change the default, the directory name must conform to the FAT 8.3 naming convention, even if the directory is installed on an NTFS volume. Specifically, do not use spaces in the directory name.


SQL Server Upgrade Path

Use this dialog box to specify the location of the SQL Server installation. For more information, choose one of the following buttons.

 Drive

 Directory


Drive

Select the drive on which the SQL Server software is currently installed.


Directory

Type the name of the directory in which the SQL Server software is currently installed.


SQL Server Installation Path

Use this dialog box to indicate the location of the current SQL Server installation. For more information, choose one of the following buttons.

 Drive

 Directory


MASTER Device Creation

Use the MASTER Device Creation dialog box to specify where you would like the MASTER device to be located and the size of the device. For more information, choose one of the following buttons.

 Drive

 Directory

 MASTER device size (MB)

See Also

The MASTER Device


MASTER Device

When you install SQL Server, the setup program creates the MASTER device, which stores the master, model, and tempdb system databases and transaction logs, and optionally the pubs sample database and transaction log. The default location of the MASTER device is C:\MSSQL\DATA\MASTER.DAT, although you can change the location.


Drive

Select the drive on which to install the MASTER device. The default is C.


Directory

Type the the path and filename for the MASTER device. The default is \MSSQL\DATA\MASTER.DAT.

The directory and filenames must conform to the FAT 8.3 naming convention, even if installed on an NTFS volume.


MASTER device size (MB)

This is the space to be allocated to the MASTER device. The default (and minimum) size is 25 MB.

Note  If you later determine you need additional device space, use DISK RESIZE to increase the size of the MASTER device if you have adequate disk space.


Upgrade MASTER Device Path

This dialog box is used to indicate the current location of the MASTER device so the setup program can perform any required upgrade. For more information, choose one of the following buttons.

 Drive

 Directory

See Also

The MASTER Device


Drive

Select the drive on which the MASTER device is currently installed.


Directory

Use this dialog box to specify the path and filename of the current MASTER device. For example:

\MSSQL\DATA\MASTER.DAT


Rebuild MASTER Device

Use the Rebuild Master Device dialog box to specify where you would like the rebuilt MASTER device to be located and the size of the device. For more information, choose one of the following buttons.

 Drive

 Directory

 MASTER Device Size (MB)

See Also

The MASTER Device


Install or Remove Client Utilities

Use this dialog box to install or remove the 32-bit client utilities.


Install Client Utilities

Use the Install Client Utilities dialog box to install the SQL Server client utilities on a computer running the Windows NT Workstation, Windows NT Server, or Windows 95 operating system. For more information, choose one of the following buttons.

 Drive

 Directory

 BCP

 ISQL/w

 SQL Enterprise Manager

 SQL Security Manager

 Configuration Diagnostics

 MS Query

 SQL Server Web Assistant

 MS DTC Client Support

 SQL Trace Utility


Client Utilities

Microsoft SQL Server includes several client utilities used for specific database and network tasks. Although the client utilities are always installed on the server during a new installation, they can also be installed alone on a computer running the Windows NT Workstation or Windows NT Server operating system.


Drive

Select the drive on which to install the client utilities.


Directory

Type the name of the root directory in which to install the client utilities.


BCP

Select this option to install the bcp utility used to copy data to or from an operating-system file.


ISQL/w

Select this option to install both versions of the isql utility (isql and ISQL/w) used to enter Transact-SQL commands and procedures.


SQL Enterprise Manager

Select this option to install SQL Enterprise Manager, a graphical application that supports enterprise-wide system administration. SQL Enterprise Manager allows for easy configuration and management of SQL Server and SQL Server objects. It provides a powerful scheduling engine, administrator alert capability, replication, drag-and-drop control of data migration and other operations across multiple servers, and a built-in interface for replication.


SQL Security Manager

Select this option to install SQL Security Manager, which is used to manage user accounts for SQL Servers that use security integration with Windows NT.


Configuration Diagnostics

Select this option to install the SQL Server application in the Windows NT Control Panel (used to determine which version of DB-Library is installed on a client and to set up SQL Server connection information on a client) and the makepipe and readpipe utilities (used to test if network named pipes are working).


MS Query

Select this option to install MS Query.


SQL Server Web Assistant

Select this option to install the SQL Server Web Assistant. This tool will assist you in publishing your data in an HTML 3.0 file format.


MS DTC Client Support

Select this option to install MS DTC Client Support.


SQL Trace Utility

Select this option to install the SQL Trace utility.


SQL Transfer Manager

Select this option to install the SQL Transfer Manager utility, which provides an easy, graphical way to transfer the objects and data from a Microsoft-based SQL Server or a non-Microsoft based SQL Server to a Windows NT-based Microsoft SQL Server. (For example, transferring data from Microsoft SQL Server installed on an Intel-based computer to Microsoft SQL Server installed on a different processor architecture.)

You can also use this tool to transfer data from a server with one sort order to a server with a different sort order.


Select Language

Use this dialog box to install an additional language. For more information, choose one of the following buttons.

 Language Name

 SA Password

 Default Language

See Also

Languages


Language

Microsoft SQL Server is available in both United States English and localized versions. All versions include system messages in United States English. Localized versions also include system messages that have been translated into another language .

When you install a localized version of SQL Server, the setup program automatically installs the localized messages and date/time formats. If you have more than one alternate language, you can use the setup program to install the localized messages and date/time formats for each language. The setup program lets you determine the default language. DB-Library applications use the country settings established by using the International application in the Windows NT Control Panel.


Language Name

Type the name of the language to install.


SA Password

Type the password to use when installing the language files.


Default Language

Select this option if you want the alternate language to be the default language for SQL Server.


Remote Setup

Use the Remote Setup dialog box to perform operations on a remote computer. For more information, choose one of the following buttons.

 Remote Installation

 Remote Server Name

 SQL Installation Drive

 Windows NT Installation Drive

 Master Database Installation Drive

 Remote Logical Drive


Remote Installation

To perform a remote installation, select this box. The other options become enabled.


Remote Server Name

Specifies the computer name for the remote computer (for example, WOLFHOUND).


SQL Installation Drive

The remote logical drive on which to install the SQL Server software. The default is C.

For example, to install SQL Server on the D drive of a remote computer, select the SQL Installation Drive option, and then from the Remote Logical Drive box, select D.


Windows NT Installation Drive

The Windows NT Installation Drive is the remote logical drive on which the Windows NT root is installed. This is where the setup program copies SQL Server client dynamic-link libraries (DLLs) and DLLs required only during installation. The default is the current entry in the SQL Installation Drive box.

For example, if the Windows NT root for a remote computer is on its D drive, select the Windows NT Installation Drive option, and then from the Remote Logical Drive box, select D.


Master Database Installation Drive

The remote logical drive on which to install the SQL Server master database. The default is the current entry in the SQL Installation Drive box.

For example, to install the master database on the D drive of a remote computer, select the Master Database Installation Drive option, and then from the Remote Logical Drive box, select D.


Remote Logical Drive

The Remote Logical Drive is the remote logical drive for the current selected option. This could be the SQL Server Installation Drive, the Windows NT Installation Drive, or the Master Database Installation Drive.

The default SQL Server Installation Drive is C. The default for the other options is the current setting of the SQL Server Installation Drive.


SQL Executive Log On Account

This dialog box is used to assign a user account that SQL Executive will use to log on when it is started as a Windows NT service.

Note  Windows NT passwords are case-sensitive. Be sure to enter the password by using the appropriate capital and/or lowercase characters.

For more information, choose one of the following buttons.

 Install the SQL Executive service to log on to Windows NT as

 Account

 Password

 Confirm Password

 Install to log on as LocalSystem account

 Continue Button

 Back Button

 Exit Button

See Also

Creating a User Account for SQL Executive


Install the SQL Executive service to log on to Windows NT

Installs SQL Executive to run as a service under the account specified in the Account box.

Windows NT services run in the security context of the user account to which they are assigned. Services can be assigned the computer's LocalSystem account (the default), or they can have a Windows NT user account assigned to them that was created specifically for that purpose.


Account

Enter the domain and username of the user account SQL Executive will use to log on. If the user account was created on the SQL Server computer, enter the computer name for the domain name. For example, if a user account named user07 in the SALES domain has been granted membership in the Administrators local group of the SQL Server computer, enter:

SALES\user07

You create and configure user accounts with the User Manager application (provided with Windows NT Server). The user account assigned to SQL Executive must belong to the Administrators local group on the SQL Server computer. This account should have the Password Never Expires option selected, be granted the Log On As A Service privilege, and (only for domain accounts) have all logon hours allowed.


Password

Enter the password of the user account entered in the Account box.

Note  Windows NT passwords are case-sensitive. Enter the password by using the appropriate capital and/or lowercase characters.


Confirm Password

Re-enter the exact password you entered in the Password box.

Note  Windows NT passwords are case-sensitive. Enter the password by using the appropriate capital and/or lowercase characters.


Install to log on as LocalSystem account

Select this option when you want to install SQL Executive by using the LocalSystem account. This option is appropriate to select when you do not know (or have not yet created) the user account and password SQL Executive will use. You can later use the Services application in Control Panel (or the Services command in Server Manager) to assign an appropriately configured user account to SQL Executive.

Note  If SQL Executive is assigned the LocalSystem account, it runs in the security context of that account and can be prevented from accomplishing many connectivity-related tasks, such as performing replication or other scheduled tasks that involve other servers.


SQL Server Already Installed

You have already installed SQL Server.

To upgrade or add utilities

Choose Continue.


User-Provided Net-Library Source Path

Type the full path (including the drive, directory, and filename) of the custom Net-Library file to install.

See Also

Network Support


Custom Sort Order Path

SQL Server can install custom sort orders from definition files as they become available. By convention, a sort order definition file uses the extension .SRT, but it is allowed to have any legal filename. For more information, choose one of the following buttons.

 Sort Filename

 Sort Order Number


Sort Filename

In the Sort Filename box, enter the full path to the definition file. Include the drive letter, directory, and filename.


Sort Order ID

In the Sort Order Number box, enter the sort order ID.

If a sort order ID is specified in documentation provided with the definition file, use that number. If no sort order ID is specified, use any number not currently used for a sort order. For a list of sort order IDs for the sort orders provided with SQL Server, see Microsoft SQL Server Setup.


Language Path

Type the full path (drive, path, and filename) of the language file to install.


SA Password

Type the password for the system administrator login on the SQL Server that is being upgraded.


SQL Server Books Online

You can optionally install the SQL Server Books Online. Installation adds the Books Online icon to the SQL Server 6.5 program group. By choosing the icon you can access SQL Server user documentation on your computer screen.

 Install on Hard Disk

 Install to Run from CD

 Do not Install


Install on Hard Disk

This option installs SQL Server Books Online on the hard disk in the \MSSQL\INSTALL directory.  Approximately 15 MB of available hard disk space is required to install Books Online on the hard disk.


Install to Run from CD

SQL Server Books Online can be run from the CD.

The Browser (EXE and DLL files necessary to run Books Online) will be installed on the hard disk. Approximately 1 MB of available hard disk space is required. The MVB file (which contains the text and graphics that are viewed online) will not be installed and will run from the CD.


Do not Install

This option gives you the choice not to install SQL Server Books Online.


Select Server Options

This dialog box is used to modify server options. Choose one of the following buttons for information:

 Root Directory

 Master Database Path

 Error Log Path

 Auto Start Server At Boot Time

 Auto Start Executive At Boot Time

 Auto Start Mail Client

 Windows NT Event Logging

 SQL PerfMon Integration

 Direct Response Mode

 On Demand Mode

 xp_cmdshell Impersonates Client

 Enable SNMP support

 Parameters

 Tape Support

 Mail Login


Root Directory

Type the path for the root directory containing SQL Server files.


Master Database Path

Type the directory path and filename for the MASTER device (MASTER.DAT).


Error Log Path

Type the directory path for the SQL Server error log file if you prefer to use the SQL Server error log instead of or in addition to the Windows NT event logging service. If you do not enter an Error Log Path, an error log is not written.


Auto Start Server At Boot Time

Select this option if you want SQL Server to start automatically whenever you boot the server computer.


Auto Start Executive At Boot Time

Select this option if you want SQL Executive to start automatically whenever you boot the server computer.


Auto Start Mail Client

Select this option to automatically start a mail client session whenever SQL Server is started.


Windows NT Event Logging

Select this option if you want to log SQL Server events in the Windows NT event log.

Note  If you will be setting up SQL Server alerts for this server you must select this option. For information about SQL Server alerts, see the Microsoft SQL Server Administrator's Companion.


SQL PerfMon Integration

Select this option if you want to make SQL Server performance statistics available to the Windows NT Performance Monitor.


Direct Response Mode

Select this option if you want SQL Server statistics gathering to be performed separately from SQL Server Statistics display. With this option, data is available immediately to the Performance Monitor and response time is good; however, the statistics display is one period behind the statistics retrieved.


On Demand Mode

Select this option if you want the Performance Monitor to request and wait for the latest data from SQL Server during each refresh period. With this option, you receive the latest data, but response time is better with Direct Response Mode. When using On Demand Mode, set the Performance Monitor Refresh Interval long enough to not overload SQL Server with requests.


xp_cmdshell Impersonates Client

Select this option to restrict use of xp_cmdshell to users who have administrator privileges on the Windows NT-based computer where SQL Server is running. When this option is selected, only users who have connected to SQL Server by using a trusted connection and are members of the local Administrators group on that computer are allowed to use xp_cmdshell.

By default, xp_cmdshell runs in the security context of the server. When this option is selected, the commands run by xp_cmdshell continue to execute in the server's security context.


Enabling SNMP support

Select this option to enable SNMP support.


Parameters

Choose this button to display the dialog box used to set SQL Server startup options.


Tape Support

Choose this button to display the dialog box used to set the amount of time to wait when trying to read a tape that has not been loaded in the drive.


Mail Login

Choose this button to display the dialog box used to specify your SQL Mail client configurations, such as login name and password.


Server Parameters

This dialog box is used to set startup parameters for SQL Server.

To add a parameter

1.	Delete the current parameter from the Parameter box.

2.	Type the new parameter.

3.	Choose the Add button.

4.	Choose the OK button.

To change a parameter

1.	Select the parameter from the Existing Parameters box.

2.	Edit the parameter in the Parameter box.

3.	Choose the Add button.

4.	Delete the old version of the parameter as described below.

To delete a parameter

1.	Select the parameter from the Existing Parameters box.

2.	Choose the Remove button.

3.	Choose the OK button.


Tape Support

This dialog box is used to set the amount of time to wait when trying to read a tape that has not been loaded in the drive.

Choose one of the following buttons for information about the options in this dialog box:

 Wait Indefinitely

 Try Once and Quit

 Try for x Minutes


Wait Indefinitely

Choose this box to indicate that you want to wait indefinitely when trying to read a tape that has not been loaded in the drive.


Try Once and Quit

Choose this box to indicate that you want to try once and then quit when trying to read a tape that has not been loaded in the drive.


Try for x Minutes

Choose this box and then type a number to indicate that you want to try for a specified number of minutes when trying to read a tape that has not been loaded in the drive.


Mail Login

This dialog box is used to specify your Windows NT mail client login name and password for SQL Server's SQL Mail use. In order to use SQL Server with mail enabling, SQL Server must have a valid mail client login name and password. To better identify the origin of SQL Server mail messages, it is a good idea to set up a new mail account for the SQL Server that has a descriptive name such as SQL Server Mail. If you are planning to use SQL Mail, you should first set up your Windows NT-based mail client and be sure that it works. Then you can configure SQL Server to start a SQL Mail session automatically, or you can use extended stored procedures to start SQL Mail at the command line. If you are configuring SQL Server to start a mail client session automatically, you must supply a mail login name and password. If you are starting a mail session from the command line, you can optionally supply your login name and password in this dialog box so that you do not have to type it at the command line. Note that SQL Mail will "piggyback" an existing client session of Mail, if one is running.

You should use this dialog box to change your saved password whenever you change your password in the mail client. Whether or not you choose to store your mail username and password through this dialog box, you must select the option to Copy SQL Mail Configuration from Current User Account at least once after you have successfully used the Windows NT mail client.

Choose one of the following buttons for information about options in this dialog box:

 Mail Login Name

 Mail Password

 Confirm Password

 Copy SQL Mail Configuration from Current User Account


Mail Login Name

In this dialog box, type the name you use to log in to the Windows NT-based mail client.


Mail Password

In this dialog box, type the password you use to log in to the Windows NT-based mail client. Note that if you change your Windows NT-based mail client password, you must change your password here as well.


Confirm Password

In this dialog box, retype the password you typed in the Mail Password box.


Copy SQL Mail Configuration from Current User Account

This check box ensures that the current Windows NT-based mail client configuration is used by SQL Mail. Select this check box to copy your Windows NT mail client configuration information for use by SQL Mail. When you first configure SQL Mail, select this check box. Thereafter, the check box does not need to be selected unless you have changed your Windows NT-based mail client configuration information.


Set Security Options

SQL Server provides a way to integrate SQL Server login security with Windows NT security so that authorized users do not have to maintain separate SQL Server login passwords and can bypass the login process of SQL Server. In addition, integrated security lets SQL Server applications take advantage of Windows NT security features, including encrypted passwords, password aging, domain-wide user accounts, and Windows-based user administration.

This dialog box is used to change login security configuration options.

Choose one of the following buttons for information about the options in this dialog box:

 Standard

 Windows NT Integrated

 Mixed

 Default Login

 Default Domain

 Set Hostname to User Name

 Successful Logins

 Failed Logins

 Map _

 Map $

 Map #


Standard

Standard mode is the default. In Standard mode, SQL Server manages its own login validation process for all connections (except client applications that explicitly request integrated security over the trusted connections).

Note  The server can be set up to deny client-requested trusted connections, but this will restrict applications and features that use forced trusted connections (such as SQL Enterprise Manager and replication).


Windows NT Integrated

Select this option to set the Login Security Mode to Windows NT Integrated. In this mode, SQL Server uses Windows NT authentication mechanisms for all connections. Only trusted connections are allowed into SQL Server. The login name and SQL Server password submitted in the login request from a DB-Library or Open Database Connectivity (ODBC) client application are always ignored by SQL Server. Network users who were assigned user-level privileges to SQL Server log in using their network username or the default login ID (if the network username is not found in syslogins). Network usernames that are assigned system administrator-level privilege log in as sa. With this option, only named pipe and multi-protocol clients are supported.


Mixed

Select this option to set the Login Security Mode to Mixed. In this mode, SQL Server allows both trusted and non-trusted connections. For trusted (named pipe and multi-protocol) connections, SQL Server examines the requested login name as specified by the client DB-Library or Open Database Connectivity (ODBC) application. If this login name matches the user's network username, or if the login name is null or spaces, SQL Server first tries the Windows NT Integrated login rules. If this fails, SQL Server uses the Standard rules. If the requested login name is any other value, the user must supply the correct SQL Server password, and SQL Server handles the login by using the Standard rules described above. All login requests from non-trusted connections are handled by using the Standard rules.


Default Login

Type the SQL Server login name used by an authorized user on trusted connections when the user's network username does not appear in syslogins. If this box is left blank, users without an entry for their network usernames in syslogins will be denied access to the server, even if they have been given user privileges.


Default Domain

Type the Windows NT or LAN Manager domain name that is the default for matching network usernames to SQL Server login names. Because the same network username can be defined in two different domains for two different users, and both can be authorized to access SQL Server, SQL Server must distinguish between the two names in the login process for a trusted connection. For network usernames defined in domains other than the specified default, SQL Server adds the domain name and a map character such as an underscore (_) to the network username before attempting the lookup in syslogins.


Set Hostname to User Name

Select this option if you want to replace the hostname from the client login record with the Windows NT network username for users under integrated security. If this is box is selected, for example, the network username will appear in the output of the sp_who system stored procedure.


Successful Logins

Select this option if you want to record successful login attempts along with other SQL Server log information in either the Windows NT event log or the SQL Server error log (or both), depending upon how you configure logging for your SQL Server.


Failed Logins

Select this option if you want to record failed login attempts along with other SQL Server log information in either the Windows NT event log or the SQL Server error log (or both), depending upon how you configure logging for your SQL Server.


Map _

Select which special Windows NT character should be mapped to the valid SQL Server character underscore (_). (Windows NT usernames include certain characters that are not valid in SQL Server login IDs, for example, hyphens, spaces, and periods. When you use either of the integrated security options or client-requested trusted connections, mappings let you indicate how to map these characters in SQL Server.)


Map #

Select which special Windows NT character should be mapped to the valid SQL Server character number sign (#). (Windows NT usernames include certain characters that are not valid in SQL Server login IDs, for example, hyphens, spaces, and periods. When you use either of the integrated security options or client-requested trusted connections, mappings let you indicate how to map these characters in SQL Server.)


Map $

Select which special Windows NT character should be mapped to the valid SQL Server character dollar sign ($). (Windows NT usernames include certain characters that are not valid in SQL Server login IDs, for example, hyphens, spaces, and periods. When you use either of the integrated security options or client-requested trusted connections, mappings let you indicate how to map these characters in SQL Server.)


Server Name

The server name used by SQL Server is taken from the computer's name. Before installing Microsoft SQL Server on a server computer, make sure that the server's computer name is a valid SQL identifier.

The first character can be alphabetic or an underscore (_). Characters that follow the first character can include letters, numbers, or the symbols #, $, or _. No embedded spaces are allowed.

If other characters are used in the computer name, rename the computer before installing SQL Server. For instructions on renaming computers, see your documentation for Windows NT. Also, if the renamed computer is a member of a Windows NT Server domain, contact your network administrator to have the new computer name added to the domain.


Server License for Microsoft Server Products

MICROSOFT LICENSE AGREEMENT

SERVER LICENSE for Microsoft server PRODUCTs

IMPORTANTREAD CAREFULLY: This Microsoft End-User License Agreement (EULA) is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation for the Microsoft software product identified above, which includes computer software and associated media and printed materials, and may include online or electronic documentation (SOFTWARE PRODUCT or SOFTWARE). By installing, copying, or otherwise using the SOFTWARE PRODUCT, you agree to be bound by the terms of this EULA. If you do not agree to the terms of this EULA, promptly return the unused SOFTWARE PRODUCT to the place from which you obtained it for a full refund.

MICROSOFT Software LICENSE

The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed, not sold.

1.	GRANT OF LICENSE. This Microsoft product contains some or all of the following types of software: Server Software that provides services on a computer called a server; Connector Software that enables a computer running Microsoft Exchange Server to communicate with other Servers running Microsoft Exchange Server or other electronic mail server software, and Client Software that allows a computer or workstation to access or utilize the services provided by the Server Software. Microsoft grants to you the following rights to the Server Software, the Connector Software (if provided), and the Client Software (collectively called the SOFTWARE PRODUCT):

a.	Installation. The CD or diskette(s) on which the Server Software and the Connector Software reside may contain several copies of the Server Software and the Connector Software, each of which is compatible with a different microprocessor architecture (such as the x86 architecture or various RISC architectures). You may install the Server Software and the Connector Software for use with only one of those architectures at any given time. Server Software.You may install one copy of the Server Software on a single computer (the computer running the Server Software shall be referred to as the Server). Connector Software. You may install one copy of the Connector Software on one Server running Microsoft Exchange Server. If you choose to install Connector Software on a Microsoft Exchange Server, you must also acquire a separate license or licenses to install and/or use the Connector Software on every other Microsoft Exchange Server in the same Microsoft Exchange Organization. A Microsoft Exchange Organization is the group of all Microsoft Exchange Servers with the same organization name specified during the Microsoft Exchange Server installation process for the express purpose of connecting the servers. Client Software. You may install the Client Software on any computer or workstation.

b.	Use of the Server Software. You may use one copy of the Server Software on one Server, which may be connected at any point in time to an unlimited number of workstations or computers operating on one or more networks. You must acquire a separate Client Access License to access or otherwise utilize the services of the Server, whether you use the Client Software, third-party software, or an application you develop to do so, unless otherwise noted in Section 2 of this Agreement. Each Client Access License must be dedicated to one unique computer or workstation. It permits that computer or workstation to access or utilize the services of any Server. This is known as using the Server Software in Per Seat Mode. However, you may elect to use the Server Software for Microsoft SQL Server, Windows NT Server, Microsoft Exchange Server, or SNA Server (but not Microsoft BackOffice or Systems Management Server) in Per Server Mode as defined below. If you choose Per Seat Mode, your choice is permanent. If you initially choose Per Server Mode, you have the right to change one time only to Per Seat Mode, as long as you acquire a Client Access License for each unique workstation or computer accessing or utilizing the services of a Server.

c.	Alternate Terms if You Elect to Use the Server Software for Microsoft SQL Server, Windows NT Server, Microsoft Exchange Server, or SNA Server in Per Server Mode. In Per Server Mode, the maximum number of computers or workstations that may access or otherwise utilize the services of the Server at a given point in time is equal to the number of Client Access Licenses that you have acquired and designated for use exclusively with that Server. You may access any Server running in the Per Server Mode by using any Microsoft or third-party client software, including computers or workstations licensed in Per Seat Mode, provided the additional access is within that Servers maximum licensed capacity of simultaneously connected computers or workstations. If you elect to change from Per Server Mode to Per Seat Mode, you may transfer any Client Access Licenses you acquired for use in Per Server Mode to an equal number of workstations or computers in Per Seat Mode.

d.	Use of the Connector Software. You may use the Connector Software on one Microsoft Exchange Server.

e.	Use of the Client Software. You may use the Client Software to configure and administer the Server. If you use the Client Software to access or otherwise utilize the services of the Server or for any other purpose, you must acquire a separate Client Access License unless otherwise noted in Section 2 of this Agreement.

f.	Other. TransferYou may transfer the Server Software to another computer, provided that it is removed from the computer from which it is transferred. Notice to UsersYou shall inform all users of the SOFTWARE of the terms and conditions of the EULA. Not For Resale SoftwareIf this SOFTWARE is labeled Not For Resale or NFR, your license only permits use for demonstration, test, or evaluation purposes. Academic Edition SoftwareIf this SOFTWARE is labeled Academic Edition or AE, your license only permits use in qualified educational settings. License PakIf this package is a License Pak, you may install and use additional copies of the Server Software up to the number of copies specified above as Licensed Copies. No Multiplexing or PoolingUse of software or hardware that reduces the number of users directly accessing or utilizing the Server Software (sometimes called multiplexing or pooling software or hardware) does not reduce the number of Client Access Licenses requiredthe required number of Client Access Licenses would equal the number of distinct inputs to the multiplexing or pooling software or hardware front end.

g.	Note Regarding the Use of Microsoft BackOffice. The Server Software components that make up Microsoft BackOffice may only be installed together for use on one Server and may not be separated.

2.	DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

For all SOFTWARERental. You may not rent or lease the SOFTWARE, but you may transfer the SOFTWARE and accompanying written materials on a permanent basis, provided you retain no copies and the recipient agrees to the terms of this EULA. Limitation on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation. Version LimitationThe Server Software contains a certain version number (such as version 3.5). This EULA permits you to install one copy of the Server Software with the same (or a lower) version number as the Server Software version number listed above on a single computer (for example, if the version number listed above is 3.5, you may install Server Software that contains a 3.5 or 2.0 version number, but not a 3.6 version number). TerminationWithout prejudice to any other rights, Microsoft may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the SOFTWARE PRODUCT and all of its component parts.

For Microsoft Windows NT ServerProcessor Limitation. The Server Software may be used by no more than four (4) processors of the Server at any one time (support for greater than four processors is available from authorized computer hardware vendors). Client Access. You need a separate Client Access License for Windows NT Server in order to access or otherwise utilize the following Windows NT Server basic network services: File Services (sharing and managing files and/or disk storage), Printing Services (sharing and managing printers), and Remote Access Service (accessing the server from a remote location through a communications link). You do not need a separate Client Access License for Windows NT Server to access or otherwise utilize any other Windows NT Server services, to access or run Microsoft or third-party server applications on Windows NT Server, or to otherwise use the Client Software. Note on Microsoft Windows for Workgroups or Windows 95 software. The CD on which Windows NT Server resides may contain a copy of Windows for Workgroups or Windows 95 software. Note that in order to install or use this software, you must acquire a separate Windows for Workgroups or Windows 95 license.

For Microsoft SQL ServerClient Access. You do not need a separate Client Access License for SQL Server in order to execute SQL Server-to-SQL Server remote stored procedures (also referred to as database remote procedure calls). Benchmark Testing. You may not disclose the results of any benchmark test of either the Server Software or Client Software to any third party without Microsofts prior written approval. Note regarding the use of run-time software. Microsoft hereby grants to you a limited nonexclusive, royalty-free right to reproduce and distribute those DB-Library, Net-Library, and ODBC files required for run-time execution of compiled applications (Run-Time Files) in conjunction with and as a part of your application software product that is created using the Microsoft SQL Server Server Software (Application), provided that you comply with the Distribution Requirements listed below.

For Microsoft Exchange ServerMicrosoft Exchange Server includes Microsoft Schedule+ (Schedule+), Microsoft Exchange Forms Designer (Forms Designer), and Microsoft Exchange Sample Applications (Sample Applications). Schedule+, the Forms Designer, and Sample Applications may only be installed and used in conjunction with the Microsoft Exchange Client Software. Client Access. You need to acquire a separate Client Access License for Microsoft Exchange Server in order to use Microsoft Exchange Client Software to access and otherwise utilize Microsoft Exchange Server and to access or otherwise utilize the services of any other electronic mail server software. Note regarding the use of the Forms Designer and Sample Applications. The Forms Designer and its components may only be used to create applications which utilize the services of Microsoft Exchange Server (Application). Microsoft grants you the following nonexclusive rights: (i) to reproduce and distribute the run-time modules of the Forms Designer in conjunction with your Application; (ii) to reproduce, customize and distribute the run-time modules of the Sample Applications in conjunction with your Application; and (iii) to use and modify the source code version of the Sample Applications and to reproduce and distribute the object code versions of such modifications in conjunction with your Application. Any distribution permitted under this Section must be in compliance with the Distribution Requirements listed below. For purposes of this Section, run-time modules are those files identified in the written materials accompanying Microsoft Exchange Server as required during the execution of your software product. Source Extractor, Microsoft Exchange Administrator Program, and Microsoft Mail Connector. Microsoft Exchange Server also includes Source Extractor software, for migrating data from other electronic mail software, Administrator software, and Microsoft Mail Connector software. The Source Extractor, Administrator, and Microsoft Mail Connector programs contain components which may be installed on additional machines. Microsoft grants you the additional right to modify the source code version of the Source Extractor programs. The Source Extractor programs may only be used to migrate data to Microsoft Exchange Server.

For Microsoft Internet Information Server Use. You do not need a separate Client Access License for Microsoft Internet Information Server to access or otherwise utilize the services of Microsoft Internet Information Server. The Client Software may only be used in conjunction with validly licensed copies of Microsoft operating system products. Distribution. You may freely copy and distribute the Client Software accompanying Microsoft Internet Information Server for your use or (for entities) use within your organization. Any distribution of the Client Software for use by third parties outside your organization must be approved by Microsoft. You must maintain all copyright notices on all copies of the Client Software. Transfer. You may permanently transfer all of your rights to the Client Software only in conjunction with a permanent transfer of the Server Software.

For Microsoft SNA ServerThe 3270 and 5250 terminal emulation applets and the ODBC/DRDA driver provided with SNA Server are licensed for use only by one user per licensed SNA Server. Licenses for additional users must be acquired separately.

For Microsoft Systems Management ServerYou must acquire at least one valid Server License for Microsoft SQL Server to use Systems Management Server. However, you do not need to acquire a Client Access License for Microsoft SQL Server to use the administration console or utilities provided with Systems Management Server to access or otherwise utilize the services of Microsoft SQL Server.

Distribution Requirements for Microsoft SQL Server and Microsoft Exchange Server Run-Time Files and Sample ApplicationsIf you distribute Microsoft SQL Server Run-Time Files, run-time modules for the Forms Designer or Sample Applications, or object code versions of the Sample Applications (collectively Redistributables) as provided above, you agree to: (a) distribute the Redistributables only in conjunction with and as a part of your Application; (b) not use Microsofts name, logo, or trademarks to market your Application; (c) include a valid copyright notice in your Application; (d) distribute all ODBC components specified in the README file in conjunction with your Application if your software product contains ODBC files; (e) include an end-user license agreement with your Application that grants a limited license to use the Redistributables and otherwise protects Microsofts and its suppliers intellectual property

rights in the Redistributables; and (f) indemnify, hold harmless, and defend Microsoft and its suppliers from and against any claims or lawsuits, including attorneys fees, that arise or result from the use or distribution of your Application. You shall display any patent or proprietary rights notices on each copy of your Application(s) that contains executables or run-time modules, if and as required in the documentation or other materials provided with Microsoft SQL Server, Forms Designer, or Sample Applications, or subsequently provided to you by Microsoft.

3.	UPGRADES. If the Server Software is an upgrade from another product, whether from Microsoft or another supplier, you may use or transfer the Server Software only in conjunction with that upgraded product, unless you destroy the upgraded product. If the Server Software is an upgrade of a Microsoft product, you now may use that upgraded product only in accordance with this EULA. If the Server Software is an upgrade of a component of a package of software programs that you licensed as a single product, the Server Software may be used and transferred only as part of that single product package and may not be separated for use on more than one computer.

4.	COPYRIGHT. The SOFTWARE PRODUCT is licensed, not sold. Title and copyrights in and to the SOFTWARE PRODUCT (including any images, applets, photographs, animations, video, audio, music, and text incorporated into the SOFTWARE), accompanying printed materials, and any copies you are permitted to make herein are owned by Microsoft or its suppliers and are protected by United States copyright laws and international treaty provisions. Therefore, you must treat the SOFTWARE PRODUCT like any other copyrighted material (e.g., a book or musical recording) except that you may either (a) make one copy of the SOFTWARE PRODUCT solely for backup or archival purposes, or (b) transfer the SOFTWARE PRODUCT to a single hard disk, provided you keep the original solely for backup or archival purposes. You may not copy the printed materials accompanying the SOFTWARE PRODUCT.

5.	DUAL-MEDIA SOFTWARE. You may receive the SOFTWARE PRODUCT in more than one medium. Regardless of the type or size of medium you receive, you may use only one medium that is appropriate for your single computer. You may not use or install the other medium on another computer. You may not loan, rent, lease, or otherwise transfer the other medium to another user, except as part of the permanent transfer (as provided above) of the SOFTWARE PRODUCT.

6.	EXPORT RESTRICTIONS. You agree that neither you nor your customers intend to or will, directly or indirectly, export or transmit (i) the SOFTWARE PRODUCT or related documentation and technical data, or (ii) your software product, as described in Section 2, above, developed with the Exchange Forms Designer, Sample Applications, or SQL Server Server software, or process, or service that is the direct product of the SOFTWARE PRODUCT to any country to which such export or transmission is restricted by any applicable U.S. regulation or statute, without the prior written consent, if required, of the Bureau of Export Administration of the U.S. Department of Commerce, or such other governmental entity as may have jurisdiction over such export or transmission.

LIMITED WARRANTY

LIMITED WARRANTY. Microsoft warrants that (a) the SOFTWARE PRODUCT will perform substantially in accordance with the accompanying written materials for a period of ninety (90) days from the date of receipt, and (b) any hardware accompanying the SOFTWARE PRODUCT will be free from defects in materials and workmanship under normal use and service for a period of one (1) year from the date of receipt. Any implied warranties on the SOFTWARE PRODUCT and hardware are limited to ninety (90) days and one (1) year, respectively. Some states/jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you.

CUSTOMER REMEDIES. Microsofts and its suppliers entire liability and your exclusive remedy shall be, at Microsofts option, either (a) return of the price paid, or (b) repair or replacement of the SOFTWARE PRODUCT or hardware that does not meet Microsofts Limited Warranty and which is returned to Microsoft with a copy of your receipt. This Limited Warranty is void if failure of the SOFTWARE PRODUCT or hardware has resulted from accident, abuse, or misapplication. Any replacement SOFTWARE PRODUCT or hardware will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. Outside the United States, neither these remedies nor any product support services offered by Microsoft are available without proof of purchase from an authorized non-U.S. source.

NO OTHER WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND ITS SUPPLIERS DISCLAIM ALL OTHER WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH REGARD TO THE SOFTWARE PRODUCT, THE ACCOMPANYING WRITTEN MATERIALS, AND ANY ACCOMPANYING HARDWARE. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHERS, WHICH VARY FROM STATE/ JURISDICTION TO STATE/JURISDICTION.

NO LIABILITY FOR CONSEQUENTIAL DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THIS MICROSOFT PRODUCT, EVEN IF MICROSOFT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES/ JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.

U.S. GOVERNMENT RESTRICTED RIGHTS

The SOFTWARE PRODUCT and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer SoftwareRestricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Microsoft Corporation/One Microsoft Way/Redmond, WA 98052-6399.

If you acquired this product in the United States, this Agreement is governed by the laws of the State of Washington. If you acquired this product in Canada, this Agreement is governed by the laws of the Province of Ontario, Canada. Each of the parties hereto irrevocably attorns to the jurisdiction of the courts of the Province of Ontario and further agrees to commence any litigation which may arise hereunder in the courts located in the Judicial District of York, Province of Ontario. If this product was acquired outside the United States, then local law may apply.

Should you have any questions concerning this Agreement, or if you desire to contact Microsoft for any reason, please contact the Microsoft subsidiary serving your country, or write: Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399.

Si vous avez acquis votre produit Microsoft au CANADA, la garantie limitée suivante vous concerne :

GARANTIE LIMITEE

GARANTIE LIMITEE  Microsoft garantit que (a) la performance du LOGICIEL sera substantiellement en conformité avec le(s) manuel(s) de produits qui accompagne(nt) le LOGICIEL pour une période de quatre-vingt-dix (90) jours à compter de la date de réception ; et (b) tout matériel fourni par Microsoft accompagnant le LOGICIEL sera exempt de défaut de matière première ou de vice de fabrication dans des conditions normales dutilisation et dentretien pour une période dun an à compter de la date de réception. Toute garantie implicite concernant le LOGICIEL et le matériel est limitée à quatre-vingt-dix (90) jours et un (1) an, respectivement.

RECOURS DU CLIENT  La seule obligation de Microsoft et votre recours exclusif seront, au choix de Microsoft, soit (a) le remboursement du prix payé ou (b) la réparation ou le remplacement du LOGICIEL ou du matériel qui nest pas conforme à la Garantie Limitée de Microsoft et qui est retourné à Microsoft avec une copie de votre reçu. Cette Garantie Limitée est nulle si le défaut du LOGICIEL ou du matériel est causé par un accident, un traitement abusif ou une mauvaise application. Tout LOGICIEL de remplacement sera garanti pour le reste de la période de garantie initiale ou pour trente (30) jours, selon laquelle de ces deux périodes est la plus longue.

AUCUNE AUTRE GARANTIEMICROSOFT DESAVOUE TOUTE AUTRE GARANTIE, EXPRESSE OU IMPLICITE, Y COMPRIS MAIS NE SE LIMITANT PAS AUX GARANTIES IMPLICITES DU CARACTERE ADEQUAT POUR LA COMMERCIALISATION OU UN USAGE PARTICULIER EN CE QUI CONCERNE LE LOGICIEL, LE(S) MANUEL(S) DE PRODUITS, LA DOCUMENTATION ECRITE ET TOUT MATERIEL QUI LACCOMPAGNENT. CETTE GARANTIE LIMITEE VOUS ACCORDE DES DROITS JURIDIQUES SPECIFIQUES.

PAS DOBLIGATION POUR LES DOMMAGES INDIRECTSMICROSOFT OU SES FOURNISSEURS NAURONT DOBLIGATION EN AUCUNE CIRCON-STANCE POUR TOUT AUTRE DOMMAGE QUEL QUIL SOIT (Y COMPRIS, SANS LIMITATION, LES DOMMAGES ENTRAINES PAR LA PERTE DE BENEFICES, LINTERRUPTION DES AFFAIRES, LA PERTE DINFORMATION COMMERCIALE OU TOUTE AUTRE PERTE PECUNIAIRE) DECOULANT DE LUTILISATION OU DE LIMPOSSIBILITE DUTILISATION DE CE PRODUIT MICROSOFT, ET CE, MEME SI MICROSOFT A ETE AVISE DE LA POSSIBILITE DE TELS DOMMAGES. EN TOUT CAS, LA SEULE OBLIGATION DE MICROSOFT EN VERTU DE TOUTE DISPOSITION DE CETTE CONVENTION SE LIMITERA AU MONTANT EN FAIT PAYE PAR VOUS POUR LE LOGICIEL.

La présente Convention est régie par les lois de la province dOntario, Canada. Chacune des parties à la présente reconnaît irrévocablement la compétence des tribunaux de la province dOntario et consent à instituer tout litige qui pourrait découler de la présente auprès des tribunaux situés dans le district judiciaire de York, province dOntario.

Au cas où vous auriez des questions concernant cette licence ou que vous désiriez vous mettre en rapport avec Microsoft pour quelque raison que ce soit, veuillez contacter la succursale Microsoft desservant votre pays, dont ladresse est fournie dans ce produit, ou écrire à : Microsoft Sales Information Center, One Microsoft Way, Redmond, Washington 980526399.

52910006