SQL Server Performance

Replication stopped

Discussion in 'SQL Server Clustering' started by TRACEYSQL, Mar 19, 2007.

  1. TRACEYSQL New Member

    We have two servers Clustered together for SQL 2000

    We have replication from Each of the servers

    Does anyone know what protocol its using for replication is it using TCP/IP

    Is there a way to replicate the data using the heartbeat between the two SQL Servers

    (We currently have our replication down and i was trying to figure out the why i can't reach the server. I can ping sql1 to sql2 and vice versa)

    Any one got any ideas
  2. MohammedU New Member

    I believe it will use TCP/IP unless it is changed in CLIENT NETWORK UTILITY....

    Why do you want to use HEARTBEAT for replication?
    What is the error you are getting?
    Are you able to run linked server queries?

  3. TRACEYSQL New Member

    I got it working now i increased the timeout errors from 300 to 3000 that worked.
    I was wondering if i could do nic to nic rather than TCP/IP where all the other traffic emails etc are occuring.
  4. MohammedU New Member

    I don't think it is going to improve anything even if you do NIC to NIC configuraton change because generally you get these type of TIMEOUT error when there are many changes and/or blocking.

    I have not done NIC to NIC...
    I do replication from East coast to West Coast without any issues...

  5. TRACEYSQL New Member

    Thanks i think i revisit my settings, it has worked for a long time then all of sudden failed must be replicating more data

  6. MohammedU New Member

  7. TRACEYSQL New Member

    Thats a good thread thank you

Share This Page