gebeurtenis
31 mrt, 23 - 2 apr, 23
De grootste SQL-, Fabric- en Power BI-leerevenement. 31 maart – 2 april. Gebruik code FABINSIDER om $ 400 te besparen.
Zorg dat u zich vandaag nog registreertDeze browser wordt niet meer ondersteund.
Upgrade naar Microsoft Edge om te profiteren van de nieuwste functies, beveiligingsupdates en technische ondersteuning.
Applies to:
SQL Server
Azure SQL Managed Instance
This topic describes how to allow non-administrators to use Replication Monitor in SQL Server by using SQL Server Management Studio or Transact-SQL. Replication Monitor can be used by users who are members of the following roles:
The sysadmin fixed server role.
These users can monitor replication and have full control over changing replication properties such as agent schedules, agent profiles, and so on.
The replmonitor database role in the distribution database.
These users can monitor replication, but cannot change any replication properties.
In This Topic
Before you begin:
To allow non-administrators to use Replication Monitor, using:
To allow non-administrators to use Replication Monitor, a member of the sysadmin fixed server role must add the user to the distribution database and assign that user to the replmonitor role.
In SQL Server Management Studio, connect to the Distributor, and then expand the server node.
Expand Databases, expand System Databases, and then expand the distribution database (named distribution by default).
Expand Security, right-click Users, and then click New User.
Enter a user name and login for the user.
Select a default schema of replmonitor.
Select the replmonitor check box in the Database role membership grid.
Select OK.
At the Distributor on the distribution database, execute sp_helpuser (Transact-SQL). If the user is not listed in UserName in the result set, the user must be granted access to the distribution database using the CREATE USER (Transact-SQL) statement.
At the Distributor on the distribution database, execute sp_helprolemember (Transact-SQL), specifying a value of replmonitor for the @rolename
parameter. If the user is listed in MemberName in the result set, the user already belongs to this role.
If the user does not belong to the replmonitor role, execute sp_addrolemember (Transact-SQL) at the Distributor on the distribution database. Specify a value of replmonitor for @rolename
and the name of the database user or the Microsoft Windows login being added for @membername
.
To verify that the user belongs to the replmonitor role, execute sp_helprolemember (Transact-SQL) at the Distributor on the distribution database, and specify a value of replmonitor for @rolename
. If the user is not listed in MemberName in the result set, the user does not currently belong to this role.
If the user does belong to the replmonitor role, execute sp_droprolemember (Transact-SQL) at the Distributor on the distribution database. Specify a value of replmonitor for @rolename
and the name of the database user or the Windows login being removed for @membername
.
gebeurtenis
31 mrt, 23 - 2 apr, 23
De grootste SQL-, Fabric- en Power BI-leerevenement. 31 maart – 2 april. Gebruik code FABINSIDER om $ 400 te besparen.
Zorg dat u zich vandaag nog registreertTraining
Module
Use Monitor to troubleshoot Power Apps - Training
Learn how the Monitor tool from Power Apps Studio can help you proactively identify, troubleshoot, and resolve issues within your app.
Certificering
Microsoft Certified: Azure Database Administrator Associate - Certifications
Beheer een SQL Server-databaseinfrastructuur voor cloud-, on-premises en hybride relationele databases met behulp van de relationele Microsoft PaaS-databaseaanbiedingen.
Documentatie
Er is geen fout opgetreden bij het abonnement - SQL Server
Dit artikel bevat een tijdelijke oplossing voor het abonnement, die zich voordoet wanneer een primaire replica van een distributeur een failover uitvoert naar een replica die niet hetzelfde agentprofiel gebruikt.
Fout wanneer de agent replicatielogboeklezer mislukt - SQL Server
In dit artikel worden de stappen beschreven voor probleemoplossing die kunnen helpen bij het oplossen van problemen die optreden nadat de agent voor replicatielogboeklezers in SQL Server is mislukt.