Some instances of SQL Server 2000 Personal Edition and SQL Server 2000 Desktop Engine (also known as MSDE 2000) instance may run as a local data store, only by running on the same computer applications. If you never been to these instances of MSDE 2000 through the network connection, these examples do not need network support, the resources to turn off those who do not need to be a wise choice.
If you are using SQL Server 2005
The concept of the SQL Server 2000 and discussions also apply to SQL Server 2005 and SQL Server Express.
Each instance of SQL Server 2000 or MSDE 2000 instance can be configured to listen on a specific set of network protocols and addresses. If an instance does not require network connectivity, turning off unused network support can reduce the instances of security-dependent. You can configure the instance to not listen on any network protocol to do this. In general, you should only run as a local data store for this version of SQL Server 2000 configuration:
? SQL Server 2000 Personal Edition
? SQL Server 2000 Desktop Engine (MSDE 2000)
A SQL Server instance is configured to not listen on the network agreement, the same computer, all applications will use the shared memory network library to communicate with them.
Close the network protocol support does not mean that the network protocol is inherently insecure. Any time a program accesses an external resource, the program should obtain information about resources for the safety of this external dependency, even though the Department of Resources also very safe too. By turning off unused resources, the program can reduce its security dependencies.
Note: All of the examples of management are to be completed on the computer it is running.
When SQL Server 2000 SP3a or MSDE 2000 SP3a instance is configured to not listen on any network protocol, they will stop listening on UDP port 1434. SQL Server 2000 or an earlier version of MSDE 2000, regardless of their configuration, always listen for UDP 1434.
If the instance of the "Windows Authentication" mode, this computer is one Windows account must be a SQL Server sysadmin fixed server role as a member. If the instance is running in mixed mode, administrators can use the sa account, or SQL Server sysadmin fixed server role of a Windows account to log on.
To use the "SQL Server 2000 Server Network" utility to an existing SQL Server 2000 or MSDE 2000 instance is configured to not listen for network connection, follow these steps:
1. If SQL Server is installed on the computer client tool, open the Microsoft SQL Server program group, and then start the "server network" utility. If you do not install the SQL Server client utilities, run the SQL Server ToolsBinn Svrnetcn.exe file folder. Usually, not SQL Server installed on the computer because the client utility is: The computer is only running instance of MSDE 2000, and these examples do not provide users with practical use of SQL Server client tools license.
2. In the "General" tab, select the "instance of this computer" list box of the SQL Server instance name. Click the default instance of the "Server Name" to select, or choose any given instance of "server name / instance name."
3. To limit the instance of SQL Server allows only local connections, click the "Disable" until "an agreement to open" list are no longer listed in any agreement. If you need to change this setting to allow remote connections, reverse this process and enable one or more agreements.
4. Click "OK."
5. To re-start the SQL Server instance, so the changes take effect.
For a current configuration does not support network connectivity to SQL Server 2000 instance, you can use the "SQL Server 2000 Server Network" utility to enable the network connection to it.
DISABLENETWORKPROTOCOLS switch
SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 3 Setup DISABLENETWORKPROTOCOLS introduced a new switch, you can use it to install a new network connection is not enabled on any instance of MSDE 2000.
For SP3, the behavior of this switch is: If you do not specify DISABLENETWORKPROTOCOLS, the instance will be installed to enable the network protocol connection. If you specify DISABLENETWORKPROTOCOLS = 1, will not enable any network protocol for instance.
In SP3a, the behavior of the DISABLENETWORKPROTOCOLS There are two changes:
? Install SP3a a new instance of the default behavior is to disable network protocol support, making the instance more secure by default.
? When upgrading an existing instance of MSDE 2000, you can specify the closed network protocol support.
The following table describes this behavior:
New installation of MSDE 2000 SP3a:
The current set of network protocols specified by the user to set network protocol showed no disable disable enable enable no no no user specified settings to disable
Upgrade to MSDE 2000 SP3a:
Currently set user-specified network protocol network protocol settings to disable disable disable disable enable the results to enable disabled no user specified settings to disable enable enable enable enable disable disable enable enable no user specified settings
Note: When you use the "/?" Switch to run MSDE 2000 setup.exe to switch out their support, / DISABLENETWORKPROTOCOLS switch is not listed.