I ran across a good article from Glenn Berry about reasons to upgrade to SQL Server 2017. In the piece, Glenn talks about the fact that SQL Server 2008 and 2008 R2 will fall out of Extended Support in 2019. That's about the time that SQL Server 2014 falls out of mainstream support, which is the support that most of us have. SQL Server 2012 has fallen out of mainstream support already. While I don't worry too much about support, some of you may, especially if you are in a regulated industry. Or you're in the EU, in which case the lack of support might be an issue if there is ever some security breach.
The upgrade question is one that most of us ask ourselves constantly. Many of us use plenty of different software packages, and regularly need to decide if we want to pay for a new version of Windows, Office, SQL, SAP, Dynamics, etc. In some cases we may find valid reasons that will give us a nice ROI and are worth the cost. In others, we may wonder if we really need some new feature? I certainly find that in some software, there isn't a compelling reason to upgrade to every new version.
These days so much software is being released at a rapid pace that we regularly have to make decisions. I get a new version of Visual Studio Code, Evernote and TweetDuck, etc. every few weeks. Often I skip these upgrades because of convenience, and only upgrade rarely to prevent being too far behind. That's a concern because if your software is too old, sometimes the upgrade is painful.
At Redgate, we release patches and enhancements every few weeks, though we don't expect many customers to necessarily upgrade more than once a quarter. There are monthly releases of SSMS and SQL Operations Studio, which I may or may not apply. Often I don't because they're an interruption to my work. Some of us rent software, like visualstudio.com, and we get upgrades whether we want them or not, though often we can use an older version for some period of time.
Many of these decisions aren't that impactful to our work as they are minor changes with little or no cost. Some aren't, and these are the ones that many technical professionals will make recommendations on whether to proceed or not. The database platform is certainly a significant decision as the costs often can significantly impact a budget. This can be especially true for mission critical applications that might require more than one server to meet HA requirements.
Do you tend to lean towards or away from upgrades? I've tended to lean away, with my default answer being I don't want to upgrade. That's if I don't have a compelling reason. If things are roughly equal, I'll stick with what works. That doesn't mean that I don't evaluate the new version and spend some time trying to determine what features or functions might be valuable. Certainly if any of Glenn's features are useful, you might consider moving to SQL Server 2017. If you're coming from SQL Server 2014 or earlier, than you ought to really look at the changes in SQL Server 2016, which are significant as well.
We recently moved SQLServerCentral to SQL Server 2017. We had been on an older OS, with limited .NET support, and when we made the decision, we decided to go ahead and choose the latest version. That's certainly a decision I do endorse. If I'm leaving 2012, 2008, or some earlier version, why stop at SQL Server 2014 or 2016. Go ahead and get to the latest version, which means you might delay your next upgrade just a bit longer.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
Write, format, analyze, and refactor SQL fast with SQL Prompt
Writing SQL is 50% faster with SQL Prompt. Your SQL code can be formatted just the way you like it, you can create and share snippets with your team, and with code analysis you get suggestions to improve your SQL as you type. Download your free trial
How to track every change to your SQL Server database
See who’s changing your database, alongside affected objects, date, time, and reason for the change with SQL Source Control. Get a full change history in your source control system. Learn more
Some time ago, Phil Factor wrote his booklet 'SQL Code Smells', collecting together a whole range of SQL Coding practices that could be considered to indicate the need for a review of the code. It was published as 119 code smells, even though there were 120 of them at the time. Phil Factor has continued to collect them and the current state of the art is reflected in this article. SQL Prompt is committed to cover as many as possible of them. Phil has also updated his book, which is free to download. More »
In this post, Redgate's Foundry team reflect on their assessment of the status of DevOps for the database. As well as giving you a behind-the-scenes look at how they've arrived at this thinking and setting out their future direction, they also invite you to shape the future of database DevOps by getting involved. More »
Squeeze maximum performance and efficiency from every T-SQL query you write or tune. Four leading experts take an in-depth look at T-SQL’s internal architecture and offer advanced practical techniques for optimizing response time and resource usage. Get your copy from Amazon today.
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.