Showing posts with label processor. Show all posts
Showing posts with label processor. Show all posts

Sunday, March 11, 2012

Dual processors?

One of my customers just plugged in a second processor on a sql server 2000
running on a dell (dual Xeon at 2G). Does the simple fact of plugging in a
second processor increase the speed of sql server standard on that machine?
I'm not sure its that simple.
Any insight would be appreciated.
BobSQL will use the second processor, provided the OS accepts and uses it.
Whether that speeds up SQL depends on what resource is limiting SQL
performance. If the system was running over 80% CPU usage, he will likely
see some noticable speed improvement. As has been said before in this
forum, you first have to identify the performance limiting factor(s) I.E.
the bottlenecks, in your system before you can determine whether adding
resource X will make it faster. This applies whether X is memory, RAM, disk
capacity/speed, CPU speed/count, or network bandwidth.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bob" <bdufour@.sgiims.com> wrote in message
news:OASJaP0BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> One of my customers just plugged in a second processor on a sql server
> 2000 running on a dell (dual Xeon at 2G). Does the simple fact of plugging
> in a second processor increase the speed of sql server standard on that
> machine? I'm not sure its that simple.
> Any insight would be appreciated.
> Bob
>|||On Thu, 22 Dec 2005 17:05:40 -0500, "Bob" <bdufour@.sgiims.com> wrote:
>One of my customers just plugged in a second processor on a sql server 2000
>running on a dell (dual Xeon at 2G). Does the simple fact of plugging in a
>second processor increase the speed of sql server standard on that machine?
>I'm not sure its that simple.
Did you say on the other thread that you are running Windows 2000?
Windows Server 2003 supports threads better and is probably better
overall for multiprocessor systems.
Josh|||Bob wrote:
> One of my customers just plugged in a second processor on a sql
> server 2000 running on a dell (dual Xeon at 2G). Does the simple fact
> of plugging in a second processor increase the speed of sql server
> standard on that machine? I'm not sure its that simple.
> Any insight would be appreciated.
> Bob
Not only should it increase speed, but it will require you puchase
another CPU license if you are using the CPU licensing model.
To be sure, check to make sure SQL Server is using both processors. You
can do this from the server properties in SQL EM.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Friday, March 9, 2012

Dual processors?

One of my customers just plugged in a second processor on a sql server 2000
running on a dell (dual Xeon at 2G). Does the simple fact of plugging in a
second processor increase the speed of sql server standard on that machine?
I'm not sure its that simple.
Any insight would be appreciated.
Bob
SQL will use the second processor, provided the OS accepts and uses it.
Whether that speeds up SQL depends on what resource is limiting SQL
performance. If the system was running over 80% CPU usage, he will likely
see some noticable speed improvement. As has been said before in this
forum, you first have to identify the performance limiting factor(s) I.E.
the bottlenecks, in your system before you can determine whether adding
resource X will make it faster. This applies whether X is memory, RAM, disk
capacity/speed, CPU speed/count, or network bandwidth.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bob" <bdufour@.sgiims.com> wrote in message
news:OASJaP0BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> One of my customers just plugged in a second processor on a sql server
> 2000 running on a dell (dual Xeon at 2G). Does the simple fact of plugging
> in a second processor increase the speed of sql server standard on that
> machine? I'm not sure its that simple.
> Any insight would be appreciated.
> Bob
>
|||On Thu, 22 Dec 2005 17:05:40 -0500, "Bob" <bdufour@.sgiims.com> wrote:
>One of my customers just plugged in a second processor on a sql server 2000
>running on a dell (dual Xeon at 2G). Does the simple fact of plugging in a
>second processor increase the speed of sql server standard on that machine?
>I'm not sure its that simple.
Did you say on the other thread that you are running Windows 2000?
Windows Server 2003 supports threads better and is probably better
overall for multiprocessor systems.
Josh
|||Bob wrote:
> One of my customers just plugged in a second processor on a sql
> server 2000 running on a dell (dual Xeon at 2G). Does the simple fact
> of plugging in a second processor increase the speed of sql server
> standard on that machine? I'm not sure its that simple.
> Any insight would be appreciated.
> Bob
Not only should it increase speed, but it will require you puchase
another CPU license if you are using the CPU licensing model.
To be sure, check to make sure SQL Server is using both processors. You
can do this from the server properties in SQL EM.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Dual processors?

