Skip to main content

Check The Status of Transaction Replication


I wanted an easier way of monitoring the status of replications without having to use the “replication monitor”. Following are three procedures that’s available in sql server to assists in getting information pertinent to the status of replication


·        Get the Publisher status

USE distribution
GO
sp_replmonitorhelppublication
@publisher = null,
@publisher_db = null,  
@publication = null,
@publication_type = 0

Results
n       Look for the status where it can be any one of the following
1 = Started , 2 = Succeeded , 3 = In progress , 4 = Idle , 5 = Retrying ,6 = Failed

Returns : current status information for one or more publications at the Publisher.The procedure is executed at the Distributor on the distribution database.
 
Resources
http://msdn.microsoft.com/en-us/library/ms186304.aspx

·       Get the individual subscriber status

USE distribution
GO

sp_replmonitorhelpsubscription
@publisher = null, 
@publisher_db = null,
@publication = null,
@publication_type = 0,
@mode = 3,
@exclude_anonymous = 0
  
Filter condition
Mode
Value
Description
0 (default)
Returns all subscriptions.
1
Returns only subscriptions with errors.
2
Returns only subscriptions that have generated threshold metric warnings.
3
Returns only subscriptions that either have errors or have generated threshold metric warnings.
4
Returns the top 25 worst performing subscriptions.
5
Returns the top 50 worst performing subscriptions.
6
Returns only subscriptions that are currently being synchronized.
7
Returns only subscriptions that are not currently being synchronized.

Returns :  - The current status information for subscriptions for one or more publications at the Publisher 
                - Returns one  row for each returned subscription. 


FYI -  The procedure is executed at the Distributor on the distribution database.

Resource
http://msdn.microsoft.com/en-us/library/ms189452.aspx


·       Pending commands to apply at subscriptions

sp_replmonitorsubscriptionpendingcmds
@publisher  = 'QASQL\QA' ,
@publisher_db  = 'DropBox' ,
@publication = 'DropBox - Full DB (6 articles)',
@subscriber  = 'QASQL\QA',
@subscriber_db = 'ECSReports' ,
@subscription_type = 0

FYI  -  All the parameter are mandatory for this procedure
       -  This procedure will have to be executed for each subscriber
       -  The procedure is executed at the Distributor on the distribution database.

Returns :  - Information on the number of pending commands for a subscription to a transactional publication and a rough estimate of how much time it takes to process them. 
                - This stored procedure returns one row for each returned subscription.

 
Resource
http://msdn.microsoft.com/en-us/library/ms189452.aspx

Comments

Post a Comment

Popular posts from this blog

Create a dacpac To Compare Schema Differences

It's been some time since i added anything to the blog and a lot has happened in the last few months. I have run into many number of challenging stuff at Xero and spread my self to learn new things. As a start i want to share a situation where I used a dacpac to compare the differences of a database schema's. - This involves of creating the two dacpacs for the different databases - Comparing the two dacpacs and generating a report to know the exact differences - Generate a script that would have all the changes How to generate a dacbpac The easiest way to create a dacpac for a database is through management studio ( right click on the databae --> task --> Extract data-tier-application). This will work under most cases but will error out when the database has difffrent settings. ie. if CDC is enabled To work around this blocker, you need to use command line to send the extra parameters. Bellow is the command used to generate the dacpac. "%ProgramFiles...
10 comments
Read more

High Watermarks For Incremental Models in dbt

The last few months it’s all been dbt. Dbt is a transform and load tool which is provided by fishtown analytics. For those that have created incremental models in dbt would have found the simplicity and easiness of how it drives the workload. Depending on the target datastore, the incremental model workload implementation changes. But all that said, the question is, should the incremental model use high-watermark as part of the implementation. How incremental models work behind the scenes is the best place to start this investigation. And when it’s not obvious, the next best place is to investigate the log after an test incremental model execution and find the implementation. Following are the internal steps followed for a datastore that does not support the merge statements. This was observed in the dbt log. - As the first step, It will copy all the data to a temp table generated from the incremental execution. - It will then delete all the data from the base table th...
4 comments
Read more

The maximum number of working threads (100) are already running

The problem                 This afternoon, out of the blue, the development folks called over wanting to know why the DB server was not responding, sure enough the databases were not accessible from application and from MMS. I knew there weren’t any maintenance happening and so I logged in to the server remotely and found that the sql services were still running as usual and the services had not restarted. To my surprise, in 10-15 mins everyone was able connect to the server again.  My first thoughts were,  it would have been an issue with the network and due to the glitch the servers weren’t accessible during the  time period. Environment details : -           The sql server were on a hyper v with a single CPU and 1024 memory -           There was 80 + transaction replications setup and further 20-30 sql ser...
Post a Comment
Read more