Remote Setup Information

You can install Microsoft® SQL Server™ on a remote computer by selecting Remote Install - install to a remote machine in the Select Install Method dialog box. To perform a remote installation, these requirements must be met:

•	Both the local and remote computers must be running Microsoft Windows NT®.

•	The local and remote computers must have the same processor type (Intel or Alpha.)

•	You must be logged on to the local computer with a user account that is an administrator on the remote computer.

This table describes the information needed for a remote installation.

Use this	To do this
Username	Specify the user account under which SQL Server Setup starts a service on the remote computer. This user account must be an administrator on the remote computer and have read access to the Setup source files directory. Do not confuse this user account with these accounts: The user account logged in to the local computer. The user account assigned in SQL Server Setup to the MSSQLServer and SQLServerAgent services. All of these user accounts are specified separately. However, you can use the same user account in each case.
Password	Specify the password for the user account.
Domain	Specify the domain name for the user account. Defaults to the domain of the user currently logged on.
Target machine	Specify the name of the remote computer.
Target path	Specify, in Universal Naming Convention (UNC) format, the directory on the remote computer where SQL Server is to be installed, for example: \\target_computer\C$\Mssql7
Setup source files	Specify, in UNC format, the directory containing the SQL Server Setup files. This defaults to the directory from which you are currently running the Setup program, for example: \\source_computer\share\SQL Server\x86\Setup
SQL Server Setup collects the information you specify in the rest of the Setup program dialog boxes into the Setup.iss file. It starts a program, Remsetup.exe, on the remote computer, and then exits. Remsetup.exe starts a remote service, copies files to the \admin$ share directory, and runs an unattended installation on the remote computer using the options specified in Setup.iss.

For more information about unattended installations, see SQL Server Books Online.


Upgrade SQL Server Beta

If you currently have the Beta 3 version of Microsoft® SQL Server™ on your computer, you can upgrade the installation to SQL Server version 7.0 rather than uninstall the Beta version and install a clean copy of SQL Server.

The benefit of upgrading from the Beta 3 version is that SQL Server retains the system and user databases, saving you the time involved in re-creating system settings and reloading data.

The benefit of uninstalling SQL Server Beta 3 and installing a clean copy of SQL Server is the time the Setup program takes to complete. Uninstalling and reinstalling is faster than running the scripts involved in the upgrade, but that time is lost if you have to re-create or reload system or user data.

If you proceed with the upgrade, SQL Server Setup prompts you for the sa password. You can select a typical, minimum, or custom installation. If you choose a custom installation, you can select which components to install. All other custom installation options are retained from the Beta 3 installation.


Upgrade SQL Server 6.x

If you have an existing Microsoft® SQL Server™ version 6.x installation, select Yes, run the SQL Server Upgrade Wizard to run the wizard automatically after SQL Server Setup has installed SQL Server 7.0.

If you do not run the SQL Server Upgrade Wizard immediately after setup, you may run it later at your convenience.


Setup Type

Installation Type

If you are installing the Enterprise, Standard, or Desktop editions of Microsoft® SQL Server™, SQL Server Setup offers three installation types:

Typical

Installs all of SQL Server using the default installation options. This installation is recommended for most users.

Compact

Installs only the minimum configuration necessary to run SQL. This installation is recommended for users who have computers with minimum available disk space.

Custom

Installs SQL Server while allowing you to change any or all of the default options. This installation is recommended for expert users.

If you run SQL Server Setup for an edition of SQL Server that is not supported on your operating system, (for example, installing SQL Server Standard Edition on Microsoft Windows 95/98,) the Setup program does not offer the choice of installation types; instead, it proceeds directly to the SQL Server Components dialog box. For more information about operating system requirements for installing various editions of SQL Server, see SQL Server Books Online.

A typical installation and a custom installation use the same default options; however, in a custom installation, you can change the options. Here are the default values for the installation options.