One of my customers just plugged in a second processor on a sql server 2000
running on a dell (dual Xeon at 2G). Does the simple fact of plugging in a
second processor increase the speed of sql server standard on that machine?
I'm not sure its that simple.
Any insight would be appreciated.
BobSQL will use the second processor, provided the OS accepts and uses it.
Whether that speeds up SQL depends on what resource is limiting SQL
performance. If the system was running over 80% CPU usage, he will likely
see some noticable speed improvement. As has been said before in this
forum, you first have to identify the performance limiting factor(s) I.E.
the bottlenecks, in your system before you can determine whether adding
resource X will make it faster. This applies whether X is memory, RAM, disk
capacity/speed, CPU speed/count, or network bandwidth.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bob" <bdufour@.sgiims.com> wrote in message
news:OASJaP0BGHA.1288@.TK2MSFTNGP09.phx.gbl...
> One of my customers just plugged in a second processor on a sql server
> 2000 running on a dell (dual Xeon at 2G). Does the simple fact of plugging
> in a second processor increase the speed of sql server standard on that
> machine? I'm not sure its that simple.
> Any insight would be appreciated.
> Bob
>|||On Thu, 22 Dec 2005 17:05:40 -0500, "Bob" <bdufour@.sgiims.com> wrote:
>One of my customers just plugged in a second processor on a sql server 2000
>running on a dell (dual Xeon at 2G). Does the simple fact of plugging in a
>second processor increase the speed of sql server standard on that machine?
>I'm not sure its that simple.
Did you say on the other thread that you are running Windows 2000?
Windows Server 2003 supports threads better and is probably better
overall for multiprocessor systems.
Josh|||Bob wrote:
> One of my customers just plugged in a second processor on a sql
> server 2000 running on a dell (dual Xeon at 2G). Does the simple fact
> of plugging in a second processor increase the speed of sql server
> standard on that machine? I'm not sure its that simple.
> Any insight would be appreciated.
> Bob
Not only should it increase speed, but it will require you puchase
another CPU license if you are using the CPU licensing model.
To be sure, check to make sure SQL Server is using both processors. You
can do this from the server properties in SQL EM.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Dual Processor Licensing

