Skip to content

Latest commit

 

History

History
45 lines (35 loc) · 3.78 KB

File metadata and controls

45 lines (35 loc) · 3.78 KB
title Log Reader Agent Security (SSMS)
description Describes the 'Log Reader Agent Security' page for a Transaction and Peer-to-peer Publication within SQL Server Management Studio (SSMS).
ms.custom seo-lt-2019
ms.date 03/14/2017
ms.prod sql
ms.prod_service database-engine
ms.reviewer
ms.technology replication
ms.topic conceptual
f1_keywords
sql13.rep.p2pwizard.LRA.f1
ms.assetid 6575e2a8-16bb-449c-bdca-4a4202d0972f
author MashaMSFT
ms.author mathoma

Log Reader Agent Security (Peer-to-Peer Replication)

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] The Log Reader Agent Security page allows you to specify the accounts under which the Log Reader Agent at each peer runs and makes connections. For information on permissions required by agents and best practices for replication security, see Replication Agent Security Model and Replication Security Best Practices.

Note

There is one Log Reader Agent for each database that is published using transactional replication. If the Log Reader Agent for a database has already been configured (either for a publication in a previous run of this wizard or for another transactional publication in the same database), you cannot change the credentials it uses in this wizard. If you specify new credentials, they are ignored. To change credentials, use the Publication Properties dialog box. For more information, see View and Modify Replication Security Settings.

Options

Click the properties button (...) in the row for each peer to access the Log Reader Agent Security dialog box. Click Help on the Log Reader Agent Security dialog box that is launched for more information on the permissions required for accounts used by the agents.

After settings have been entered in the dialog box, connection information for the Subscriber is displayed in the grid.

Agents for Publisher
The name of each peer server instance.

Peer Database
The database that serves as the publication database and subscription database at each peer.

Connection to Distributor
The context under which the connection to the Distributor is made. The local connection to the Distributor is always made using the context of the [!INCLUDEmsCoName] Windows account under which the agent runs, so this field will always display Impersonate '<Domain>\<Login>' or Impersonate '<Computer>\<Login>'.

Connection to Publisher
The context under which the connection to the Publisher is made. The connection to the Publisher can be made using a [!INCLUDEmsCoName] [!INCLUDEssNoVersion] login or using the context of the Windows account under which the agent runs. The field displays one of the following: Use login '<Login>', Impersonate '<Domain>\<Login>' or Impersonate '<Computer>\<Login>'. [!INCLUDEmsCoName] recommends that all connections be made using the context of the Windows account.

See Also

Administer a Peer-to-Peer Topology (Replication Transact-SQL Programming)
Peer-to-Peer Transactional Replication