- You configure transactional replication in Microsoft SQL Server 2005 or in Microsoft SQL Server 2008.
- The transactional replication topology consists of several publishers.
- The publishers replicate data into the same subscriber database.
- The distribution agents run continuously or run on a very frequent schedule. For example, the distribution agents run every minute.
Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Note Typically, the correct rowcount estimate is equal to the number of subscriptions in the database. If you use the Subscription Streams feature, the rowcount estimate is equal to the number of subscriptions multiplied by the number of configured streams for each subscription.
Method 1: Use the DBCC UPDATEUSAGE command
To resolve this issue, update the incorrect rowcount value. To do this, run the following command:
Method 2: Use the ALTER INDEX statement
To resolve this issue, rebuild the indexes that are associated with the MSreplication_subscriptions table. To do this, use the following statement:
Method 1: Use SQL Server Management Studio
To use SQL Server Management Studio to check the rowcount value for the MSreplication_subscriptions system table, follow these steps:
- Start SQL Server Management Studio, and then connect to the subscriber server instance.
- Expand Databases, and then expand the subscriber database.
- Expand Tables, and then expand System Tables.
- Right-click dbo.MSreplication_subscriptions, and then click Properties.
- Click Storage, and then verify the rowcount value in the Row count field.
To check the rowcount value for the MSreplication_subscriptions system table, run the following query:
Article ID: 2674882 - Last Review: Mar 23, 2012 - Revision: 1