I intend to run SQL 2k on a dual processor server, my company wish however
to be very economic with licenses and i'd like to know if you run SQL 2k or
2005 for that matter, is it possible from inside SQL to set the application
to only run on one of the processors?
I know this is a bit of a dunb question and there are some very smart
answers that could be said, but i just need to ask the question, so i can go
back to company people and tell them they are being very tight!!
And get them to buy another enterprise server processor licence.
RgdsFrom the SQL Server licensing FAQ
(http://www.microsoft.com/sql/howtobuy/faq.mspx)
<Excerpt>
Do I have to acquire licenses for all of the processors in a server?
A. You have to acquire licenses only for processors that are accessible to
any copy of the operating system upon which SQL Server 2005 is installed. In
a virtualized environment, processor licenses are required for every
processor that is accessed by a virtual machine. Please see the
virtualization licensing brief and virtualization white paper for more
information on how to license under a virtualized environment.
</Excerpt>
The same applies to SQL 2000. Although you can set SQL Server processor
affinity to restrict processor utilization, this does not reduce the number
of licenses required.
Hope this helps.
Dan Guzman
SQL Server MVP
"Stu" <lbwer@.blah.com> wrote in message
news:OxhPN5VtGHA.3552@.TK2MSFTNGP03.phx.gbl...
>I intend to run SQL 2k on a dual processor server, my company wish however
>to be very economic with licenses and i'd like to know if you run SQL 2k or
>2005 for that matter, is it possible from inside SQL to set the application
>to only run on one of the processors?
> I know this is a bit of a dunb question and there are some very smart
> answers that could be said, but i just need to ask the question, so i can
> go back to company people and tell them they are being very tight!!
> And get them to buy another enterprise server processor licence.
> Rgds
>|||"Stu" <lbwer@.blah.com> wrote in message
news:OxhPN5VtGHA.3552@.TK2MSFTNGP03.phx.gbl...
>I intend to run SQL 2k on a dual processor server, my company wish however
>to be very economic with licenses and i'd like to know if you run SQL 2k or
>2005 for that matter, is it possible from inside SQL to set the application
>to only run on one of the processors?
>
Yes. You can set SQL Server's CPU Affinity mask to have SQL run on a subset
of the processors. However this has no affect on licensing.
affinity mask Option
http://msdn2.microsoft.com/en-us/library/ms187104.aspx

> I know this is a bit of a dunb question and there are some very smart
> answers that could be said, but i just need to ask the question, so i can
> go back to company people and tell them they are being very tight!!
> And get them to buy another enterprise server processor licence.
>
SQL Sever must be licensed on all processors that the Windows instance can
see. So unless you can turn off one of the CPU's in the BIOS, or you
install SQL Server on a Virtual Server that can only "see" one CPU, you must
license both processors.
SQL Server Pricing and Licensing
http://www.microsoft.com/sql/howtob...rlicensing.mspx
David|||Meaning I guess that because the application is installed on a dual
processor box, it will need 2 licences no matter now many are being
utilised?
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:%234SpDIWtGHA.1512@.TK2MSFTNGP03.phx.gbl...
> "Stu" <lbwer@.blah.com> wrote in message
> news:OxhPN5VtGHA.3552@.TK2MSFTNGP03.phx.gbl...
> Yes. You can set SQL Server's CPU Affinity mask to have SQL run on a
> subset of the processors. However this has no affect on licensing.
> affinity mask Option
> http://msdn2.microsoft.com/en-us/library/ms187104.aspx
>
> SQL Sever must be licensed on all processors that the Windows instance can
> see. So unless you can turn off one of the CPU's in the BIOS, or you
> install SQL Server on a Virtual Server that can only "see" one CPU, you
> must license both processors.
> SQL Server Pricing and Licensing
> http://www.microsoft.com/sql/howtob...rlicensing.mspx
> David
>|||"Stu" <lbwer@.blah.com> wrote in message
news:e2XEVNWtGHA.4140@.TK2MSFTNGP03.phx.gbl...
> Meaning I guess that because the application is installed on a dual
> processor box, it will need 2 licences no matter now many are being
> utilised?
Yes. Of course for licensing you count "sockets" not "cores".
David|||For SQL 2000, it is necessary to license for each CPU in the computer -even
if they are not used by SQL Server.
However, it SQL 2005, if you used VM Ware (or MS Virtual Server) to create
totally separate environments, then you can license for only the number of
CPU's that are used by SQL Server in that environment.
That could be cost effective for you.
See:
http://download.microsoft.com/downl...censingv1.1.doc
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <lbwer@.blah.com> wrote in message
news:e2XEVNWtGHA.4140@.TK2MSFTNGP03.phx.gbl...
> Meaning I guess that because the application is installed on a dual
> processor box, it will need 2 licences no matter now many are being
> utilised?
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:%234SpDIWtGHA.1512@.TK2MSFTNGP03.phx.gbl...
>

Dual Processor Licensing

I intend to run SQL 2k on a dual processor server, my company wish however
to be very economic with licenses and i'd like to know if you run SQL 2k or
2005 for that matter, is it possible from inside SQL to set the application
to only run on one of the processors?
I know this is a bit of a dunb question and there are some very smart
answers that could be said, but i just need to ask the question, so i can go
back to company people and tell them they are being very tight!!
And get them to buy another enterprise server processor licence.
RgdsFrom the SQL Server licensing FAQ
(http://www.microsoft.com/sql/howtobuy/faq.mspx)
<Excerpt>
Do I have to acquire licenses for all of the processors in a server?
A. You have to acquire licenses only for processors that are accessible to
any copy of the operating system upon which SQL Server 2005 is installed. In
a virtualized environment, processor licenses are required for every
processor that is accessed by a virtual machine. Please see the
virtualization licensing brief and virtualization white paper for more
information on how to license under a virtualized environment.
</Excerpt>
The same applies to SQL 2000. Although you can set SQL Server processor
affinity to restrict processor utilization, this does not reduce the number
of licenses required.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Stu" <lbwer@.blah.com> wrote in message
news:OxhPN5VtGHA.3552@.TK2MSFTNGP03.phx.gbl...
>I intend to run SQL 2k on a dual processor server, my company wish however
>to be very economic with licenses and i'd like to know if you run SQL 2k or
>2005 for that matter, is it possible from inside SQL to set the application
>to only run on one of the processors?
> I know this is a bit of a dunb question and there are some very smart
> answers that could be said, but i just need to ask the question, so i can
> go back to company people and tell them they are being very tight!!
> And get them to buy another enterprise server processor licence.
> Rgds
>|||"Stu" <lbwer@.blah.com> wrote in message
news:OxhPN5VtGHA.3552@.TK2MSFTNGP03.phx.gbl...
>I intend to run SQL 2k on a dual processor server, my company wish however
>to be very economic with licenses and i'd like to know if you run SQL 2k or
>2005 for that matter, is it possible from inside SQL to set the application
>to only run on one of the processors?
>
Yes. You can set SQL Server's CPU Affinity mask to have SQL run on a subset
of the processors. However this has no affect on licensing.
affinity mask Option
http://msdn2.microsoft.com/en-us/library/ms187104.aspx
> I know this is a bit of a dunb question and there are some very smart
> answers that could be said, but i just need to ask the question, so i can
> go back to company people and tell them they are being very tight!!
> And get them to buy another enterprise server processor licence.
>
SQL Sever must be licensed on all processors that the Windows instance can
see. So unless you can turn off one of the CPU's in the BIOS, or you
install SQL Server on a Virtual Server that can only "see" one CPU, you must
license both processors.
SQL Server Pricing and Licensing
http://www.microsoft.com/sql/howtobuy/sqlserverlicensing.mspx
David|||Meaning I guess that because the application is installed on a dual
processor box, it will need 2 licences no matter now many are being
utilised?
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:%234SpDIWtGHA.1512@.TK2MSFTNGP03.phx.gbl...
> "Stu" <lbwer@.blah.com> wrote in message
> news:OxhPN5VtGHA.3552@.TK2MSFTNGP03.phx.gbl...
>>I intend to run SQL 2k on a dual processor server, my company wish however
>>to be very economic with licenses and i'd like to know if you run SQL 2k
>>or 2005 for that matter, is it possible from inside SQL to set the
>>application to only run on one of the processors?
> Yes. You can set SQL Server's CPU Affinity mask to have SQL run on a
> subset of the processors. However this has no affect on licensing.
> affinity mask Option
> http://msdn2.microsoft.com/en-us/library/ms187104.aspx
>> I know this is a bit of a dunb question and there are some very smart
>> answers that could be said, but i just need to ask the question, so i can
>> go back to company people and tell them they are being very tight!!
>> And get them to buy another enterprise server processor licence.
> SQL Sever must be licensed on all processors that the Windows instance can
> see. So unless you can turn off one of the CPU's in the BIOS, or you
> install SQL Server on a Virtual Server that can only "see" one CPU, you
> must license both processors.
> SQL Server Pricing and Licensing
> http://www.microsoft.com/sql/howtobuy/sqlserverlicensing.mspx
> David
>|||"Stu" <lbwer@.blah.com> wrote in message
news:e2XEVNWtGHA.4140@.TK2MSFTNGP03.phx.gbl...
> Meaning I guess that because the application is installed on a dual
> processor box, it will need 2 licences no matter now many are being
> utilised?
Yes. Of course for licensing you count "sockets" not "cores".
David|||For SQL 2000, it is necessary to license for each CPU in the computer -even
if they are not used by SQL Server.
However, it SQL 2005, if you used VM Ware (or MS Virtual Server) to create
totally separate environments, then you can license for only the number of
CPU's that are used by SQL Server in that environment.
That could be cost effective for you.
See:
http://download.microsoft.com/download/e/c/a/ecafe5d1-b514-48ab-93eb-61377df9c5c2/SQLServer2005Licensingv1.1.doc
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <lbwer@.blah.com> wrote in message
news:e2XEVNWtGHA.4140@.TK2MSFTNGP03.phx.gbl...
> Meaning I guess that because the application is installed on a dual
> processor box, it will need 2 licences no matter now many are being
> utilised?
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:%234SpDIWtGHA.1512@.TK2MSFTNGP03.phx.gbl...
>> "Stu" <lbwer@.blah.com> wrote in message
>> news:OxhPN5VtGHA.3552@.TK2MSFTNGP03.phx.gbl...
>>I intend to run SQL 2k on a dual processor server, my company wish
>>however to be very economic with licenses and i'd like to know if you run
>>SQL 2k or 2005 for that matter, is it possible from inside SQL to set the
>>application to only run on one of the processors?
>>
>> Yes. You can set SQL Server's CPU Affinity mask to have SQL run on a
>> subset of the processors. However this has no affect on licensing.
>> affinity mask Option
>> http://msdn2.microsoft.com/en-us/library/ms187104.aspx
>> I know this is a bit of a dunb question and there are some very smart
>> answers that could be said, but i just need to ask the question, so i
>> can go back to company people and tell them they are being very tight!!
>> And get them to buy another enterprise server processor licence.
>>
>> SQL Sever must be licensed on all processors that the Windows instance
>> can see. So unless you can turn off one of the CPU's in the BIOS, or you
>> install SQL Server on a Virtual Server that can only "see" one CPU, you
>> must license both processors.
>> SQL Server Pricing and Licensing
>> http://www.microsoft.com/sql/howtobuy/sqlserverlicensing.mspx
>> David
>

dual processor license

We are buying a new db server that will support the future growth of our
company. Our current database load can easily be handled by a single
processor server, but I would like to buy a server that can handle a much
heavier load in the future.
1) I am wondering if I get a dual processor server, can I install a single
processor license of sql server for the time being?
2) Will this only utilize one processor?
3) Can I add an additional processor license in the future as when we need
more processing power?
4) Also, what is the latest projected relase date for SQL Server 2005?
5) Is any pricing availible for this yet?
6) If I get SQL Server 2000 license now, will there be any upgrade options
to 2005 when it is availible?
Any advice is greatly appreciated.
--DanThe SQL Server 2000 Licensing FAQ at
http://www.microsoft.com/sql/howtobuy/faq.asp states the following:
Q. Do I have to license all of the processors in a server?
A. You only have to acquire licenses for processors that are
accessible to any copy of the operating system upon which SQL Server 2000 is
installed.
So that should take care of questions 1 through 3. :-) You could physically
remove one of the processors from the new system and run it that way until
you have need, then purchase the second processor license and install the
second processor.
For #4, I believe our official response is in the summer of 2005.
For #5, I don't think any of the pricing decisions have been made yet.
For #6, there's usually some kind of upgrade pricing, but again, I doubt
that decision has been made yet.
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to the newsgroups only, thanks.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6E68F23D-3143-4385-8876-06CF474C7299@.microsoft.com...
> We are buying a new db server that will support the future growth of our
> company. Our current database load can easily be handled by a single
> processor server, but I would like to buy a server that can handle a much
> heavier load in the future.
> 1) I am wondering if I get a dual processor server, can I install a single
> processor license of sql server for the time being?
> 2) Will this only utilize one processor?
> 3) Can I add an additional processor license in the future as when we need
> more processing power?
> 4) Also, what is the latest projected relase date for SQL Server 2005?
> 5) Is any pricing availible for this yet?
> 6) If I get SQL Server 2000 license now, will there be any upgrade options
> to 2005 when it is availible?
> Any advice is greatly appreciated.
> --Dan
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end|||Just to add a little to the discussion. MS licensing currently allows you
to buy with software assurance. This lets you upgrade to the newest version
when it comes out provided it's in the timeframe provide by the SA license.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:eHlqD#u6EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The SQL Server 2000 Licensing FAQ at
> http://www.microsoft.com/sql/howtobuy/faq.asp states the following:
> Q. Do I have to license all of the processors in a server?
>
> A. You only have to acquire licenses for processors that are
> accessible to any copy of the operating system upon which SQL Server 2000
is
> installed.
>
>
> So that should take care of questions 1 through 3. :-) You could
physically
> remove one of the processors from the new system and run it that way until
> you have need, then purchase the second processor license and install the
> second processor.
> For #4, I believe our official response is in the summer of 2005.
> For #5, I don't think any of the pricing decisions have been made yet.
> For #6, there's usually some kind of upgrade pricing, but again, I doubt
> that decision has been made yet.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to the newsgroups only, thanks.
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:6E68F23D-3143-4385-8876-06CF474C7299@.microsoft.com...
> > We are buying a new db server that will support the future growth of our
> > company. Our current database load can easily be handled by a single
> > processor server, but I would like to buy a server that can handle a
much
> > heavier load in the future.
> >
> > 1) I am wondering if I get a dual processor server, can I install a
single
> > processor license of sql server for the time being?
> > 2) Will this only utilize one processor?
> > 3) Can I add an additional processor license in the future as when we
need
> > more processing power?
> > 4) Also, what is the latest projected relase date for SQL Server 2005?
> > 5) Is any pricing availible for this yet?
> > 6) If I get SQL Server 2000 license now, will there be any upgrade
options
> > to 2005 when it is availible?
> >
> > Any advice is greatly appreciated.
> > --Dan
>
>

