I have been working in VB6 to VB.NET migration project.In VB6 project they have individual databases (access db .mdb) for every user now we made that to centralized database using SQL Server.

In the old application we have a MasterDB.mdb which is in sync with the local.mdb. Some times we need to sync with both the users of local.mdb. After a particular interval of time we need to sync with the MasterDB.mdb.

We need to do this in SQL Server. So, I have a done more analysis related to SQL Server. I read a MSDN forums and many articles related to replication in SQL Server (Related Scenario). I think that merge replication matches to my requirements.

Can anyone suggest whether I have chosen the correct replication? Do we have any environment changes to set up this replication?

  • Just to be clear, what is the strategy to migrate from Access to SQL Server? Separate databases, I assume? The topology of your system isn't clear from the question text. – Jon Seigel Mar 11 '13 at 14:38
  • Client wants to migrate the DB part to SQL Server also. So he wants to do the replication process in SQL Server also . – Hemant Kumar Mar 12 '13 at 5:16
  • 1
    That's my question. Is there actually a need/requirement to use replication, instead of a single database across the entire application? – Jon Seigel Mar 12 '13 at 13:51

To reinforce what Jon says - a single DB to which all clients connect all the time, with the schema designed accordingly, will be a much better solution. You only need replication in a few circumstances. One is if a client machine must be able to work while disconnected. Another will be if there are huge latency issues between your various sites. Replication, especially two-way merge replication, can be a huge pain - during upgrades, for example.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.