Reducing SQL Server Sync I/O Contention :: Tip 5

Trident Submarine

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 time, then you can derive greater … Read more Reducing SQL Server Sync I/O Contention :: Tip 5

Reducing SQL Server Sync I/O Contention :: Tip 4

Add Filter

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 … Read more Reducing SQL Server Sync I/O Contention :: Tip 4

Reducing SQL Server Sync I/O Contention :: Tip 3

Primary Key

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.

Reducing SQL Server I/O Contention during Sync :: Tip 2

Database Storage

All DBAs know that Joining tables on non-indexed columns is the most expensive operation SQL Server can perform.

Reducing SQL Server I/O Contention during Sync :: Tip 1

SAN Storage

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.