Replication: Help! I lost a replication system stored procedure

“Could not find stored procedure MSMERGE_INS/UPD/DEL_SP_XXXXXXXXXX” If you have replication set up on a SQL Server 2005 (any build post SP2) or SQL 2008, and you receive a similar error as the one mentioned above, there is a way to resolve this issue without having to reinitialize / drop – create your publication. http://msdn.microsoft.com/en-us/library/bb326615.aspx SP_VUPGRADE_MERGEOBJECTS…

0

Replication: Merge Filters – optimize optimize optimize

I noticed that many people overlook optimizing their filters in a merge replication topology. This is crucial to performance and attempting to tweak the replication itself (example: using pre-computed partitions) may not be sufficient. An example of such: All the join filters specified against the published articles in merge publication would be evaluated during DML…

0

Replication: Partitioned snapshot fails with "Incorrect syntax near" message when article name has more than 40 characters

Repro: ** note: if you will be trying this repro – please remember to alter the script to suit your environment (Example: @web_synchronization_url) ** SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[tbl_Thisisareallylongtablenametoemphisetheissue](     [Col] [uniqueidentifier] ROWGUIDCOL  NOT NULL CONSTRAINT [DF__tbl_Activ__Activ__084B3915]  DEFAULT (newsequentialid()),     [Col2] [uniqueidentifier] NOT NULL,    …

0

Replication: Snapshot does not generate correctly the partition scheme when you add a view to the publication

Problem: SQL Server 2005: I have created a database that contains various file groups and assigned the new data files to their respective file group. I also created a partition function and partition scheme (using the file groups created). I then created a transactional publication in which I place all the articles involved. The snapshot…

0

Replication: Configuring Remote Distributor Generates the following error: “"Could not find stored procedure ‘sp_replcheck_qv’”

Problem: When I try to configure a SQL Server 2008 to be a remote distributor of my SQL Server 2005 / 2000 instance, I get the following error generated when using the GUI wizard: Could not find stored procedure ‘sp_replcheck_qv’ This prevents me from adding a SQL Server 2008 instance to the remote distributor configuration…

1

Replication: Identity column seeded incorrectly if two or more merge agents try to adjust the publisher range in parallel

Problem: SQL Server 2008 Merge replication with automatic identity range handling. Suddenly, every insert on a specific table (TABLE1) stopped working with message: The insert failed. It conflicted with an identity range check constraint in database ‘DBNAME’, replicated table ‘dbo.TABLE1’, column ‘TblId’. If the identity column is automatically managed by replication, update the range as…

0

Replication: The merge process could not query the last sent and received generations.

Problem: Topology: – Merge replication with statically-filtered publications. – 2 publishers, CLSILVA1 and CLSILVA2, which are publishing a different set of tables – Many subscribers; most of them are subscribing to both publishers into the same subscriber database – Each publisher has an individual publication for each subscriber; so each article is included in several…

0

Replication: a few Questions and Answers

Here are some interesting questions, and their respective answers, which may clarify a few things in regards to replication: Best practices replication performance: The first place to look is the SQL Server 2008 Books Online, especially the chapter “The System Has a Performance Issue” under Replication->Troubleshooting->Troubleshooting Concepts. This chapter summarizes basic steps and also provides…

0

Replication: The lineage parameter is shorter than the minimum required size

Problem: I created/altered a (new) record on Subscriber B which I then synchronized with my publisher. The row is then downloaded to Subscriber A and fails. Running a profiler trace, I notice that the error message is the following: Server: Msg 21512, Level 16, State 5, Procedure ins_xxxxx, Line 32 GETMAXVERSION: The lineage parameter is…

1