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 using specific interprocess communication (IPC) mechanism protocols.
SQL Server includes a set of server Net-Libraries that enable simultaneous connections from clients running named pipes or other interprocess communication (IPC) mechanisms. Named pipes are installed by default (and it is recommended that named pipes not be removed, even if other Net-Libraries are chosen). During installation, the setup program gives you the option of setting up one or more of these other Net-Libraries on the server:
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.
If you set up SQL Server to listen on TCP/IP, the setup program prompts you for the TCP/IP port number SQL Server will listen on when accepting connections from TCP/IP sockets clients. The default is 1433, the official Internet Assigned Number Authority (IANA) socket number for Microsoft SQL Server.
If you set up SQL Server to listen on Banyan VINES, the setup program prompts you for a StreetTalk™ PC-based service name. This 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 PC-based service name used by SQL Server must first be created using the MSERVICE program included with your VINES software. Also, to start SQL Server you must be logged in with administrative privileges.
Note that before you can configure SQL Server to listen on Banyan VINES, you must install the Banyan VINES software (available from Banyan).
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 machine name of the server for consistency. For example:
ACCOUNTING1
Note that it is not necessary to enter the AppleTalk zone, because the local zone will be used when registering the service.
If you set up SQL Server to listen on DECnet sockets, the setup program prompts you for the DECnet object ID that SQL Server will listen on when accepting connections from clients under this Net-Library.
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 pound (#) 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.
A server can listen on multiple Net-Libraries at one time. In addition to listening on the other server Net-Libraries you select, by default SQL Server always listens on named pipes as well.
By default, SQL Server listens on the standard pipe, \\.\pipe\sql\query, for named pipe connections. You can change the pipe name. You can also drop named pipe support and set SQL Server to listen only on other Net-Libraries.
You cannot change Net-Library configurations during an upgrade. The existing Net-Library configurations are carried over and can be modified after upgrade using SQL Setup from the Microsoft SQL Server 6.0 program group.