Skip to content

database-mirroring-allow-network-access-windows-authentication.md

Latest commit

 

History

History
61 lines (48 loc) · 4.19 KB

database-mirroring-allow-network-access-windows-authentication.md

File metadata and controls

61 lines (48 loc) · 4.19 KB
title Database Mirroring - Allow Network Access - Windows Authentication | Microsoft Docs
ms.custom
ms.date 05/17/2016
ms.prod sql
ms.prod_service high-availability
ms.component database-mirroring
ms.reviewer
ms.suite sql
ms.technology high-availability
ms.tgt_pltfrm
ms.topic conceptual
helpviewer_keywords
Windows authentication [SQL Server]
database mirroring [SQL Server], security
ms.assetid 28c8fec5-5feb-4c84-8d72-f2bd1ae3b40d
caps.latest.revision 34
author MikeRayMSFT
ms.author mikeray
manager craigg

Database Mirroring - Allow Network Access - Windows Authentication

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] Using Windows Authentication for connecting the database mirroring endpoints of two instances of [!INCLUDEssNoVersion] requires manual configuration of login accounts under the following conditions:

  • If the instances of [!INCLUDEssNoVersion] run as services under different domain accounts (in the same or trusted domains), the login of each account must be created in master on each of the remote server instances and that login must be granted CONNECT permissions on the endpoint.

  • If the instances of [!INCLUDEssNoVersion] run as the Network Service account, the login of the each host computer account (DomainName**\**ComputerName$) must be created in master on each of the remote server instances and that login must be granted CONNECT permissions on the endpoint. This is because a server instance running under the Network Service account authenticates using the domain account of the host computer.

Note

Ensure that an endpoint exists for each of the server instances. For more information, see Create a Database Mirroring Endpoint for Windows Authentication (Transact-SQL).

To configure logins for Windows Authentication

  1. For the user account of each instance of [!INCLUDEssNoVersion], create a login on the other instances of [!INCLUDEssNoVersion]. Use a CREATE LOGIN statement with the FROM WINDOWS clause.

    For more information, see Create a Login.

  2. Also, to ensure that the login user has access to the endpoint, use the GRANT statement to grant connect permissions on the endpoint to the login. Note that granting connect permissions to the endpoint is unnecessary if the user is an Administrator.

    For more information, see Grant a Permission to a Principal.

Example

The following [!INCLUDEtsql] example creates a [!INCLUDEssNoVersion] login for a user account named Otheruser that belongs to a domain called Adomain. The example then grants this user connect permissions to a pre-existing database mirroring endpoint named Mirroring_Endpoint.

USE master;  
GO  
CREATE LOGIN [Adomain\Otheruser] FROM WINDOWS;  
GO  
GRANT CONNECT on ENDPOINT::Mirroring_Endpoint TO [Adomain\Otheruser];  
GO

See Also

Overview of Always On Availability Groups (SQL Server)
Database Mirroring (SQL Server)
Transport Security for Database Mirroring and Always On Availability Groups (SQL Server)
The Database Mirroring Endpoint (SQL Server)