|
|
You're in the
sql server replication
group:Rows do not match between Publisher and Subscriber. (Possible Bug?
sql server replication:
How did you set this guy up and how are you modifying the row? BCP, DTS, or
a direct update/insert/delete? -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Pascal" <Pascal@discussions.microsoft.com> wrote in message news:7A76A241-D091-441A-9A3A-0FB57CBE1AC4@microsoft.com... >I have a transactional updatable subscriber database that works fine for >all > articles (164 of them) apart from one where I continuously get the error > above. > > The thing is, msrepl_tran_version is the same on both the publisher and > the > subscriber. I have tried everything. I've rebuilt the Subscriber triggers, > I've rebuilt the Publisher update SP, I've dropped and re-created the > article. > > The intersting thing is when I remove 'sp_MSsync_upd_trig_' from the > subscriber it works one time, but fails to update msrepl_tran_version on > the > publisher leaving the 2 articles out of synch and the next update fails > (as > it should). > > Any thoughts before I give up and try merge replication instead? > > I'm running SQL Server 2k SP4 on both machines. OS is Windows Server 2k. > > Cheers.
I have a transactional updatable subscriber database that works fine for all
articles (164 of them) apart from one where I continuously get the error above. The thing is, msrepl_tran_version is the same on both the publisher and the subscriber. I have tried everything. I've rebuilt the Subscriber triggers, I've rebuilt the Publisher update SP, I've dropped and re-created the article. The intersting thing is when I remove 'sp_MSsync_upd_trig_' from the subscriber it works one time, but fails to update msrepl_tran_version on the publisher leaving the 2 articles out of synch and the next update fails (as it should). Any thoughts before I give up and try merge replication instead? I'm running SQL Server 2k SP4 on both machines. OS is Windows Server 2k.
It was a manual synchronisation. Published - Backed-up - Restored to Remote
Server (on same lan) - Pushed the Subscription out - Applied synctran_commands from the publisher to the subscription manually. THe distributor is on the publisher server. I am updating a row via QA calling an update SP. When the rows are synched the update to the subscriber succeeds, so does the update at the publisher, but msrepl_tran_version remains the same at the publisher. It is not getting updated to the version on the subscriber. If I publish out the table to another empty database and allow the snapshot agent to re-create the table and apply the schema and data it works fine. However I don't see any differences in the SPs/Triggers that are created. Hope I'm making sense. Cheers. [quoted text, click to view] "Hilary Cotter" wrote:
> How did you set this guy up and how are you modifying the row? BCP, DTS, or > a direct update/insert/delete? > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Pascal" <Pascal@discussions.microsoft.com> wrote in message > news:7A76A241-D091-441A-9A3A-0FB57CBE1AC4@microsoft.com... > >I have a transactional updatable subscriber database that works fine for > >all > > articles (164 of them) apart from one where I continuously get the error > > above. > > > > The thing is, msrepl_tran_version is the same on both the publisher and > > the > > subscriber. I have tried everything. I've rebuilt the Subscriber triggers, > > I've rebuilt the Publisher update SP, I've dropped and re-created the > > article. > > > > The intersting thing is when I remove 'sp_MSsync_upd_trig_' from the > > subscriber it works one time, but fails to update msrepl_tran_version on > > the > > publisher leaving the 2 articles out of synch and the next update fails > > (as > > it should). > > > > Any thoughts before I give up and try merge replication instead? > > > > I'm running SQL Server 2k SP4 on both machines. OS is Windows Server 2k. > > > > Cheers. > >
Let me see if I understand what you did. You created a publication on your
publisher. You backed up the publication database, your restored the backup of the publication database on the subscriber (hopefully at that time no-one was working on the publication database), and then you created your subscription? Was it a sync or a no sync subscription? Your chances of having this work successfully would be if you did a sync subscription (i.e. the subscriber does not have the schema and data in place option). I would advise you to drop and recreate the subscription and push it again, again making sure no-one was working on the publication database while you are doing this. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Pascal" <Pascal@discussions.microsoft.com> wrote in message news:9EA15FAA-8398-42BC-99C3-736EC1EFF99C@microsoft.com... > It was a manual synchronisation. Published - Backed-up - Restored to > Remote > Server (on same lan) - Pushed the Subscription out - Applied > synctran_commands from the publisher to the subscription manually. > > THe distributor is on the publisher server. > > I am updating a row via QA calling an update SP. > > When the rows are synched the update to the subscriber succeeds, so does > the > update at the publisher, but msrepl_tran_version remains the same at the > publisher. It is not getting updated to the version on the subscriber. > > If I publish out the table to another empty database and allow the > snapshot > agent to re-create the table and apply the schema and data it works fine. > However I don't see any differences in the SPs/Triggers that are created. > > Hope I'm making sense. > > Cheers. > > > "Hilary Cotter" wrote: > >> How did you set this guy up and how are you modifying the row? BCP, DTS, >> or >> a direct update/insert/delete? >> >> -- >> Hilary Cotter >> Director of Text Mining and Database Strategy >> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. >> >> This posting is my own and doesn't necessarily represent RelevantNoise's >> positions, strategies or opinions. >> >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> >> >> >> "Pascal" <Pascal@discussions.microsoft.com> wrote in message >> news:7A76A241-D091-441A-9A3A-0FB57CBE1AC4@microsoft.com... >> >I have a transactional updatable subscriber database that works fine for >> >all >> > articles (164 of them) apart from one where I continuously get the >> > error >> > above. >> > >> > The thing is, msrepl_tran_version is the same on both the publisher and >> > the >> > subscriber. I have tried everything. I've rebuilt the Subscriber >> > triggers, >> > I've rebuilt the Publisher update SP, I've dropped and re-created the >> > article. >> > >> > The intersting thing is when I remove 'sp_MSsync_upd_trig_' from the >> > subscriber it works one time, but fails to update msrepl_tran_version >> > on >> > the >> > publisher leaving the 2 articles out of synch and the next update fails >> > (as >> > it should). >> > >> > Any thoughts before I give up and try merge replication instead? >> > >> > I'm running SQL Server 2k SP4 on both machines. OS is Windows Server >> > 2k. >> > >> > Cheers. >> >> >>
It was a no-sync subscription. I find them to be the quickest way to get
replication going on a large and complex database. I have since dropped and re-created the table at the subscriber that wasn't updating properly and this seems to have cured the problem. It was a real pain as I had a lot of ref integrity to tear down and re-create in order to achieve this. I can only guess that soemthing had gone awry in the system tables regarding this object. Thanks for your time. Regards, Pascal. [quoted text, click to view] "Hilary Cotter" wrote:
> Let me see if I understand what you did. You created a publication on your > publisher. You backed up the publication database, your restored the backup > of the publication database on the subscriber (hopefully at that time no-one > was working on the publication database), and then you created your > subscription? Was it a sync or a no sync subscription? Your chances of > having this work successfully would be if you did a sync subscription (i.e. > the subscriber does not have the schema and data in place option). > > I would advise you to drop and recreate the subscription and push it again, > again making sure no-one was working on the publication database while you > are doing this. > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Pascal" <Pascal@discussions.microsoft.com> wrote in message > news:9EA15FAA-8398-42BC-99C3-736EC1EFF99C@microsoft.com... > > It was a manual synchronisation. Published - Backed-up - Restored to > > Remote > > Server (on same lan) - Pushed the Subscription out - Applied > > synctran_commands from the publisher to the subscription manually. > > > > THe distributor is on the publisher server. > > > > I am updating a row via QA calling an update SP. > > > > When the rows are synched the update to the subscriber succeeds, so does > > the > > update at the publisher, but msrepl_tran_version remains the same at the > > publisher. It is not getting updated to the version on the subscriber. > > > > If I publish out the table to another empty database and allow the > > snapshot > > agent to re-create the table and apply the schema and data it works fine. > > However I don't see any differences in the SPs/Triggers that are created. > > > > Hope I'm making sense. > > > > Cheers. > > > > > > "Hilary Cotter" wrote: > > > >> How did you set this guy up and how are you modifying the row? BCP, DTS, > >> or > >> a direct update/insert/delete? > >> > >> -- > >> Hilary Cotter > >> Director of Text Mining and Database Strategy > >> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > >> > >> This posting is my own and doesn't necessarily represent RelevantNoise's > >> positions, strategies or opinions. > >> > >> Looking for a SQL Server replication book? > >> http://www.nwsu.com/0974973602.html > >> > >> Looking for a FAQ on Indexing Services/SQL FTS > >> http://www.indexserverfaq.com > >> > >> > >> > >> "Pascal" <Pascal@discussions.microsoft.com> wrote in message > >> news:7A76A241-D091-441A-9A3A-0FB57CBE1AC4@microsoft.com... > >> >I have a transactional updatable subscriber database that works fine for > >> >all > >> > articles (164 of them) apart from one where I continuously get the > >> > error > >> > above. > >> > > >> > The thing is, msrepl_tran_version is the same on both the publisher and > >> > the > >> > subscriber. I have tried everything. I've rebuilt the Subscriber > >> > triggers, > >> > I've rebuilt the Publisher update SP, I've dropped and re-created the > >> > article. > >> > > >> > The intersting thing is when I remove 'sp_MSsync_upd_trig_' from the > >> > subscriber it works one time, but fails to update msrepl_tran_version > >> > on > >> > the > >> > publisher leaving the 2 articles out of synch and the next update fails > >> > (as > >> > it should). > >> > > >> > Any thoughts before I give up and try merge replication instead? > >> > > >> > I'm running SQL Server 2k SP4 on both machines. OS is Windows Server > >> > 2k. > >> > > >> > Cheers. > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |