SQL Replication

Hot Topic

SQL 2005 SP1 CTP - Bug Reports
SSIS Performance Throttling?
Copy Table from another table
Conditional calculated member
New installation https issue
How to retrieve data from query and link the data to a data number?
Upsizing Access 2003 database to SQL Server Express
A/Synchronous execution of SSIS ETL packages
SSIS Delete/Insert/Update
Choosing explicit cell in Excel to SQL Database

SQL Server

Error CS2001 & CS2008
UK Datetime parameter problem SQL 2005 RS
The media set has 2 media families but only 1 are provided.
Suggest Column Types
Pre execute Failure on Look up task
Problem: FILEGROWTH of 100 MB set to 12800% on restart
SQL 2000 alongside SQL Express?
About reinitializing ....
MDAC won't play
Multithreaded run of SSIS packages

SQL Replication

I have an end-user question about what replication solutions are available in SQL 2005 for the following configuration. We are looking for a replication option that will allow instant replication of changes made to the database at a remote office with a WAN connection. This is a manufacturing operation and the aplication in use requires those changes to be instantly replicated to the primary SQL server located in the data center.

The vendor that supports our application has never had an instance where there was a WAN separation between the application and the database (we run the application through Citrix/Terminal Services) and has yet to attemt an installation using replication.

What replication options should we consider and what type of overhead will it require in terms of bandwidth to support live replication of the database. I know there are a million variables that come into play here, but if there is a general direction anyone could point me in I would certainly appreciate it.

Thank you!






Answer this question

SQL Replication

  • Jerome Bonnet

    In looking around the site it seems that Merge replication is what we are looking for, but most of the scenarios I read did not require the changes to be replicated instantly which is what we are looking for. This is not a massive database supporting thousands of users.. it's about a 2GB database supporting 25 users.





  • Ralph Perkins

    You can look at Transactional Replication with updating subscriber scenario. Immediate Updating subscriber can work, although if the line between the subscriber and distributor goes down, all changes at the subscriber will fail until the line is up and running. Changes at the distributor will queue up until line is up and running.

    If you have SQL 2005, and you have Enterprise Edition, you can also take a look at Peer-to-Peer.

  • Tore Bleken

    are changes flowing one way If so, transactional replication seems better suited.

  • Lasha

    Changes will be going both ways... all scheduling and job detail is updated on one end and the production data updated on the other.
  • SQL Replication
Answer this question