SQL Server Performance

Newbie Replication question

Discussion in 'Performance Tuning for SQL Server Replication' started by whiteboy, Sep 10, 2003.

  1. whiteboy New Member

    Hi all<br /><br />We're proposing a solution for a customer at the moment. They currently have a SQL server that they run their internal product system from. <br /><br />They want the information from this system to be made available to an extranet to be hosted locally. We initially proposed that we would export the required information from their current server to a web/sql server overnight. <br /><br />They have asked if their data could be realtime. They want the web server to mirror the current server.<br /><br />We would still propose two servers because of the potential strain on the current server.<br /><br />So my question is, what sort of work does SQL have to do, and what sort of strain on their network will their be, if SQL is synchronising all day.<br /><br />Would Transactional replication be the best way? Does this lock the database whilst it is updating? If so, the web server is locked out too isn't it?<br /><br />I don't like the sound of it!<br /><br />Cheers<br /><br />Gareth <br /><br />p.s. be gentle, its my first post [<img src='/community/emoticons/emotion-5.gif' alt=';)' />]
  2. satya Moderator

  3. Twan New Member

    Transactional replication would be great, although not 100% real time. You are not planning to do any updating from the extranet? How much data is updated internally and is it regular or large batches?

    The replication work does lock rows as any other process would, but it is all based on primary keys so will be fast. We use transactional & merge replication here and have not had any problems to date.


Share This Page