Solved

2-way synchronization between 2 SQL tables on different servers

Posted on 2008-06-18
1
550 Views
Last Modified: 2009-07-29
In searching, I've seen similar questions, but not specific to my situation. I have a SQL 2005 Database with a Access front-end. I would like to make some of the data available to people via a web site. The issue is that I don't want the web server hitting the same box that holds the in-house SQL database. For security, I'd rather have that on a different box, which I have. The data could be modified by either the web client or by a user using the front-end Access database (could be modified on either SQL Server). So I have 2 questions:

1) I havn't spent much time with Replication and I know some people like to stay away from it. What do I use in SQL to do this and are there any issues I should be aware of. I assume Merge Replication would be the way to go, but I'm conserned about simultaneous edits to the same record. What happens in a replication conflict? Do I need a Merge Replication Publication and Subscription on both servers to do this?

2) Is this the best way to handle this situation? What do you folks do? Use one database server for both web users and in-house users? Am I overly security paranoid and just asking for trouble with Replication? A quick upgrade to 2008 is an option, does that help me any in regards to this problem?

Thanks in advance. I'm looking more for advice and a proper direction, so please excuse all the questions.
0
Comment
Question by:bandriese
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 143

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 500 total points
ID: 21819332
>I assume Merge Replication would be the way to go
yes, it's the easiest.

>but I'm conserned about simultaneous edits to the same record.
that's the replications conflict resolution mechanisms you need to configure, to indicate which update will "win".
note: having 2 replicated databases or 1 database is mainly the same "problem", just that when person B updates the same record 1 second later than person A, the changes of person A are overwritten.


do you really expect 2 persons to edit the same record (I mean, from the "business" model?)

you could of course to your home-made solution, but it will end up with the same tricks/hacks for the same problem the replication exists...
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Viewers will learn how the fundamental information of how to create a table.

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question