Selecting versions and editions, understanding licensing, and modernizing platforms.
99 associated posts37 primary posts
I'm running into something that I'm having a hard time believing.
A client was hitting CPU issues during load testing, and they swore all things were equal between their SQL Server 2016 and 2019 environments. The 2019 box was having CPU pressure issues that didn't show up on the 2016 box. I've played this game before, and every time, the root cause has been different configurations between the two servers.
Sometimes, y'all post questions at https://pollgab.com/room/brento and they don't get a lot of upvotes, and reading through 'em, I bet it's because other people don't quite understand what you're asking. I think there might actually be a good question at the heart of it, but ... I'm just not sure what it is, and it needs to be rephrased.
I took a break from my Black Friday sale customer support emails to check in on the questions you posted at https://pollgab.com/room/brento and answer the highest-voted ones:
https://www.youtube.com/watch?v=L9CyC70X5Bo
SQL Server 2014's end of support date is coming in less than two years: July 9, 2024. I know that sounds far-off right now, but consider the work you have to do between now and then: Pick a new version to migrate to Set up development SQL Servers for that new version Start developing &…
This time on Office Hours, I let a few questions piled up at https://pollgab.com/room/brento that required in-depth answers to really do 'em justice. In particular, there was a statistics question that needed demos.
https://www.youtube.com/watch?v=d0CX1j0nKrA
You posted and upvoted questions at https://pollgab.com/room/brento, and I sat down by the fire on a chilly evening in Vail, Colorado to answer 'em. I was driving cross-country, heading back from a road trip to see my mom.
https://www.youtube.com/watch?v=SvLQdyTreQ8
It's the first webcast I've done from my new Vegas pad. You posted questions at https://pollgab.com/room/brento/ and I discussed the highest-upvoted ones:
https://www.youtube.com/watch?v=3wV64rqwxSk
Most of the time, when you need to change SQL Server's behavior - like how it handles memory or parallelism - there are easy-to-use switches to get the job done. In SQL Server Management Studio, just right-click on the server's name, go into Properties, and there are all kinds of things you can mess with. Most of the time, you're going to make things worse, but whatever.
Let's get together at sunrise in Cabo San Lucas, Mexico and talk through your highest-upvoted questions from https://pollgab.com/room/brento.
https://www.youtube.com/watch?v=sw2v_TInvac
Let's watch the sun rise at Land's End and cover your top-voted questions from https://pollgab.com/room/brento/.
https://www.youtube.com/watch?v=rtriOfpu_SU
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
I stopped at a waterfall in Iceland to answer your top-voted questions from https://pollgab.com/room/brento.
https://www.youtube.com/watch?v=tWguvLfHaNA
You upvoted questions at https://pollgab.com/room/brento, and today I'm at the harbor in Heimaey to cover 'em.
https://www.youtube.com/watch?v=dbpo9aRWxAE
Today's session comes to you from the harbor in Húsavík, the whale watching capitol of Europe.
https://www.youtube.com/watch?v=BMvm7_D9RwU
Businesses who need high availability and disaster recovery usually want three servers:
A primary SQL Server where all the writes & reads take place
A high availability SQL Server sitting right next to the primary, in the same data center, keeping up with its writes, and
A disaster recovery SQL Server sitting in another city or region, keeping up with the writes, but not necessarily in real time - the writes here are usually asynchronous
Six months ago today, you installed SQL Server Evaluation Edition. You told yourself you'd take care of that sooner or later, and...you forgot. Now, your SQL Server won't start:
Error 17051: SQL Server evaluation edition has expired.
Awww, shucks. Good news though! You don't have to uninstall & reinstall from scratch - there's an easier way.
You want to check for corruption, but you don't want to slow down your primary production server.
In this post, I'm specifically talking about offloading the corruption checking process. I'm not talking about doing corruption checking on both the primary and other servers - that's wonderful, and if you're doing that, you should hug yourself. You're doing a good job. Who's a good dog? You are! Good dog.
When you're downloading SQL Server, it's important to choose Enterprise Core, not Enterprise. The plain "Enterprise" one is limited to just 20 CPU cores.
But let's say you didn't know that, and you waltzed over to the download page. There are two Enterprises listed, and it's not really clear what the differences are between the two:
The features list by edition is out, and there's a disclaimer at the top:
This content is being updated for SQL Server 2019. The information in the article is not final.
You've gotten through a lot of this training. You've tried fixing the problem with indexes, query tuning, and judicious application of various configuration switches. You've been watching webcasts and using free scripts, but...
Things just aren't getting better.
