MSSQL_REPL027183
Message Details
Product Name |
SQL Server |
Product Version |
9.0 |
Product Build Number |
9.00.1399.60 |
Event ID |
27183 |
Event Source |
MSSQLSERVER |
Component |
SQL Server Database Engine |
Symbolic Name |
|
Message Text |
The merge process failed to enumerate changes in articles with parameterized row filters. If this failure continues, increase the query timeout for this process, reduce the retention period for the publication, and improve indexes on published tables. |
Explanation
This error is raised if a Merge Agent timeout occurs while processing changes in a filtered publication. The timeout might be caused by one of the following issues:
- Not using the precomputed partitions optimization.
- Index fragmentation on columns used for filtering.
- Large merge metadata tables, such as MSmerge_tombstone, MSmerge_contents, and MSmerge_genhistory.
- Filtered tables that are not joined on a unique key and join filters that involve a large number of tables.
User Action
To resolve the issue:
- Increase the value of the -QueryTimeOut parameter for the Merge Agent to allow processing to continue while you address the underlying issues causing the error. Agent parameters can be specified in agent profiles and on the command line. For more information, see:
- How to: Work with Replication Agent Profiles (SQL Server Management Studio)
- How to: View and Modify Replication Agent Command Prompt Parameters (SQL Server Management Studio)
- How to: Work with Replication Agent Profiles (Replication Transact-SQL Programming)
- Programming Replication Agent Executables.
- Use the precomputed partitions optimization if possible. This optimization is used by default if a number of publication requirements are met. For more information about these requirements, see Optimizing Parameterized Filter Performance with Precomputed Partitions. If the publication does not meet these requirements, consider redesigning the publication.
- Specify the lowest setting possible for the publication retention period, because replication cannot clean up metadata in the publication and subscription databases until the retention period is reached. For more information, see Subscription Expiration and Deactivation.
- As part of maintenance for merge replication, occasionally check the growth of the system tables associated with merge replication: MSmerge_contents, MSmerge_genhistory, and MSmerge_tombstone, MSmerge_current_partition_mappings, and MSmerge_past_partition_mappings. Periodically re-index these tables. For more information, see Reorganizing and Rebuilding Indexes.
- Ensure that columns used for filtering are properly indexed and rebuild such indexes if necessary. For more information, see Reorganizing and Rebuilding Indexes.
- Set the join_unique_key property for join filters that are based on unique columns. For more information, see Join Filters.
- Limit the number of tables in the join filter hierarchy. If you are generating join filters of five or more tables, consider other solutions: do not filter tables that are small, not subject to change, or are primarily lookup tables. Use join filters only between tables that must be partitioned among subscriptions.
- Make a smaller number of changes on filtered tables between synchronizations, or run the Merge Agent more frequently. For more information about setting synchronization schedules, see How to: Specify Synchronization Schedules (SQL Server Management Studio) and How to: Specify Synchronization Schedules (Replication Transact-SQL Programming).
See Also
Concepts
Cause and Resolution of Replication Errors