dual processor license

We are buying a new db server that will support the future growth of our
company. Our current database load can easily be handled by a single
processor server, but I would like to buy a server that can handle a much
heavier load in the future.
1) I am wondering if I get a dual processor server, can I install a single
processor license of sql server for the time being?
2) Will this only utilize one processor?
3) Can I add an additional processor license in the future as when we need
more processing power?
4) Also, what is the latest projected relase date for SQL Server 2005?
5) Is any pricing availible for this yet?
6) If I get SQL Server 2000 license now, will there be any upgrade options
to 2005 when it is availible?
Any advice is greatly appreciated.
--Dan
The SQL Server 2000 Licensing FAQ at
http://www.microsoft.com/sql/howtobuy/faq.asp states the following:
Q. Do I have to license all of the processors in a server?
A. You only have to acquire licenses for processors that are
accessible to any copy of the operating system upon which SQL Server 2000 is
installed.
So that should take care of questions 1 through 3. :-) You could physically
remove one of the processors from the new system and run it that way until
you have need, then purchase the second processor license and install the
second processor.
For #4, I believe our official response is in the summer of 2005.
For #5, I don't think any of the pricing decisions have been made yet.
For #6, there's usually some kind of upgrade pricing, but again, I doubt
that decision has been made yet.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to the newsgroups only, thanks.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6E68F23D-3143-4385-8876-06CF474C7299@.microsoft.com...
> We are buying a new db server that will support the future growth of our
> company. Our current database load can easily be handled by a single
> processor server, but I would like to buy a server that can handle a much
> heavier load in the future.
> 1) I am wondering if I get a dual processor server, can I install a single
> processor license of sql server for the time being?
> 2) Will this only utilize one processor?
> 3) Can I add an additional processor license in the future as when we need
> more processing power?
> 4) Also, what is the latest projected relase date for SQL Server 2005?
> 5) Is any pricing availible for this yet?
> 6) If I get SQL Server 2000 license now, will there be any upgrade options
> to 2005 when it is availible?
> Any advice is greatly appreciated.
> --Dan
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Just to add a little to the discussion. MS licensing currently allows you
to buy with software assurance. This lets you upgrade to the newest version
when it comes out provided it's in the timeframe provide by the SA license.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:eHlqD#u6EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The SQL Server 2000 Licensing FAQ at
> http://www.microsoft.com/sql/howtobuy/faq.asp states the following:
> Q. Do I have to license all of the processors in a server?
>
> A. You only have to acquire licenses for processors that are
> accessible to any copy of the operating system upon which SQL Server 2000
is
> installed.
>
>
> So that should take care of questions 1 through 3. :-) You could
physically
> remove one of the processors from the new system and run it that way until
> you have need, then purchase the second processor license and install the
> second processor.
> For #4, I believe our official response is in the summer of 2005.
> For #5, I don't think any of the pricing decisions have been made yet.
> For #6, there's usually some kind of upgrade pricing, but again, I doubt
> that decision has been made yet.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> Please reply to the newsgroups only, thanks.
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:6E68F23D-3143-4385-8876-06CF474C7299@.microsoft.com...
much[vbcol=seagreen]
single[vbcol=seagreen]
need[vbcol=seagreen]
options
>
>