Installation option	Typical/Custom	Compact
Install database server	Yes	Yes
Install upgrade tools	Yes	No
Install replication support	Yes	Yes
Install full-text search	No	No
Install client management tools	All	None
Install client connectivity	Yes	Yes
Install online documentation	Yes	No
Install development tools	None	None
Install code samples	None	None
Set character set	1252 - ISO Character Set	1252 - ISO Character Set
Set sort order	Dictionary order, case-insensitive	Dictionary order, case-insensitive
Set Unicode collation	General, case-insensitive	General, case-insensitive
Configure network protocols  (Windows NT®)	Named Pipes, TCP/IP Sockets, and Multiprotocol	Named Pipes, TCP/IP Sockets, and Multiprotocol
Configure network protocols  (Windows 95/98)	TCP/IP Sockets	TCP/IP Sockets
When you install SQL Server on Windows NT, these options are offered for all installation types:

•	Logon accounts for SQL Server and SQL Server Agent.

•	Whether to start SQL Server and SQL Server Agent.

You can back up and change your selections at any time before SQL Server Setup begins copying files.

Note  When you click Back, the window you return to reverts to the default options. The options you specified earlier are not retained.

File Locations

SQL Server Setup recognizes three file paths in allowing you to specify where the SQL Server files are installed. You may specify distinct file paths for both the program and data file locations. The default directory for both the program and data files is C:\Mssql7. Setup also installs files in the system directory. The system file location cannot be changed.

•	Program File Location

The program file location is the root directory where the setup program creates the folders that contain the program files and those files that typically do not change as you use SQL Server. Although these files are not read-only, the folders do not contain data, log, backup files, or replication data; therefore, the space requirements should not increase as SQL Server is used. Program files cannot be installed on a removable disk drive.

•	Data File Location

The data file location is the root directory where the setup program creates the folders that contain database and log files, as well as directories for the system log, backup, and replication data. SQL Server Setup creates database and log files for the master, model, tempdb, msdb, pubs, and Northwind databases. The SQL Server data path should be located on a drive that has space available for these files to grow. Data files cannot be installed on a file system using compression.


Select Components

When installing Microsoft® SQL Server™, you can choose which components to install from six categories. You can install all, some, or none of the components from each category.

You can run SQL Server Setup again later to install componenets that you did not install in the initial setup or to reinstall components. When run after the initial installation, the Setup program skips directly to the SQL Server Components dialog box. The typical installation options are checked by default. Check the components you want to install or reinstall and clear all others.

SQL Server Program Files

•	SQL Server

Installs the SQL Server relational database engine and other core tools. If any SQL Server program files are installed, the SQL Server component must be installed. When installing the SQL Server component, the Setup program also installs bcp, isql, osql, ODBC, OLE DB, and DB-Library.

•	Upgrade Tools

Installs the SQL Server Upgrade Wizard, which is used to upgrade SQL Server version 6.x databases to SQL Server version 7.0. The SQL Server Upgrade Wizard can only be installed on a computer running Microsoft Windows NT®.

•	Replication Support

Installs the scripts and binary files used for replication.

•	Full-Text Search

Installs the Microsoft full-text search engine, which extends the ability to search on character columns beyond the basic equality and LIKE operators. Full-text search is not available in the Desktop Edition.

Management Tools

•	SQL Server Enterprise Manager

Used to perform server and enterprise administrative tasks.

•	SQL Server Profiler

Used to monitor, record, and support auditing of SQL Server database activity.

•	SQL Server Query Analyzer

Used to enter Transact-SQL statements and procedures interactively. Also provides graphical query analysis in the form of graphical showplans.

•	MS DTC Client Support

Used to extend database transactions across multiple servers.

Microsoft Distributed Transaction Coordinator (MS DTC) coordinates transactions across a network of systems based in Windows NT and Microsoft Windows® 95/98. MS DTC client support includes Sampdtcc.exe, the sample MS DTC client program, and Sampdtcs.exe, the sample MS DTC client/server program.

•	Replication Conflict Resolver

Used to view and, if necessary, change the way synchronization conflicts are resolved.

Client Connectivity

The client connectivity component is used to allow communication between clients and servers. Includes network libraries for ODBC, OLE DB, and SQL-DMO (SQL Distributed Management Objects,) DB-Library, and the client-side network libraries.

Online Documentation

SQL Server Books Online provides on-screen access to the entire SQL Server documentation set. Its full-text search capability allows you to search quickly for a word or a phrase through the entire documentation set.

•	Books Online on Disk

Installs the documentation set in the \Mssql7\Books directory by default (program file location).

•	Books Online on CD

Creates a Start menu shortcut to run SQL Server Books Online from the SQL Server compact disc.

Development Tools

