Although SQL Server 2000 is flexible in regard to collations, don't underestimate the choices you make during installation. As I mentioned earlier, the server's collation applies to all system databases and determines collation rules for all objects recorded in system databases (e.g., login names, database names). Furthermore, tempdb's collation is also the server collation you chose during installation. When you create a temporary table, the table's columns use tempdb's collation unless you specify COLLATE database_default in each column definition to apply the collation of the database you're connected to.
Network Libraries
After specifying collation settings, you move on to the Network Libraries dialog box, which Figure 8 shows. Network Library is the protocol the client application uses to communicate with SQL Server. Both the client and SQL Server must have at least one matching Network Library through which they can communicate. In the Network Libraries dialog box, you set the Network Libraries SQL Server will use to communicate with clients.
In SQL Server 6.5, only Named Pipes and Multi-Protocol allow Windows authentication; all other Network Libraries allow only SQL Server authentication. So, for SQL Server 6.5, the type of logins you want to support is a factor in which Network Library you choose. Furthermore, only Multi-Protocol allows data encryption, so you have to choose that Network Library if you want SQL Server 6.5 to support data encryption. In SQL Server 7.0, all Network Libraries support Windows authentication, so you have more flexibility in that sense, but Multi-Protocol remains the only protocol that allows data encryption.
In SQL Server 2000, you can force encryption by using Secure Sockets Layer (SSL) with all Network Libraries through the SQL Server Network Utility and the SQL Server Client Network Utility, so encryption doesn't determine Network Library. Also, in SQL Server 2000, Multi-Protocol doesn't support the instance-naming scheme SERVERNAME\INSTANCENAME, so Multi-Protocol isn't a good choice when you have named instances. The most commonly used Network Library in SQL Server 2000 is probably TCP/IP Sockets. It provides good performance, allows Windows authentication, and you can enforce SSL encryption with it if you need to.
Most people working with previous releases of SQL Server know that SQL Server's default TCP port is port 1433. When using the default port, client connections don't need to provide the port number aside from the server name or IP address. However, SQL Server 2000 supports multiple instances, which can't all use the same port number. So when you install a named instance, the installation program suggests 0 as the port number. Port number 0 means that when SQL Server starts for the first time, it dynamically chooses a free port number and keeps it permanently or until you manually change it later. So how can client connections continue referring to SQL Server by providing its name/IP+instance name alone without specifying the port number? A listener service in SQL Server 2000 listens on port 1433 for client requests to connect to SQL Server, then redirects the request to the appropriate instance by examining the instance name in the request and matching it with the instance's port number.
Unattended and Remote Installation
Now that we're done with standard installation, let's discuss unattended installation. The setupsql.exe program lets you record an answer file containing all the answers for the various installation options that you usually choose in the installation-program dialog boxes. Later, you can run an installation by executing one command that invokes setupsql.exe with the answer file as an argument. This type of installation, which doesn't require any user intervention, is called unattended installation.
To prepare the answer file, start the installation program, choose Advanced Options in the Installation Selection dialog box, then choose Record Unattended .ISS file in the dialog box that Figure 9 shows. The installation program walks you through the regular setup dialog boxes, where you can fill in all the options you want to record. When you're finished, the installation program creates a file called setup.iss in the \WINNT folder.
To invoke an unattended installation, run the setupsql.exe program with the -s option for silent installation and the -f1 option to specify the answer file. For example, to invoke a silent unattended installation that doesn't inform you when the installation is finished, you can use the following command:
<path>\setupsql.exe -s -f1 <path>\setup.iss
If you want to know when the installation finished, invoke the setupsql.exe program from a command prompt or in a batch file as follows:
start /wait <path>\setupsql.exe -s -f1 <path>\setup.iss
Prev. page
1
2
[3]
4
next page 
