May 24, 2002 at 6:36 pm
Created publication which included a join filter. Created push subscription to other machine. SQL2K SP2 NT4SP6a.
Ran fine but I set up incorrectly with starting data (my error). Pre creation command is 'None' (=keep tables unchanged) and originally started with 'nosync'.
Dropped subscription in EM, taking option to run spMergeSubscription_Cleanup.
Recreated subscription in EM with nosync equivalent and get error below. Tried recreating snapshot (without much hope) and same error.
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
The process could not bulk copy into table '"dbo"."sysmergesubsetfilters"'.
(Source: 04SQL (Agent); Error number: 20037)
Cannot insert duplicate key row in object 'sysmergesubsetfilters' with unique index 'nc1sysmergesubsetfilters'.
(Source: 04SQL (Data source); Error number: 2601)
The records are in sysmergesubsetfilters from the previous setup it appears. Should the cleanup delete these records ? If so I will run it manually. I am loathe to do so without understanding the problem or making it worse. Can the sysmergesubsetfilters be 'emptied' manually without creating havoc. My previous experiences of modifying these types of tables suggests reaching for the backup tapes shortly after !
Any assistance gratefully received.
May 24, 2002 at 8:28 pm
My guess would be yes, but only a guess. I use transactional, rare need for merge. Having a backup seems wise! In general considering you're setting it up all over again I doubt you'll do much damage.
Andy
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply