Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

2-way synchronization between 2 SQL tables on different servers

Posted on 2008-06-18
1
Medium Priority
?
554 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 1500 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

Moving data to the cloud? Find out if you’re ready

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

Question has a verified solution.

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

I have a large data set and a SSIS package. How can I load this file in multi threading?
Ready to get certified? Check out some courses that help you prepare for third-party exams.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

688 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