REPLICATION: Load Test Platform for Merge Replication

Zen4Sync is all about providing an Orchestration and Load Test platform able to validate any SQL Server Merge Replication based Architecture. http://zen4sync.codeplex.com/

0

Replication: Watch out for STREAM_BLOB_COLUMNS when setting up replication on your SQL 2008 + server

When setting up merge replication on your SQL 2008 + server, please be careful with the parameter STREAM_BLOB_COLUMN. By default, this option is set to FALSE, as explained here in BOL:  [ @stream_blob_columns= ] ‘stream_blob_columns’Specifies that a data stream optimization be used when replicating binary large object columns. stream_blob_columns is nvarchar(5), with a default of…

0

Replication: If sql_variant column includes a value with new datetime type, the value is replicated as base type nvarchar even if schema option 0x200000000 is not set

Problem: If sql_variant column includes a value with new datetime type, the value is replicated as base type nvarchar even if schema option 0x200000000 is not set during the application of the SNAPSHOT (only). After the snapshot has been applied, if you execute the command to verify the property of the sql_variant column: SELECT SQL_VARIANT_PROPERTY(column_name,‘BaseType’),…

0

Replication: XML data loss occurs when Merge agent fails with Violation of Foreign Key

Problem: Consider the following scenario: You use a merge publication operation to replicate XML data in Microsoft SQL Server 2005, in Microsoft SQL Server 2008, or in Microsoft SQL Server 2008 R2. A foreign key violation error occurs in the same merge replication batch. In this scenario, you may find the merge replication fails and…

0

Replication: What is the difference between Database Compatibility Mode and Publication Compatibility Mode

Database Compatibility Mode: Compatibility level affects behaviors only for the specified database, not for the entire server. Compatibility level provides only partial backward compatibility with earlier versions of SQL Server. Use compatibility level as an interim migration aid to work around versiondifferences in the behaviors that are controlled by the relevant compatibility-level setting.            In this…

0

Replication: Error "You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels" generated when altering published table columns

Problem:   Error “You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels” generated when altering published table columns in a transactional replication. Cause:   Unable to alter columns on Published database if using any isolation level besides the READ COMMITTED or REPEATABLE READ isolation level. READPAST hint is not…

0

Replication: Merge Performance Tip

Problem: Publisher: SQL Server 2008 Subscriber: SQL Server Compact 3.5 Merge Replication Performance issue when using keep_partition_changes or precomputed partitions   Cause:   There could be many causes to this and analysis would have to be done however sometimes it may be due to missing indexes.   Solution/Workaround:   In a test environment, use the following…

0

Replication: Fake Conflicts?

One problem that is hard to resolve / understand is fake conflicts within a merge replication topology.   Looking at a scenario in which fake conflicts were occurring, we saw that following:   Our affected subscriber is synchronizing with 2 publications that have retention=14. The publisher also has an additional publication with retention=30. All the…

0

Note to all Readers

Seems like there was an issue with the comments for this blog – I wasn’t getting notified and hence never got to respond. My apologies to all those that commented and never got a reply. If you do have a comment, please do not hesitate to e-mail me by selecting “e-mail Blog Author” Thanks!  

0