dual processor license

We are buying a new db server that will support the future growth of our
company. Our current database load can easily be handled by a single
processor server, but I would like to buy a server that can handle a much
heavier load in the future.
1) I am wondering if I get a dual processor server, can I install a single
processor license of sql server for the time being?
2) Will this only utilize one processor?
3) Can I add an additional processor license in the future as when we need
more processing power?
4) Also, what is the latest projected relase date for SQL Server 2005?
5) Is any pricing availible for this yet?
6) If I get SQL Server 2000 license now, will there be any upgrade options
to 2005 when it is availible?
Any advice is greatly appreciated.
--DanJust to add a little to the discussion. MS licensing currently allows you
to buy with software assurance. This lets you upgrade to the newest version
when it comes out provided it's in the timeframe provide by the SA license.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:eHlqD#u6EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The SQL Server 2000 Licensing FAQ at
> http://www.microsoft.com/sql/howtobuy/faq.asp states the following:
> Q. Do I have to license all of the processors in a server?
>
> A. You only have to acquire licenses for processors that are
> accessible to any copy of the operating system upon which SQL Server 2000
is
> installed.
>
>
> So that should take care of questions 1 through 3. :-) You could
physically
> remove one of the processors from the new system and run it that way until
> you have need, then purchase the second processor license and install the
> second processor.
> For #4, I believe our official response is in the summer of 2005.
> For #5, I don't think any of the pricing decisions have been made yet.
> For #6, there's usually some kind of upgrade pricing, but again, I doubt
> that decision has been made yet.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to the newsgroups only, thanks.
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:6E68F23D-3143-4385-8876-06CF474C7299@.microsoft.com...
much[vbcol=seagreen]
single[vbcol=seagreen]
need[vbcol=seagreen]
options[vbcol=seagreen]
>
>

