Version selection, end of support, adoption, and upgrade readiness.
15 associated posts15 primary posts
This entire blog post is driven by the #1 feature in this list. I think about the #1 feature a lot, like at least once a week. I think about it so much that I had to stop and think about what other similar great things Microsoft has done over the years, and be thankful for what a nice platform this is to work with. Let's go through 6 of my favorite Microsoft decisions.
If you right-click on a database in SQL Server Management Studio, you get an option to set Compatibility Level at the database level:
When you upgrade SQL Server or you want to improve performance, which option should you choose? Should you always go with the newest compatibility level? If you have an old application, can you upgrade SQL Server but still keep the old compat level without the vendor knowing? Let's hit the common questions.
I went through your highest-voted questions from Pollgab and talked through 'em, and strangely, there was a bit of a 2008R2 theme!
https://youtu.be/3-B5L3Komq4
Your company is ignoring the news: SQL Server 2008 and 2008R2 are officially out of support as of today, but nothing's changing at your company. You still have SQL Server 2008 in production, and you're a little nervous. How should you approach the conversations with management? Brent Ozar will help: he's been there too, fighting…
Whether you're looking to go cutting-edge and hop on SQL Server 2019 as soon as it's available, or whether you're just trying to evacuate from SQL Server 2008 to anything that's going to be supported after this summer, you're probably doing upgrade projects. This is a good time to ask yourself 5 questions: 1. Do…
Wait! Before you install that next SQL Server, hold up. Are you sure you're using the right version?
I know, management wants you to stay on an older build, and the vendor says they'll only support older versions, but now's your chance to make your case for a newer version - and I'm gonna help you do it.
I'm almost afraid to look into the SQL ConstantCare® client base to see the answer to this, but let's put on a pair of rubber gloves and go find out. SQL Server 2016: <1% out of support. I LOVE YOU PEOPLE. However, you've had the luxury of time here: SP1 came out in November 2016,…
Starting with yesterday's release of SQL Server 2017, Microsoft has a new servicing model: they're only delivering Cumulative Updates, and not doing Service Packs.
Pedro Lopes writes:
This week, Brent, Richie, and Erik discuss estimating compression savings, disabling triggers, suggestions to first-time Pass Summit attendees, tools for database version control, transitioning from SQL 2000 to 2016, troubleshooting failovers, and how to convince your manager to upgrade to newer version of SQL. FYI: our regular transcriptionist is out for a couple of weeks,…
Ask not for whom the bell tolls
It tolls for SQL Server 2005. Which means in a few short months, you'll need to get out of Dodge. I'm sure you all have your upgrade ducks in a row, you've studied the breaking changes, the upgrade path, and maybe even downloaded the latest upgrade advisor. Smarty pants you are! I'm proud of you.
Can I upgrade an existing instance without migrating?
This is nothing against SQL Server 2014, but I can't stand in-place upgrades. Over the years I've had in-place upgrades work flawlessly on a few instances, and then had an install issue cause it to fail in the middle on other instances. Usually the critical instances, just because I'm not always lucky. And when upgrade fails, it doesn't always roll back completely, or allow you to just re-run it. You may be down for a good long time.
Stop. Before you think about upgrading your existing SQL Server to the latest version, think it through.
Your hardware is old. Even if it's just a couple of years old, the latest advances in processors, memory, and storage mean it's practically an antique.
Let's say you get your hands on a brand new version of SQL Server that you haven't played with before, and you want to know what system objects have changed - DMVs, DMFs, system stored procs, yadda yadda yadda. Sure, you could read the documentation - but ain't nobody got time for that, and they're probably leaving out the juicy stuff, right? Here's what I do (thanks to improvement suggestions from Kendra):
It's finally time-- you've been given the thumbs up to upgrade to SQL Server 2012. You've selected your SQL Server Edition and worked out your licensing agreement. You've sized new hardware in production and sketched out your migration plan. You're ready to install developer edition in the test environment. You grab your installation media and...…
This month's Redmond Mag glows about some new features in SQL 2008, and yes, it does have a lot of cool tricks up its sleeve. But before you go upgrading your servers to get those new features, there's one thing you need to know. New versions of SQL Server are not always faster for every…
