by Holger Linke, Microsoft SQL Escalation Engineer GUIDs and Clustered Indexes 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
Read More »
You can use SQL Server Replication technologies to move data between local on premises SQL Server to SQL Server running in Windows Azure Virtual Machines or between Windows Azure Virtual Machines. Similar to move data between non-trusted corporate domains, keys are 1) use SQL Server Authentication and 2) configure a client alias for the server
Read More »
“The row was not found at the Subscriber when applying the replicated command.” errors reported by the SQL Replication Distribution Agent can often be some of the hardest issues to troubleshoot. With great satisfaction I was able to uncover this mysterious error for one of my customers. In the customers SQL Replication topology they’re consolidating
Read More »
Abstract Many technology solutions use a STORE and FORWARD model to move data though out the business. It begins when source data change is detected, collected, and STORED in a cache. This cache data, often on a schedule, is processed and FORWARD to one or more destinations. Microsoft technologies using “store and forward” include Log
Read More »
How to Archive your SQL Errorlogs into a Table Chris Skorlinski Microsoft SQL Server Escalation Services Have you noticed your SQL Server errorlogs taking up a lot of disk space? Ever wonder what was logged a few weeks ago, but the logs have already rolled over? Why not create a SQL Agent job and archive
Read More »