Prev: Merge agent crashing generating a mdmp file
Next: Newbie - Can replication do this?
From: Rafael Bahia on 20 Jun 2010 20:04

Message-ID: <6c5f2e7fc37f4ae7973a6014ebed4954(a)newspe.com>
X-Mailer: http://www.umailcampaign.com, ip log:189.25.81.239
Newsgroups: microsoft.public.sqlserver.replication
NNTP-Posting-Host: 22.bb.5446.static.theplanet.com 70.84.187.34
Lines: 1
Path: news.netfront.net!zen.net.uk!dedekind.zen.co.uk!newsfeed01.sul.t-online.de!newsfeed00.sul.t-online.de!t-online.de!TK2MSFTFEEDS02.phx.gbl!TK2MSFTFEEDS01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl!newspe.com
Xref: news.netfront.net microsoft.public.sqlserver.replication:2121

Hi,

Recently I've solved this problem by recreating the primary key at the
subscriber manually. The snapshot kept saying that the primary key had been
created but when I checked it was not. Right after I created it, the
syncronization process came back to normal, applying all the undistributed
commands finally. I then checked the properties of the publication for the
table being replicated (just one in this case) and saw that the "recreate
clustered indexes" option was marked as 'true'. However, I saw no script for
recreating this object in the snapshot folder. A bug perhaps? I created a
script and put it to execute automatically every time SQL Server generates a
new snapshot. Of course that all that discovery and solution came after many
hours of suffering trying to identify the problem itself.

url:http://www.ureader.com/msg/1156508.aspx
 | 
Pages: 1
Prev: Merge agent crashing generating a mdmp file
Next: Newbie - Can replication do this?