July 15, 2014 at 7:12 am
I can't find any other posts on this subject so I thought I would start one as a placeholder and float some ideas.
I understand that proprietary SQL Server Replication is not possible to/from Azure SQL Database due to obvious reasons (no local MSDB DB or SQL Agent for example).
My best solution so far is for an intermediary SQL Server sitting inside an on-premise DMZ to move data in and out using SSIS Packages. This solution relies upon 'duplicate' licensing which almost makes the cloud-concept academic however, plus at least a working knowledge of SSIS.
Alternatively an Azure SQL Server VM (Iaas) with the necessary VPN configured to connect to on-premise servers using Domain credentials. Again, this negates the WASD (PaaS) concept.
July 15, 2014 at 9:46 am
...is there any news on SQL Data Sync? I can find old postings on TechNet and MSDN but cannot see any sign of that functionality within the Portal. I guess another feature retired before it lived?
July 15, 2014 at 10:25 am
The only way I know of that you could currently do this would be to build it yourself. Whether you use SSIS or not is something of a discussion point, but it'll have to be an external application because there's nothing within the direct Microsoft Azure SQL Database stack to support it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 15, 2014 at 7:12 pm
SQL Swerver (7/15/2014)
...is there any news on SQL Data Sync? I can find old postings on TechNet and MSDN but cannot see any sign of that functionality within the Portal. I guess another feature retired before it lived?
It's called Sync Framework now. I tried to use it instead of replication for some local servers and if you do the same on anything more than the barest quantity of data you're going to have an extremely bad time. It's really designed for synchronising tiny amounts of data to mobile/tablet clients and it's quite a pain to work with (I was using PowerShell).
July 16, 2014 at 4:57 am
Good call, thanks Cody K for the insight!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply