Skip to content

Using 2020 vision with SQL Server

Reading Time: 4 minutes

In this post I’d like to discuss using 2020 vision with SQL Server. For those wondering what I mean by that I will explain shortly.

Before I do that, I’d just like to wish everybody reading this a Happy New Year.

Anyway, just to clarify what I mean by using 2020 vision with SQL Server.

As you probably know having 2020 vision means that you can see things clearly. However, in this case I mean looking clearly at how you do things with SQL Server to see if you need to update anything.

For instance, look and see if you need to introduce any modern applications or methods to become more efficient.


For some of you this might mean a change of mindset. It’s a start of a new decade and a lot of things changed towards the end of the last one.

Including, how people work with SQL Server and related technologies. I know this may seem daunting to some of you, however we all have to adapt with the times.

In reality, there’s a lot of people that don’t want to change the way they work. However, whereas they might not want to change the way they work their businesses can, and more than likely will as times change.

For example, a company may decide to migrate users from an application that solely manages Kanban style boards to a more heavily integrated application like Azure DevOps instead.

If the business has heavily invested in that new application, do you realistically expect them to encourage the use of the old one as well as the new one?

In addition, a lot of changes happen after people at various levels attend conferences.

Because they are either keen to implement what they have learned, or they are high up in the business and push for these changes to happen.

So, you need to prepare yourself for the future as things are changing. Look at the current trends to see what changes may affect you in the future.

In addition, it’s worth looking at new applications and methods to see if any of them can help you. Like the below example.

SQL Server updates

For example, you might want to look at how you deploy SQL Server updates. Especially if you still do them manually on all your servers using some code provided by others.

You can look to deploy your updates within a deployment pipeline instead, using an application like Azure DevOps. Of course, other applications are available as well.


I know for a lot of long-term SQL Server Database Administrators this might sound complex, and to be honest the first time it can be. However, usually it’s only the learning curve that is complex.

Afterwards, you will find a lot of the changes will make your life easier. In addition, this is the way the industry is moving, and we have to move with the times.

Some of the New Year resolutions I discussed in December 2018 can help with this. You can read them in detail here. In addition, I have other blog posts that share learning resources you can use.

Performance tuning

At the start of the last decade there was a lot of focus on getting the most performance out of SQL Server, and high availability.

Whilst both of these are still important, in these modern times businesses want things like SQL server and database updates deployed as fast as possible as well.

Which is why there’s now more of a demand for SQL Engineers. People who are able to move with the times and can develop more automated solutions for companies.

Of course, there’s still a need for people to do performance tuning. Which certainly has been made easier over the years with new features and free tools being introduced.

For example, using Query Store can make a big difference in performance tuning query performance.

Azure DevOps session

I understand how some people reading this might feel. I myself had to go through a change of mindset to adopt to new methods. Nowadays, as well as using new methods myself I help people who work for clients adopt them as well.

Last year, I presented about Azure DevOps to people in different teams for one particular client. So, I understand the issues faced by people in different areas.

In fact, it’s one of the reasons I’ve decided to co-present about using Azure DevOps with SQL Server. For those interested, you can watch me and Sander Stad present our session is at SQL Saturday Edinburgh at the beginning of February.

Of course, there are plenty of other sessions at SQL Saturday Edinburgh linked to newer ways to deploy SQL Servers as well.

Including at least three which includes containers. In reality, it could end up being four. Depending on what happens during the second session I am presenting towards the end of the event.

If you are interested in attending than you can see the full schedule for SQL Saturday Edinburgh in detail here.

Final word

Anyway, as we see in a new year and a new decade I encourage you to take a step back and look at the bigger picture. See if there is room for improvement.

In other words, start using 2020 vision with SQL Server. Because I’m a firm believer that just because something has always been done the same way, doesn’t always mean it’s right.

In this new decade, I encourage you to take on a similar mindset because things are changing.

Using 2020 vision with SQL Server
Published inAzure DevOpsPresentingSQL Server

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *