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.