StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POApproaches for Database Synchronization
primarykey
Id
12088313
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-23T09:08:16.660
FavoriteCount
0
LastActivityDate
2012-10-12T18:56:57.660
LastEditDate
2012-10-12T18:56:57.660
LastEditorUserId
1573118
OwnerUserId
1573118
ParentId
0
PostTypeId
1
Score
0
ViewCount
1092
LastEditorDisplayName
text
Body
I am currently been assigned to develop a sync application for my company. We have SQL server on our database server which will be synced with the client database. Client databases are not known, they can be SQLite or MYSQL or whatever. What this sync app does is, detect changes that occur on server & client databases. Save these changes and sync. If changes occur on server database it will be synced with the client database and vice versa. I did some research on it and came to know many solutions. One of them is to use a Microsoft Sync Framework. But I hardly found a good implementation example on it for syncing with remote databases. Then I came across Change Data Capture(CDC) on SQL Server 2008. CDC works by detecting the change on the source table through triggers and put these changes on a separate table called sync_table, this table is then used for syncing. Since, I cannot use the CDC feature because I don't have sufficient database rights on my machine, I have started to develop my own solution which works like how CDC does. I create separate sync_table for each source table, create triggers to detect data change and put this data in the sync_table. However, I am advised to do some more research on it for choosing the best implementation methodology. I need to keep the following things in mind, <ul> <li>Databases may/may not be on the same network.</li> <li>On server side, the user must be able to select which tables will take part in the sync process.</li> <li>Devices that will sync with the server database need to be registered first. Meaning that all client devices will be registered by the user before they can start syncing.</li> </ul> As usual any help will be appreciated :) 
Tags
<database><synchronization>
Title
Approaches for Database Synchronization
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USIbad
UserOwnerUserId
1. USIbad
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.