![]() SQL Server Network Utility automatically detects if the instance of SQL Server you specify is on a failover cluster. For more information about setting up a proxy server, see Connections to SQL Server Through Proxy Server. For more information about certificates, see the Windows 2000 documentation. To use SSL encryption, you must install a certificate using the fully qualified domain name of the computer running the instance of SQL Server 2000. For more information about SSL encryption, see Net-Library Encryption. The encryption is turned on or off for the entire enabled server protocols and you cannot specify encryption for a specific protocol. Enable the Secure Sockets Layer (SSL) encryption for all of the enabled server protocols.If the instance is running on a SQL Server 2000 failover cluster, it will listen on those ports on each IP address selected for SQL Server during SQL Server setup. If you specify a list of port addresses, the instance of SQL Server will listen on those ports on each IP address available on the computer running the instance. You can specify a comma-separated list of port addresses for the TCP/IP protocol. When you are entering network addresses manually on a computer running multiple instances of SQL Server, you must not duplicate network addresses between instances. Specify or change the network address on which each enabled protocol will listen.Disable a server protocol that is no longer needed.For more information about VIA, see VIA Clients. VIA is not available for systems running Microsoft Windows® 98. For VIA to work, you must use the supported hardware (Giganet). This protocol provides highly reliable and efficient data transfer, when used with specific hardware. For example, enable the protocol for VIA (Virtual Interface Architecture). Enable the server protocols on which the instance of SQL Server will listen. ![]() ![]() Manage the server Net-Library properties for each instance of SQL Server on a database computer.However, if your server uses a network protocol on which SQL Server, by default, is not listening (for example, if your server is using NWLink IPX/SPX), and the SQL Server server Net-Library for that protocol is not activated to listen for SQL Server clients, you must use SQL Server Network Utility.Īlthough no server Net-Library configuration actions are necessary to enable SQL Server applications to connect to any instance of SQL Server, you can do the following: In most cases, you do not need to reconfigure Microsoft® SQL Server™ to listen on additional server Net-Libraries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |