Share this PostReplTip – Bulk Updates with Transactional Replication by Taiyeb Zakir We’re seeing several customers performing bulk updates on the Publisher. Consider for example a table with 10 rows and 2 columns C1 and C2 and we run this update. Update table set C1 = “Something” This updated 10 rows as one set, but
Read More »
Share this PostYou 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
Read More »
Share this PostHolger Linke Microsoft SQL Server Escalation Services Abstract Provides details and explanations why SQL Server Merge Replication does not support central subscriber topologies. This fact was originally stated in SQL Server Books Online and further documented in KB article KB 2750005, but is still causing some misconceptions and confusion. This blog article will
Read More »
Share this PostJose Moreira B. Neto Microsoft SQL Server Escalation Services From SQL Server BOL we have: -ReadBatchSize Is the maximum number of transactions read out of the transaction log of the publishing database per processing cycle, with a default of 500. -MaxCmdsInTran Specifies the maximum number of statements grouped into a transaction as the
Read More »
Share this PostAbstract 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”
Read More »