Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to:
SQL Server
Azure SQL Managed Instance
When using transactional replication, transaction commands are stored in the distribution database until the Distribution Agent propagates them to all Subscribers or a Distribution Agent at the Subscriber pulls the changes. These pending commands in the distribution database can be viewed programmatically using replication stored procedures. For more information, see Replication Stored Procedures (Transact-SQL).
(Optional) At the Publisher on the publication database, execute sp_helparticle. Specify @publication
and @article
. Note the value of article id in the result set.
At the Distributor on the distribution database, execute sp_browsereplcmds. (Optional) Specify the article ID from step 2 for @article_id
. (Optional) Specify the ID of the publication database for @publisher_database_id
, which can be obtained from the database_id column in the sys.databases catalog view.
Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register today