Tag: Merge Replication
In this third article on building Microsoft MEAP, I’ll show you how to Shard your SQL Server 2012 database using Replication to create a Shared Nothing data architecture to support Internet-scale mobile solutions. In the previous article, I discussed Gartner’s Enterprise Application Integration Tools (EAI) critical capability for building a Mobile Enterprise Application Platform (MEAP) using Microsoft […]
Hey folks, just wanted to let you know that cumulative update package 7 for SQL Server Compact 3.5 Service Pack 2 has been released to the web. You can download the new bits over at http://support.microsoft.com/kb/2665342. This is a hotfix for an incorrect sort order for a subscriber in SQL Server Compact 3.5 SP2 that synchronizes with […]
Wow! Just opened a 1099 tax document for 2011 from Apress. People must still be buying my old books on eMbedded Visual Basic, the .NET Compact Framework 2.0, and SQL Server Compact 2.0. The Pocket PC and Windows Mobile live on! A separate 1099 for Hood Canal Press tells me that my SQL Server Merge […]
Today’s tip is an easy one. When it comes to delivering server solutions with Windows Server and SQL Server, speed is your friend (as we used to say in the submarine service). More speed means more things can happen in a given period of time. If more things can happen in a given period of […]
One of the features that makes SQL Server Merge Replication superior to other sync technologies is something called Precomputed Partitions. SQL Server creates and maintains distinct data partitions/subsets for each unique user or other type of filter value. Other sync technologies figure out “what’s-changed” on the fly when a Subscriber synchronizes. This means all change-tracking […]
Uniqueness is a key factor when synchronizing data between SQL Server/Azure and multiple endpoints like Slates and Smartphones. With data simultaneously created and updated on servers and clients, ensuring rows are unique to avoid key collisions is critical. As you know, each row is uniquely identified by its Primary Key.
All DBAs know that Joining tables on non-indexed columns is the most expensive operation SQL Server can perform.
The act of tracking changes made by each SQL Server Compact or Silverlight sync subscriber can cause a lot of locking and blocking on the server.