•	Headers and Libraries

Installs the include (*.h) files and library (*.lib) files needed by C developer to create programs that use OLE DB, ODBC, DB-Library, Open Data Services, SQL-DMO, Embedded SQL for C, and MS DTC. These files are installed in the \Mssql7\DevTools\Include and the \Mssql7\DevTools\Lib directories by default (program file location).

•	Backup/Restore API

Installs the header files, sample programs, and documentation needed to develop custom applications to back up and restore Microsoft® SQL Server™ databases.

•	Debugger Interface

Installs an interface for stored procedure debugging.

Code Samples

The samples component installs programming sample files that can be used for reference when writing programs for SQL Server. These files are installed in folders in the \Mssql7\DevTools\Samples directory by default (program file location). You can install any or all of these samples:

Option	Name
DBLIB	DB-Library
DTS	Data Transformation Services
ESQLC	Embedded SQL for C
MS DTC	Microsoft Distributed Transaction Coordinator
ODBC	Open Database Connectivity
ODS	Open Data Services
OLEAut	OLE Automation
Repl	Replication
SQL-DMO	SQL Distributed Management Objects
SQL-NS	SQL Namespace


Character Set, Sort Order, and Unicode Collation

The character set, sort order, and Unicode collation govern what character data is available and how it is sorted and compared. Choose a character set first; this determines what sort orders are available. Next choose a sort order; the character set and sort order combination determine a default Unicode collation. Be careful when changing already selected options because this can change other options back to a default value.

Important  It is critical that you select the correct character set, sort order, and Unicode collation when you first install Microsoft® SQL Server™. If you need to change these after installation, you must rebuild your databases and reload your data.

Character set

A character set, also known as a code page, is a group of letters, digits, and symbols that make up the possible values for the SQL Server character-based data types char, varchar, and text. Each character set contains 256 values. The printable characters of the first 128 values are the same for all character sets. The last 128 characters, referred to as extended characters, differ from set to set.  The extended characters often represent language-specific letters and symbols.

Sort order

A sort order is a set of rules that determines how SQL Server collates and presents data in response to database queries. A sort order determines how non-Unicode character data is compared (which characters are considered equivalent) and in what sequence it is returned from a query.

Unicode collation

A Unicode collation acts as a sort order for Unicode data. This is separate from the sort order for non-Unicode data. A Unicode collation consists of a locale and several comparison styles.

Select a Unicode locale from the list of countries and cultural regions to sort characters as is standard in that area.  The Unicode collation still provides a sort order for all characters in the Unicode standard, but precedence is given to the locale specified. Choose the general Unicode collation for any of these locales.

Afrikaans	Faeroese	Malay
Albanian	Farsi	Russian
Arabic	Georgian	Serbian
Basque	Greek	Swahili
Bulgarian	Hebrew	Urdu
Byelorussian	Hindi
English	Indonesian
The four comparison styles allow you to ignore the differences between similar characters. For example, if the case-insensitive comparison style is chosen, the characters A and a are considered equal. The width-insensitive and kana-insensitive comparison styles are relevant only to characters found in certain East Asian languages.

For more information about character sets, sort orders, and Unicode collation, see SQL Server Books Online.


Network Libraries

Microsoft® SQL Server™ uses network libraries to pass network packets back and forth between clients and a server running SQL Server. The network libraries, implemented as dynamic-link libraries (DLLs), perform the network operations required to communicate by using specific interprocess communication (IPC) mechanisms.

A server can listen on multiple network libraries at one time. During installation, SQL Server Setup installs all of the Net-Libraries onto the computer and allows you to configure some or all of the Net-Libraries. If a particular Net-Library is not configured, the server cannot listen on that Net-Library. After installation, you can change these configurations using the Server Network utility.

Named Pipes

Named Pipes support is required on Microsoft Windows NT® installations of SQL Server. Server-side Named Pipes is not supported on Microsoft Windows® 95/98. By default, SQL Server listens on the standard pipe, \\.\pipe\sql\query, for Named Pipes Net-Library connections. After SQL Server is installed, you can change the pipe name. You can also drop named pipe support and set SQL Server to listen only on other Net-Libraries.

TCP/IP Sockets

This Net-Library allows SQL Server to communicate using standard Windows Sockets as the IPC method across the TCP/IP protocol. By default, Windows 95/98 uses the TCP/IP Sockets Net-Library.

If you set SQL Server to listen on TCP/IP, type the TCP/IP port number in the Port number box. This is the port that SQL Server listens on when accepting connections from TCP/IP Sockets clients. The default is 1433, the official Internet Assigned Number Authority (IANA) socket number for SQL Server.

If you set SQL Server to listen on a proxy server using Microsoft Proxy Server over TCP/IP Sockets, type the proxy server address in the Remote WinSock proxy address box when you set up the TCP/IP Sockets Net-Library.

Multiprotocol

The Multiprotocol Net-Library uses the Windows remote procedure call (RPC) facility. With the Multiprotocol Net-Library, unlike other Net-Libraries, configuration parameters are not required.

The Multiprotocol Net-Library:

•	Communicates over most IPC mechanisms supported by Windows NT. (Only TCP/IP Sockets, NWLink IPX/SPX, and Named Pipes are considered tested and supported.)

•	Allows the use of Windows NT Authentication over all protocols that RPC supports.

•	Supports encryption for user password authentication as well as data.

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

To use Multiprotocol encryption for password authentication and data, select Enable Multiprotocol encryption. Multiprotocol encryption is not supported on Windows 95/98.

NWLink IPX/SPX

This Net-Library allows SQL Server to communicate 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 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. The Net-Library allows Novell SPX clients to connect.

AppleTalk ADSP

The server AppleTalk (ADSP) Net-Library allows Apple Macintosh® clients to connect to SQL Server by using native AppleTalk (as opposed to TCP/IP Sockets).

If you set up SQL Server to listen on AppleTalk, the Setup program prompts you for the AppleTalk service object name. The AppleTalk service object name is assigned by your system administrator, who might want to use the computer name of the server for consistency; for example, ACCOUNTING1.

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

The AppleTalk Net-Library is not supported on Windows 95/98.

Banyan VINES

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

If you set up SQL Server to listen on Banyan VINES, the Setup program prompts you for a StreetTalk service name. This has the form servicename@group@org, where servicename is the StreetTalk computer-based service name used by SQL Server, group is the group, and org is the organization. The computer-based service name used by SQL Server must first be created by using the MSERVICE program included with your VINES software. Also, to start SQL Server, you must be logged in with administrative permissions.

All Net-Libraries are installed by the Setup program. These are the default server Net-Library settings by platform.

Windows NT	Windows 95/98
TCP/IP Sockets	TCP/IP Sockets
Named Pipes	Shared Memory1
Multiprotocol	Multiprotocol

1 Shared Memory is a Net-Library used only for client/server connections on the same Windows 95/98 computer. You do not need to configure the Shared Memory Net-Library.

Here are the default client Net-Library settings by platform.

Windows NT	Windows 95/98
Named Pipes	TCP/IP Sockets


Services Accounts

When running on Microsoft® Windows NT®, Microsoft SQL Server™ and SQL Server Agent are started and run as Windows NT services named MSSQLServer and SQLServerAgent. For these services to run, they must be assigned a Windows NT user account. Both services may be assigned the same user account.

Note  Microsoft Windows® 95/98 does not support Windows NT services; instead, SQL Server simulates the MSSQLServer and SQLServerAgent services. You do not need to create user accounts for these simulated services.

Three types of accounts can be assigned to SQL Server services:

Local system

Local user

Domain user

The local system and local user accounts do not have network access rights. Using a local account restricts SQL Server from interacting with other servers. Some server-to-server activities can be performed only with a domain user account. For example:

Remote procedure calls (RPCs)

Replication

Backing up to network drives

Heterogeneous joins that involve remote data sources

SQL Mail and SQL Server Agent’s mail features

This restriction applies if you are using Microsoft Exchange. Most other mail systems also require clients (MSSQLServer and SQLServerAgent) to be run on accounts with network access.

You may enter one logon account for all of the services, or specify an account for each. The default account is the domain user account currently logged into the computer. You may also specify whether the services should start automatically whenever you restart Windows NT. Because the SQLServerAgent service can only run when the MSSQLServer service is running, you can set the SQLServerAgent service to autostart only if you set the MSSQLServer service to autostart as well.

Note  Another service, Microsoft Search, is installed along with the full-text search custom installation option. Microsoft Search is always assigned the local system account.