dual processor benefit

Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?
Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:

> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>
|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>

dual processor benefit

Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:

> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we shoul
d
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to veri
fy
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>

dual processor benefit

Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>

Dual Processor

Is it possible to at a second processor on a W2K OR W2K3
server with SQL installed without re-install everything.
ThanksFor Win2k have a look at
HOW TO: Add Support for Multiple Processors in Windows 2000
http://support.microsoft.com/default.aspx?scid=KB;en-us;234558
If the OS can see the new processor, SQL will pick it up automatically
following a restart. Not sure about the details for Win2003
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Rob Zw." <anonymous@.discussions.microsoft.com> wrote in message
news:0c2701c3b8f2$00fec980$a501280a@.phx.gbl...
Is it possible to at a second processor on a W2K OR W2K3
server with SQL installed without re-install everything.
Thanks

dual core processor conflict graphics card

ok i have intel dual core i have a conflict only in playing a game black hawk down it gives me a run stop error. locks up and has to be restarted. microsoft gave me a fix but when i do the fix it causes me to get a system dump error on the game. i can update my web site do anything else let daughter play her games or do her school work and nothing happens. i was told i needed to set up the dual core so that my programs dont conflict i am a moron when it comes to computers is there a fix for this or i am i just going to have to go back to single core processor for now thanks

