MS SQL Server - HyperTreading and SQL 2000 licenses.

Author

HyperTreading and SQL 2000 licenses.

Thinkpad21

2006-12-13, 7:12 pm

Hi,

Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
many licenses need to be configured in SQL interface.
I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
showing are really 2 physical CPU's...

Thanks !!!

Arnie Rowland

2006-12-13, 7:12 pm

SQL Licensing is per physical CPU 'Socket'.

Dual core, hyperthreaded processors can be seen as four (4) processors by
the OS (and SQL Server) -BUT only require a single license.

There is a Computer GOD!

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf

"Thinkpad21" <thinkpad21@yahoo.com> wrote in message
news:ukXwjFuHHHA.1264@TK2MSFTNGP03.phx.gbl...
> Hi,
>
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...
>
> Thanks !!!
>
>

David Portas

2006-12-13, 7:12 pm

Thinkpad21 wrote:
> Hi,
>
> Licensing wise, if a server has 2 physical CPU's that hyperthreaded, how
> many licenses need to be configured in SQL interface.
> I know we need to buy 2, but does SQL 2000 recognize that the 4 CPU's
> showing are really 2 physical CPU's...

Regardless of how you license it SQL Server can use all processors. It
is your repsonsibility to license them correctly (i.e. per physical
processor).

For optimum performance with HT it is important that you mask 2 of the
logical processors so that SQL Server will not attempt to use more than
that number. 2 x HT CPUs is NOT the same as 4 cores.

See: http://support.microsoft.com/kb/322385

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

Sponsored Links