SQL Server Performance

Size of the queue in Transactional Replication

Discussion in 'Performance Tuning for SQL Server Replication' started by shantaram, Mar 19, 2006.

  1. shantaram New Member

    Hi <br />In addition to my previous query, I wud also like to know the number of transactions possible(size of the queue) in transactional replication with queued updating. That is I want to know how many tranactions can be stored in a queue without loss of data when the connection between the Publisher and Subscriber is not there.<br />Anyone on this please?...[<img src='/community/emoticons/emotion-1.gif' alt=':)' />]<br /><br />Regards<br />Shantaram
  2. satya Moderator

  3. shantaram New Member

    Hi Satya
    Thanx for the reply....I'll try to make the question simpler...
    In case of transactional replication, when there is no connection between the publisher & the subscriber how many transactions can get stored in a queue without any of the transaction getting lost till the time the connection is regained.
    Hope now the question is more clear.
  4. satya Moderator

    I guess that depends on the memory available to SQL server and in order to continue the transactions there shouldn't be any interruption between the servers.

    Refer tohttp://msdn.microsoft.com/library/d...patterns/html/ImpTransactionalReplication.asp about implementing master-slave type of replication that may be suited to the current issue.


    Satya SKJ
    Contributing Editor & Forums Moderator
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page