BLOG

SQL server Capacity Limits by Edition of SQL Server

08-04-2019  0 Comment(s)
  • A thread or logical processor is one logical computing engine from the perspective of SQL Server, the operating system, an application or driver.

  • A core is a processor unit, which can consist of one or more logical processors.

  • A physical processor can consist of one or more cores. A physical processor is the same as a processor package, or a socket.

Systems with more than one physical processor or systems with physical processors that have multiple cores and/or hyperthreads enable the operating system to execute multiple tasks simultaneously. Each thread of execution appears as a logical processor. For example, if you have a computer that has two quad-core processors with hyper-threading enabled and two threads per core, you have 16 logical processors: 2 processors x 4 cores per processor x 2 threads per core. It is worth noting that:

  • The compute capacity of a logical processor from a single thread of a hyperthreaded core is less than the compute capacity of a logical processor from that same core with hyperthreading disabled.

  • But the compute capacity of the 2 logical processors in the hyperthreaded core is greater than the compute capacity of the same core with hyperthreading disabled.

Starting with SQL Server 2012, each edition of SQL Server has two compute capacity limits:

  1. A maximum number of Sockets (Same as Physical processor or Socket or Processor package).

  2. A maximum number of cores as reported by the operating system.

These limits apply to a single instance of SQL Server. They represent the maximum compute capacity that a single instance will use. They do not constrain the server upon which the instance may be deployed. In fact deploying multiple instances of SQL Server on the same physical server is an efficient way to use the compute capacity of a physical server with more sockets and/or cores than the capacity limits below.

Comment Here

Comments

No Comments to Show

WE ALWAYS WORK WITH :