Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / August 2006

Tip: Looking for answers? Try searching our database.

Transactions done twice during failover

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Avi - 27 Aug 2006 08:57 GMT
Hi experts,

I'm running replication from SQL Server 2000 to Sybase.  Whenever I do a
failover from one node to the other I get duplicate rows.  That means that
certain transactions are done twice.

What can I do to avoid that?

Thanks a million,
Avi
Hilary Cotter - 27 Aug 2006 17:33 GMT
I suspect you need to put a pk on the Sybase tables to prevent this from
happening. If it is happening on the log reader agent writing to the
distribution database this is a known issue. When I encounter this I delete
the offending rows from msrepl_transactions and msrepl_Commands and have the
log reader send them again.

You might also want to use the continue on data consistency error profile.

Signature

Hilary Cotter
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

> Hi experts,
>
[quoted text clipped - 6 lines]
> Thanks a million,
> Avi
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.