Subscriber bloating when VarDecimal Compressed settings not transferred

Share this Post

When using compressed “VarDecimal Storage Format Enabled” on Transactional or Merge published tables you’ll discover this setting is not applied to subscribers leading to table bloating.

Database Properties

Table Properties

Try This: Publish table with varDecimal

Observe the subscriber is not created with compressed vardecimal storage resulting in additional storage requirements on subscriber for the same data on publisher.


  1. Pre-create the tables on Subscriber with identical schema as Publisher.
  2. Change publication setting under Article properties from “Drop and Create” to “truncate only”, then push down a new Snapshot. This ensure new data is pushed down when Subscriber is initialized or re-initialized however table schema is left unchanged.

However, having a table set to not replicate schema requires you to manually change Subscriber’s scheme should published table schema change. Another option for Transactional Replication is to setup the subscribers using Backup\Restore. This ensure the Subscribers have identical schema settings as Publisher. This comes with its own trade-offs. Lean more on and at

Share this Post

About: ReplTalk

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.