SQL Server Queue V2
SQL Server Queue (V2)
Connexion v26 introduces a new SQL Server queue implementation designed for substantially higher throughput, predictable partition maintenance, and Tier 2 archiving. It is a full rewrite of the legacy SQL Server queue rather than an in-place schema update.
Group-specific retention
SQL Server Queue V2 and PostgreSQL both support group-specific partition intervals and Tier 1 retention. A group inherits its repository defaults unless an override is configured. SQL Server Queue V2 creates and retires each group's partition boundaries using that group's settings.
Retention is measured from the end of the partition. Queued or delayed work can keep a partition online beyond its normal retention window. When Tier 2 is enabled for the applicable data, archiving must complete before that partition is removed from Tier 1.
Why use Queue V2
The V2 queue replaces the legacy row-oriented hot path with a partition-aware and batch-oriented design. The principal improvements are:
Partitioned, so participates in tier 2/warm storage.
Less resource intensive.
Uses newer Sql Server features.
Higher processing efficiency through partition-aware, batch-oriented operations. Throughput gains depend on message size, database configuration and workload.
For new SQL Server message repositories, Queue V2 is the preferred production queue. The legacy queue remains available during migration, but it does not receive the partition-dependent capabilities of V2.