![]() I would argue that the warning is hidden in a small sea of text that a lot of people are going to skip, but still, it’s better than what we had before. If you try to install the plain “Enterprise” version on a big box, you get a warning: Must be a SQL Server problem.” And technically…it is. This is especially problematic when the DBAs are seeing tons of SOS_SCHEDULER_YIELD waits, indicating there’s massive CPU pressure, but the sysadmins are saying, “The server’s only 31% busy. In celebration of the impending SQL Server 2014 release, and in recognition that a large percentage of my clients are on that cusp of the Standard/Enterprise licensing decision for the currently available versionlet’s talk about SQL Server 2012 Specifically, why Enterprise edition might be a huge advantage or even an imperative for your shop. For example, here’s a 128-core VM where this “Enterprise Edition” was installed: SQL Server is only using 20 physical CPU cores, no matter how big your machine is. ![]() You see it right there? No? Of course you don’t. But if you download that SQL Server Enterprise one, install it, and then look in the error log after startup, there’s a tiny message hidden in a sea of text: ![]() If you click the “Info” link on the Enterprise version, there are no hints to indicate what’s about to happen. ![]() There are two Enterprises listed, and it’s not really clear what the differences are between the two: The plain “Enterprise” one is limited to just 20 CPU cores.īut let’s say you didn’t know that, and you waltzed over to the download page. When you’re downloading SQL Server, it’s important to choose Enterprise Core, not Enterprise.
0 Comments
Leave a Reply. |