Skip to content

hide-an-instance-of-sql-server-database-engine.md

Latest commit

 

History

History
46 lines (36 loc) · 4.19 KB

hide-an-instance-of-sql-server-database-engine.md

File metadata and controls

46 lines (36 loc) · 4.19 KB
title Hide an Instance of SQL Server Database Engine | Microsoft Docs
ms.custom
ms.date 08/19/2015
ms.prod sql
ms.prod_service high-availability
ms.reviewer
ms.technology configuration
ms.topic conceptual
helpviewer_keywords
Database Engine [SQL Server], hiding instances
hiding instances of Database Engine
ms.assetid 392de21a-57fa-4a69-8237-ced8ca86ed1d
author MikeRayMSFT
ms.author mikeray
manager craigg

Hide an Instance of SQL Server Database Engine

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] This topic describes how to hide an instance of the [!INCLUDEssDE] in [!INCLUDEssCurrent] by using SQL Server Configuration Manager. [!INCLUDEssNoVersion] uses the [!INCLUDEssNoVersion] Browser service to enumerate instances of the [!INCLUDEssDE] installed on the computer. This enables client applications to browse for a server, and helps clients distinguish between multiple instances of the [!INCLUDEssDE] on the same computer. You can use the following procedure to prevent the SQL Server Browser service from exposing an instance of the [!INCLUDEssDE] to client computers that try to locate the instance by using the Browse button.

Using SQL Server Configuration Manager

To hide an instance of the SQL Server Database Engine

  1. In SQL Server Configuration Manager, expand SQL Server Network Configuration, right-click Protocols for <server instance>, and then select Properties.

  2. On the Flags tab, in the HideInstance box, select Yes, and then click OK to close the dialog box. The change takes effect immediately for new connections.

Remarks

If you hide a named instance, you will need to provide the port number in the connection string to connect to the hidden instance, even if the browser service is running. We recommend that you use a static port instead of a dynamic port for the named hidden instance.
For more information, see Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager).

Clustering

If you hide a clustered named instance, cluster service may not be able to connect to [!INCLUDEssNoVersion]. This will cause the cluster instance's IsAlive check to fail and [!INCLUDEssNoVersion] will go offline. We recommend that you create an alias in all the nodes of the clustered instance to reflect the static port that you configured for the instance.
For more information, see Create or Delete a Server Alias for Use by a Client (SQL Server Configuration Manager).

If you hide a clustered named instance, cluster service may not be able to connect to [!INCLUDEssNoVersion] if the LastConnect registry key (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI11.0\LastConnect) has a different port than the port that [!INCLUDEssNoVersion] is listening on. If the cluster service is unable to make a connection to the [!INCLUDEssNoVersion], you might see an error similar to the following:
Event ID: 1001: Event Name: Failover clustering resource deadlock.

See Also

Server Network Configuration
Description of SQL Virtual Server client connections
How to assign a static port to a SQL Server named instance - and avoid a common pitfall