Your thread is in the wrong forum.

However, you may want to try looking into the following, you can specify that a process runs on just one processor, so your game could be run on one core of the processor.

I'm not sure on how you would do this, probably through task manager. Try posting it on the black hawk down forums on the software vendors site or phoning the games support line.

Dual Core Processor

We are in process of moving to 64 bit HP servers with sql2005 standard
edition. We were just wondering which is better option, to get a server with
2 dual core processor or to get a srver with just 4 processor? How does
SQL2005 handle the hypertheading of dual processor?
Thanks,
CarlosDual core processors and hyperthreaded processors are totally different
things. Hyperthreading actually adds a "virtual" core, and is not leveraged
very well by SQL Server. Multicore processors, on the other hand, actually
behave like multiple processors -- two cores gives you two processors worth
of power. The great thing in terms of SQL Server licensing is that you only
need to pay per socket, rather than per core. So buying two dual core
processors will save you a substantial amount of money over buying four
single-core processors. And now you can buy quad-core processors, so why
not just get ONE of those?
Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Carlos" <carlosarango@.SQLserver.com> wrote in message
news:EB6E4323-8944-476E-A01B-D85B158BBB3F@.microsoft.com...
> We are in process of moving to 64 bit HP servers with sql2005 standard
> edition. We were just wondering which is better option, to get a server
> with
> 2 dual core processor or to get a srver with just 4 processor? How does
> SQL2005 handle the hypertheading of dual processor?
> Thanks,
> Carlos|||Thanks Adam, that makes sense
"Adam Machanic" wrote:
> Dual core processors and hyperthreaded processors are totally different
> things. Hyperthreading actually adds a "virtual" core, and is not leveraged
> very well by SQL Server. Multicore processors, on the other hand, actually
> behave like multiple processors -- two cores gives you two processors worth
> of power. The great thing in terms of SQL Server licensing is that you only
> need to pay per socket, rather than per core. So buying two dual core
> processors will save you a substantial amount of money over buying four
> single-core processors. And now you can buy quad-core processors, so why
> not just get ONE of those?
>
> --
> Adam Machanic
> SQL Server MVP - http://sqlblog.com
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Carlos" <carlosarango@.SQLserver.com> wrote in message
> news:EB6E4323-8944-476E-A01B-D85B158BBB3F@.microsoft.com...
> > We are in process of moving to 64 bit HP servers with sql2005 standard
> > edition. We were just wondering which is better option, to get a server
> > with
> > 2 dual core processor or to get a srver with just 4 processor? How does
> > SQL2005 handle the hypertheading of dual processor?
> >
> > Thanks,
> >
> > Carlos
>

Dual Core Processor

We are in process of moving to 64 bit HP servers with sql2005 standard edition. We were just wondering which is better option, to get a server with 2 dual core processor or to get a srver with just 4 processor? How does SQL2005 handle the hypertheading of dual processor?

Thanks,

CarlosWe are in process of moving to 64 bit HP servers with sql2005 standard edition. We were just wondering which is better option, to get a server with 2 dual core processor or to get a srver with just 4 processor? How does SQL2005 handle the hypertheading of dual processor?

Thanks,

Carlos
How about a Quad processor?

First; it will reduce the load on the mother board's Memory Bus. AMD's data-sheet on 4-core mention that "competitors" (Intel) behave more like two duo-core processors on the same backplane, but I'm not sure how far that goes but it implies that performance wise (at the hardware layer) that Intel 2-Core is similar to two 2-Core processors.

Second; Microsoft only counts it as a single CPU. So; anything licensed (from MS) by CPU will save substantially on licensing fees.

I don't have the link, so here's the quote:

SQL Server Multicore Licensing Policy
Published: August 1, 2005

Multicore processors, which consist of multiple processing execution
units or "cores" on one chip, promise to boost computing power, allowing
servers, workstations, and PCs to perform more functions simultaneously.
By the end of 2006, Intel expects more than 80 percent of its server
products to be shipping with multicore technology. Because most
server-side software is licensed "per processor," it has caused
confusion among some software vendors regarding whether to charge their
customers "per processor" or "per core."

Microsoft has been driving thought leadership in this area by charging
the same amount per processor, regardless of how many cores are in the
processor. Microsoft was the first database vendor to make this
announcement, in October of 2004, and continues to be the only vendor to
date that has taken this position. This strategy is based on the belief
that multicore processors are a natural extension of Moore's Law (that
the number of transistors on a chip doubles about every one to two
years), and that the benefits should be passed on directly to customers.

