Sync Team Blog - All Comments

re: SQL Data Sync Preview December Service Update Is Now Live!

New Portal still not showing Sync (as at 17May2013) — Fri, 17 May 2013 01:50:30 GMT

Today I noticed the old portal is no longer working and the new portal is not showing sync. So now I have no way on monitoring my syncs.... I understand this is still preview and love what it is doing for us and think you have done an amazing job. Don't let the management portals be the reason we don't use it.

re: SQL Data Sync Preview December Service Update Is Now Live!

Nicholas Rogoff — Fri, 03 May 2013 10:54:42 GMT

That's great and it's getting better, but please don't discontinue the Silverlight UI just yet. There are many functions still either not available or not working on the new portal.

I can't get access to logs, or see the schema that an agent reports etc..

Also when are you going to let us delete an agent that no longer exists. I can't imagine why this is such a problem?

re: Synchronization Services for ADO .NET for Devices: Improving performance by skipping tables that don’t need synchronization

Anandhavel — Wed, 10 Apr 2013 14:01:41 GMT

Hi Sreedhar,

Can u provide us a sample application please. It would be really helpful for us.

Email: anand21cen@gmail.com

re: SQL Server to SQL Azure Synchronization using Sync Framework 2.1

JuneT — Sat, 30 Mar 2013 04:33:55 GMT

yes, you have to do the PerformPostRestoreFixup before the synching the restored database for the first time. and yes, that's the code for doing it.

re: SQL Server to SQL Azure Synchronization using Sync Framework 2.1

Sea Dog Mariner — Tue, 26 Mar 2013 15:48:10 GMT

JuneT:

I guess I'd be looking for the vb equivilant of Liam's C# code below:

SqlConnection serverConn = new SqlConnection();

serverConn.ConnectionString = "Data Source=localhost;Trusted_Connection=True;Database=MYDATABASE";

SqlConnection.ClearPool(serverConn);

SqlSyncStoreRestore databaseRestore = new SqlSyncStoreRestore(serverConn);

databaseRestore.PerformPostRestoreFixup();

Since you mention a chance of sync ID issues without this procedure, I want to make sure we get it correct.

re: SQL Server to SQL Azure Synchronization using Sync Framework 2.1

Sea Dog Mariner — Tue, 26 Mar 2013 15:33:26 GMT

JuneT:

Do you have a sample of PerformPostRestoreFixup in vb code? The WF for the attach/detach action is in vb, while the WF for the provision/sync action is in C#.

re: SQL Server to SQL Azure Synchronization using Sync Framework 2.1

Sea Dog Mariner — Tue, 26 Mar 2013 04:04:28 GMT

Still a work in progress. I had used PerformPostRestoreFixup in some previous trials when working on Liam’s blog “How to Synchronize Multiple Geographically Distributed SQL Server Databases using SQL Azure Data Sync”, but since removed it from my code. So I assume that this must be accomplished immediately after db file is attached at RemoteOffice and before it is synced to Azure?

re: SQL Server to SQL Azure Synchronization using Sync Framework 2.1

JuneT — Fri, 22 Mar 2013 12:30:42 GMT

@Sea Dog Mariner,

are you running PerformPostRestoreFixup on for every copy of the original database that you are re-attaching?

re: SQL Server to SQL Azure Synchronization using Sync Framework 2.1

Sea Dog Mariner — Thu, 21 Mar 2013 19:57:35 GMT

OK- so I answer my own post...

Further diagnosis and trials lead to a very simple answer.

Only need to provision the first Instance. Then sync.

Then detach and copy the applicable .mdf/.ldf files to a new directory. Reattach the first Instance and then attach the copied .mdf file in the new directory to a second Instance. There is no need to provision the second Instance again - it is already provisioned. Just complete a sync.

The first Instance and second Instance will now sync via the SQL Azure db.

You can add as many remote site syncs as required using this method.

re: SQL Server to SQL Azure Synchronization using Sync Framework 2.1

Sea Dog Mariner — Fri, 15 Mar 2013 16:44:12 GMT

Thanks JuneT for steering me in the right direction (previous post). Thanks Liam for a detailed article.

I have successfully followed your article and am using Sync Framework 2.1 as you have outlined to sync between a SQL Server 2012 instance and SQL Azure.

SQL Server db provisions and syncs fine to SQL Azure db (Azure obviously provisions fine also)

I want to now add other SQL Instances of the same database name to sync similarily to your article: How to Synchronize Multiple Geographically Distributed SQL Server Databases using SQL Azure Data Sync - Sync Team Blog - Site Home - MSDN Blogs.

When I copy the db (before it has been provisioned as per your Sync Framework 2.1 article) and then run the provision/sync code to sync a second remote db, I receive text in console as follows:

Provisioning SQL Server...

Done Provisioning SQL Server...

SQL Azure already provisioned....

Then when I try to sync the 2nd db SQL Instance, I receive text in console as follows:

ScopeName=ALLTABLESSYNCGROUP

Starting Sync 3/14/2013 8:20:10 PM......

and then nothing. It just seems to lock (or end), with no end result.

I have also applied your "Changes Applied event fired" code as I was previously timing out (db about 650,000 records). First sync to fresh Azure db takes about 30 minutes. Subsequent syncs takes 15 seconds. I have left the 2nd db trying to sync for several hours, but still no "Changes Applied event fired" notice (and no movement).

Any further insight on adding additional SQL Server instances to sync scenario as described in: SQL Server to SQL Azure Synchronization using Sync Framework 2.1?