Sql – Getting Started with Sync Framework

databasemicrosoft-sync-frameworknetsql server

I'm having some trouble getting started with the Sync Framework. In doing research, it looks like the Sync Framework is a better fit for what we need than replication or a custom-rolled solution.

Basically, we need to keep some datasets synced from our central office with every store in the company to overcome shortfalls with crappy DSL service and bad wiring.

Anyway, I've read through the MSDN articles on SQL Server syncing with the Sync Framework, and looked at some of the example projects they provide, and I'm still at a loss as to where to start.

I really would like to see just an outline of the process that an app we write would have to go through to register with the central office, pull down the initial dataset, and then stay synchronized.

In summary, I'm looking for an outline of how to two-way sync a client SQL Server Express instance with a SQL Server Enterprise instance.

Best Answer

If you are looking for an introduction to what the sync services are capable of, you can do worse than watch Microsofts Daniel Moths 18min intro video at http://channel9.msdn.com/posts/DanielMoth/ADONET-Sync-Services-v10/

Your biggest problem is making sure, when designing your databbase, that you can partition the data into sections that can be syncronised to different locations easily. E.g. contacts to sales people and not having overlapping contacts...

Syntax:

ALTER TABLE {TABLENAME} 
ADD {COLUMNNAME} {TYPE} {NULL|NOT NULL} 
CONSTRAINT {CONSTRAINT_NAME} DEFAULT {DEFAULT_VALUE}
WITH VALUES

Example:

ALTER TABLE SomeTable
        ADD SomeCol Bit NULL --Or NOT NULL.
 CONSTRAINT D_SomeTable_SomeCol --When Omitted a Default-Constraint Name is autogenerated.
    DEFAULT (0)--Optional Default-Constraint.
WITH VALUES --Add if Column is Nullable and you want the Default Value for Existing Records.

Notes:

Optional Constraint Name:
If you leave out CONSTRAINT D_SomeTable_SomeCol then SQL Server will autogenerate
a Default-Contraint with a funny Name like: DF__SomeTa__SomeC__4FB7FEF6

Optional With-Values Statement:
The WITH VALUES is only needed when your Column is Nullable
and you want the Default Value used for Existing Records.
If your Column is NOT NULL, then it will automatically use the Default Value
for all Existing Records, whether you specify WITH VALUES or not.

How Inserts work with a Default-Constraint:
If you insert a Record into SomeTable and do not Specify SomeCol's value, then it will Default to 0.
If you insert a Record and Specify SomeCol's value as NULL (and your column allows nulls),
then the Default-Constraint will not be used and NULL will be inserted as the Value.

Notes were based on everyone's great feedback below.
Special Thanks to:
@Yatrix, @WalterStabosz, @YahooSerious, and @StackMan for their Comments.

Using MS Sync Framework to synchronize two SQL CE Dbs

Sync Framework 2.0 allows synchronization between SQL Server Compact Edition databases.

SqlCeSyncProvider is used to synchronize SQL Server Compact databases.

This provider can be used to synchronize with a central server but also has the ability to synchronize with other clients, which is not possible with SqlCeClientSyncProvider. This ability enables developers to target new scenarios such as a collaboration scenario in which teams of people need to synchronize among each another in the absence of a connection to a central server.

Best Answer

Related Solutions

Sql – Add a column with a default value to an existing table in SQL Server

Syntax:

Example:

Notes:

Using MS Sync Framework to synchronize two SQL CE Dbs

Related Topic