Synchronization In Sql Server

Question

0.00/5 (No votes)

See more:

I have come across a new task where in i have to upgrade my application such that when the entries are made in any of the databases located at remote site, the data must be updated at the main server. The detail problem is like we want to design the system such that the user is unaware about the connectivity of the database he just has to use the application for his work. so I want to implement such design where the data entered is always updated on the server database. The ways I thought for is the online and offline connection. Offline connection is important as there is no guarantee of having the Internet connection on every site at every time so even if there is no internet connection the user can use application and can then connect to the server at a scheduled time for updating the data at the server. I thought of restoring the database, but this can't be done everyday as the size of database will be increasing every moment. So I need to find out ways of implementing such design where the user is free from the updating purpose, the data automatically gets updated at scheduled time(in offline mode) and keeps on updating continuously when it is connected(in online mode).
For example the emails, Train tickets reservation, etc.

So can any one give any insight on this please?
Thanks in advance

Posted 5-Feb-13 17:39pm

kunal jangade

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CHill60 · Answer 1 · 2013-02-06T00:00:00

Having done something similar a few years ago I can tell you that this is not a nice task!
Much will depend on which version of SQL-Server you are using - the tools have been getting better. Another key point is whether or not the data is shared - in other words if the same rows can be updated at any of the locations then the task is far more complicated.

However here are some starting points ...

Transactional Replication is a key phrase for your research - Microsoft article can be found here[^] and another here[^]

If you are using SQL 2005 then this detailed how-to[^] will be useful

SQL2008 upwards see this article[^] which uses Sync and includes a code sample.

Depending on your budget and expertise, my advice would be go for a third-party out-of-the-box solution rather than trying to write/configure something yourself - here's an example product from Red-Gate[^]

Good luck