StandbyMP 12.3 delivers significant improvements in performance and scalability for SQL Server disaster recovery, particularly in environments with many databases, while also delivering important performance enhancements for Oracle and PostgreSQL.
With SQL Server adoption of StandbyMP growing by almost 300% in the past year, 12.3 represents our next step in supporting teams that need reliable, high-performance database continuity at any scale. This follows the key additions last year, such as scheduled read-only access.
StandbyMP 12.3 introduces several under-the-hood improvements that directly address operational challenges faced by DBAs managing large SQL Server estates.
Improved load-management logic prevents overloading busy SQL Server instances. This is especially important when managing many databases or performing bulk DR operations in active environments.
Query batching and engine optimisations significantly reduce the time required to create and manage large numbers of standby configurations. For partners and customers with larger environments, this results in faster rollouts and more predictable deployments.
Support for SQL Server native backup compression reduces network usage and storage overhead, particularly in environments with large databases or constrained bandwidth.
StandbyMP 12.3 improves how the platform behaves day to day when managing hundreds of databases. Multi-database actions execute more efficiently, and routine operational tasks scale cleanly as environments grow.
These enhancements benefit every StandbyMP user across SQL Server, Oracle, and PostgreSQL, making upgrades to 12.3 a strong recommendation for all environments.
StandbyMP is designed to provide enterprise-grade database continuity without the cost, complexity, or constraints of native SQL Server high availability and disaster recovery options.
SQL Server Log Shipping becomes difficult to manage as database counts grow and offers limited operational control, with no true switchover or switchback and frequent standby rebuilds during troubleshooting.
StandbyMP addresses these limitations with intuitive multi-database actions, advanced functionality such as switchovers and automated failovers, and one-click re-synchronization without rebuilding the standby.
Basic Availability Groups are limited to one database per availability group, making larger environments harder to manage and scale.
StandbyMP enables efficient disaster recovery for hundreds of databases while remaining on SQL Server Standard Edition, helping organisations minimise licensing costs without sacrificing capability.
Windows Server Failover Clustering introduces complexity and risk, particularly in existing environments.
StandbyMP requires no clustering, is typically deployed without disruption, and allows existing Log Shipping environments to be migrated without rebuilding the standby database.
Synchronous Availability Groups struggle with latency, while asynchronous configurations lack key operational features.
StandbyMP is designed for reliable operation across long distances, supporting less-than-ideal network conditions and enabling geographically dispersed standby sites for increased resiliency.
Native SQL Server HA and DR technologies require significant expertise to deploy and maintain.
StandbyMP reduces this burden through fully guided standby configuration, one-click actions with built-in pre-checks, and access to 24/7 DBA support.
Whether you are a partner, an existing customer planning an upgrade, or new to StandbyMP, version 12.3 represents a meaningful step forward for SQL Server disaster recovery, particularly in environments operating at scale. Please ensure you review the release notes, OS and database support, and installation guidance in the user manual prior to installation.
📘 Read the Technical Release Notes