Blog: How to test breaking changes and new features during the SQL Server upgrade

Database upgrade is inevitable if you’re running aging versions of your databases. Alongside with cool new features, the upgrade brings some code changes. Regardless of the severity of these code updates, you need a proven solution to test these code changes.

Let us consider a following case: after upgrading a SQL Server 2008 database to SQL Server 2017, we also updated the SQL code in the database to meet the new standards. Now we need to test this application and make sure that it works like before. Are you familiar with this challenge? If the answer is yes, then you will be happy to learn more about a proven, fully automated DB Best solution. Our Migration Platform product can carefully and gently guide you through the upgrade hurdles.

Watch the following video to see the seamless database upgrade verification powered by DB Best Migration Platform.

Typical SQL Server database upgrade challenges

Performing the SQL Server database upgrade, we always rely on the SQL Server Upgrade Advisor utility. Currently, Microsoft renamed this tool to Data Migration Assistant.

According to this utility, you can split the SQL Server code upgrade changes into 2 categories. The first one is critical updates, which are breaking the source code. For example, these include behavior changes, deprecated features, and other important code updates. The second category includes optimization suggestions and recommendations on the implementation of the new features. These code changes are not critical. However, if you implement them in the database upgrade project, you still need to test the code execution.

In the video above, we show how to use DB Best Migration Platform to test 1 breaking change and 3 new features implemented in the upgraded SQL Server database. Generally speaking, the approach doesn’t change depending on the complexity of the code updates.

How DB Best Migration Platform helps test code changes

We at DB Best consider database upgrades as a subset of the database migrations. However, we understand that in this particular case, the database schema conversion and SQL code upgrades require fewer efforts compared to the heterogeneous database migrations. According to our established 12-step database upgrade methodology, the most labor-intensive step of a database upgrade project is functional testing.

The video above emphasizes the importance of validating the application update alongside with data verification. The Test Organizer module in our Migration Platform significantly decreases the upgrade verification time by automating the tests generation. Yes, you don’t need to create the test scripts manually.

The other cool feature that you will love about our Test Organizer is the automatic loading of all the associated and affected objects during the test run. This means that if your test affects data in a table, our Migration Platform will show this table to you so that you can easily see the changes.

The Test Organizer module also allows for creating groups of tests and defining the test execution order. You can ignore specific tests while executing a group of tests and define whether the tests should run in-parallel or sequentially. Finally, you can easily compare the output returned by any of the tests.

If you want to take advantage of the Test Organizer module in DB Best Migration Platform, be sure to download our Migration Platform datasheet to learn more about our product. You can also request a product demo to get a better vision and understanding of our product. Let us convince you of the quality, reliability, and performance of the DB Best Migration Platform.

Share this...
Share on Facebook
Tweet about this on Twitter
Share on LinkedIn