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.
Important retention difference
Tier 1 retention is repository-wide for SQL Server Queue V2. Every channel group that uses the same SQL Server V2 repository receives the same hot-storage retention. PostgreSQL can apply different Tier 1 retention values to different groups within one repository.
This is usually manageable because completed SQL Server partitions can be moved to Tier 2 for long-term, queryable storage. If groups require materially different Tier 1 retention windows, use separate SQL Server V2 repositories or PostgreSQL.
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.
Double the speed (or more) in internal synthetic tests.
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.