By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,439 Members | 1,315 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,439 IT Pros & Developers. It's quick & easy.

need information on SQL SERVER 2000 with multi-threading CPU

P: n/a
Hi,
I have SQL SERVER 2000 SP4 Enterprise , Windows 2003
Enterprise on
Xeon 4 Processors (now with multi-threading CPU) and I have
questions which
seem weirds to me (used to have the same config without
Multi-Threading) as following:
1. SQL Server see 8 CPUs. Is this because of
multi-threading CPUs ?
2. when use SP_WHO2 ACTIVE ,
2.1 Result has user SPID , which block
itself
(it is UPDATE and SELECT
statements, most often)
2.2 Result has user SPID , show more
than one result rows with
the same processe and command
3. when use Properties of SQL Server , it has an
error 15407 in log.

many thanks in advance
NiponW

Nov 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
SQL Server sees 8 CPUs because the OS sees 8 CPUs. Windows 2003 is
hyper-threading aware, so you shouldn't worry about SQL 2000 not
handling parellelism well (although SQL 2005 is supposed to do it
better). If this were a Windows 2000 box, I would recommend turning
hyper-threading off.

Regarding SP_WHO2: Often times processes block themselves. I wouldn't
worry about it too much unless you see many processes blocked. Also,
sometimes processes do show up multiple times and you may find the
difference in the SP_WHO2 output or you may not. But the different
values will be in the sysprocesses table if you were to correspond each
SPID from the output to the table.

Error 15407 means invalid login. That happens all the time with SQL
Server. If see you a lot then someone may be attempting to hack into
your server. You are lucky if it is a domain user (e.g.
EURODOMAIN\JOHNSMITH) because you can go to his desk and hit him with a
stick. If you only see the error from a SQL login, then you should open
a Profiler window and perform a trace on Login:Failed and be sure to
check the HOSTNAME column. You can at least bring that information back
to your network group and possibly trace the person that way.

Nov 23 '05 #2

P: n/a
Hi

Have a look at this thread:
http://groups.google.com/group/micro...513ab281?hl=en

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mi**@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"NiponW" <ni****@yahoo.com> wrote in message
news:11**********************@g49g2000cwa.googlegr oups.com...
Hi,
I have SQL SERVER 2000 SP4 Enterprise , Windows 2003
Enterprise on
Xeon 4 Processors (now with multi-threading CPU) and I have
questions which
seem weirds to me (used to have the same config without
Multi-Threading) as following:
1. SQL Server see 8 CPUs. Is this because of
multi-threading CPUs ?
2. when use SP_WHO2 ACTIVE ,
2.1 Result has user SPID , which block
itself
(it is UPDATE and SELECT
statements, most often)
2.2 Result has user SPID , show more
than one result rows with
the same processe and command
3. when use Properties of SQL Server , it has an
error 15407 in log.

many thanks in advance
NiponW

Nov 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.