Mike Austin (MetrixData360) introduces licensing complexities by focusing on precise definitions: physical server, physical processor, physical core, and the related but distinct concepts of virtual cores/virtual processors. He emphasizes that Microsoft defines a virtual core as a hardware thread (either a physical core or a hyper-thread) and underscores the need to understand these terms for correct licensing.
Chapters
When it comes to licensing, a lot of the times it has to start with understanding the definitions of what things are. And typically we're in it, we're in infrastructure, we're in procurement. We know what a processor is, and we know what a core is. But the reality is, sometimes a processor means one thing and a core means another thing. Then you get into virtual processors and virtual cores and things like that, and it can become a very, very confusing topic. I always like to start with what is the definition of things? You got a physical server. We all know what that is. It's a piece of hardware that's capable of running an operating system that we install SQL Server, right? We have a physical processor. That's the actual processor in the box. And how many of those are there? And then you have physical cores. But then you get into more complex concepts like virtual core. Some people call them virtual processors. Is a virtual processor the same as a virtual core? You have to understand what these sorts of things mean, right? Because in Microsoft definition, a virtual core represents a hardware thread, and they design define a hardware thread as either a physical core or hyper thread in a physical processor.