For example, if you are using SQL Server Enterprise Edition on a
four-processor server with dual-core processors, using all eight cores
(two cores x four processors), you will require only four processor
licenses. That can mean substantial savings for customers of Microsoft
compared to its competitors.

Dual Core Processor

We are in process of moving to 64 bit HP servers with sql2005 standard
edition. We were just wondering which is better option, to get a server with
2 dual core processor or to get a srver with just 4 processor? How does
SQL2005 handle the hypertheading of dual processor?
Thanks,
Carlos
Dual core processors and hyperthreaded processors are totally different
things. Hyperthreading actually adds a "virtual" core, and is not leveraged
very well by SQL Server. Multicore processors, on the other hand, actually
behave like multiple processors -- two cores gives you two processors worth
of power. The great thing in terms of SQL Server licensing is that you only
need to pay per socket, rather than per core. So buying two dual core
processors will save you a substantial amount of money over buying four
single-core processors. And now you can buy quad-core processors, so why
not just get ONE of those?

Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Carlos" <carlosarango@.SQLserver.com> wrote in message
news:EB6E4323-8944-476E-A01B-D85B158BBB3F@.microsoft.com...
> We are in process of moving to 64 bit HP servers with sql2005 standard
> edition. We were just wondering which is better option, to get a server
> with
> 2 dual core processor or to get a srver with just 4 processor? How does
> SQL2005 handle the hypertheading of dual processor?
> Thanks,
> Carlos
|||Thanks Adam, that makes sense
"Adam Machanic" wrote:

> Dual core processors and hyperthreaded processors are totally different
> things. Hyperthreading actually adds a "virtual" core, and is not leveraged
> very well by SQL Server. Multicore processors, on the other hand, actually
> behave like multiple processors -- two cores gives you two processors worth
> of power. The great thing in terms of SQL Server licensing is that you only
> need to pay per socket, rather than per core. So buying two dual core
> processors will save you a substantial amount of money over buying four
> single-core processors. And now you can buy quad-core processors, so why
> not just get ONE of those?
>
> --
> Adam Machanic
> SQL Server MVP - http://sqlblog.com
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Carlos" <carlosarango@.SQLserver.com> wrote in message
> news:EB6E4323-8944-476E-A01B-D85B158BBB3F@.microsoft.com...
>

Dual Core Processor

We are in process of moving to 64 bit HP servers with sql2005 standard
edition. We were just wondering which is better option, to get a server with
2 dual core processor or to get a srver with just 4 processor? How does
SQL2005 handle the hypertheading of dual processor?
Thanks,
CarlosDual core processors and hyperthreaded processors are totally different
things. Hyperthreading actually adds a "virtual" core, and is not leveraged
very well by SQL Server. Multicore processors, on the other hand, actually
behave like multiple processors -- two cores gives you two processors worth
of power. The great thing in terms of SQL Server licensing is that you only
need to pay per socket, rather than per core. So buying two dual core
processors will save you a substantial amount of money over buying four
single-core processors. And now you can buy quad-core processors, so why
not just get ONE of those?
Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Carlos" <carlosarango@.SQLserver.com> wrote in message
news:EB6E4323-8944-476E-A01B-D85B158BBB3F@.microsoft.com...
> We are in process of moving to 64 bit HP servers with sql2005 standard
> edition. We were just wondering which is better option, to get a server
> with
> 2 dual core processor or to get a srver with just 4 processor? How does
> SQL2005 handle the hypertheading of dual processor?
> Thanks,
> Carlos|||Thanks Adam, that makes sense
"Adam Machanic" wrote:

> Dual core processors and hyperthreaded processors are totally different
> things. Hyperthreading actually adds a "virtual" core, and is not leverag
ed
> very well by SQL Server. Multicore processors, on the other hand, actuall
y
> behave like multiple processors -- two cores gives you two processors wort
h
> of power. The great thing in terms of SQL Server licensing is that you on
ly
> need to pay per socket, rather than per core. So buying two dual core
> processors will save you a substantial amount of money over buying four
> single-core processors. And now you can buy quad-core processors, so why
> not just get ONE of those?
>
> --
> Adam Machanic
> SQL Server MVP - http://sqlblog.com
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Carlos" <carlosarango@.SQLserver.com> wrote in message
> news:EB6E4323-8944-476E-A01B-D85B158BBB3F@.microsoft.com...
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
Thanks
It's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:

> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
ThanksIt's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:

> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
ThanksIt's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:
> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>