SQL Server 2016 has arrived with a host of new features and improvements that are tempting for businesses. However, before rushing to upgrade, it is important to consider the benefits and risks associated with adopting the latest release.

The Wisdom of Not Leading the Way

Many managers are cautious when it comes to upgrading software, especially a critical application-support product like SQL Server. The philosophy of running a version behind the latest release, known as “N-1,” is a risk management strategy that aims to prevent anomalies and downtime associated with unproven technology.

While the Community Technology Preview (CTP) releases of SQL Server help identify and fix issues before the final release, they are not comprehensive and do not reflect actual production workloads. Waiting until Service Pack 1 (or later) to upgrade to a new SQL Server version is a wise decision, especially when a company’s data is its most valuable asset.

The Wisdom of Using the New Version

Despite the cautionary approach of N-1, SQL Server 2016 introduces significant changes and features that can greatly benefit businesses. Dynamic data masking, Always Encrypted, and row-level security enhance data security, which is crucial for databases containing sensitive personal identifying information.

Another exciting feature is the ability to stretch SQL database tables into Azure, providing an archival solution that saves time for DBAs and developers. With these and other improvements, SQL Server 2016 offers compelling reasons to consider upgrading.

The DBA’s Conundrum and The Solution

For database administrators (DBAs), it can be challenging to balance the need for data safety with the desire to learn and utilize the latest SQL Server version. Creating a playpen environment, either on a spare server or using tools like Visual Studio with MSDN, allows DBAs to experiment with SQL Server 2016 without risking production data.

Once familiar with the new version, DBAs can create a presentation to justify the upgrade to management. It is essential to be transparent about the risks involved and provide a well-considered plan that includes hardware or operating system upgrades, estimated downtime, and testing in a lower environment.

Be Ready to Wait

While management may be receptive to the upgrade plan, they may also decide to delay until SQL Server 2016 reaches Service Pack 1. In such cases, it is important to remain patient and understand that the best IT managers prioritize risk management and stability.

Conclusion

There is wisdom in the N-1 approach to upgrading software, but there is also value in exploring and testing new releases and features. By creating a safe testing environment and presenting a well-justified upgrade plan, DBAs can demonstrate the benefits of adopting SQL Server 2016 while mitigating potential risks.

Remember, upgrading to a new SQL Server version should be a carefully evaluated decision that considers the importance of data security and stability for the business.

John F. Tamburo is the Chief Database Administrator for Landauer, Inc., the world’s leading authority on radiation measurement, physics, and education. You can find John on Twitter at @SQLBlimp and read his blog at www.sqlblimp.com.