hi,
I have sql server 2k with sp3 on win2k advanced server.
the sqlserver.exe is consuming 95 to 100% of cpu and the cpu remains at 100% percent most of the times.
I have checked with the profiler but could not find anything fishy.
any help would be highly appreciated.
Regards,
Harshal.Is there anything running at all? Perhaps a block/lock? I would suggest contacting PSS if this problem persists.|||what is pps?|||Originally posted by harshal_in
hi,
I have sql server 2k with sp3 on win2k advanced server.
the sqlserver.exe is consuming 95 to 100% of cpu and the cpu remains at 100% percent most of the times.
I have checked with the profiler but could not find anything fishy.
any help would be highly appreciated.
Regards,
Harshal.
I am currently running windows XP and having the same problem. The only way to fix it is to shut the program down through program manager and it does not affect my operating system. Have you found anything further on this issue>
?|||I could be wrong, but this sounds like the SQl Slammer worm. Microsoft have published details how to deal with it:
http://www.microsoft.com/security/slammer.asp
--Original Message--
I am currently running windows XP and having the same problem. The only way to fix it is to shut the program down through program manager and it does not affect my operating system. Have you found anything further on this issue
Showing posts with label increased. Show all posts
Showing posts with label increased. Show all posts
Thursday, March 8, 2012
Cpu Usage 100% On 6.5 Sql
we have CPU Usage upto almost 100% i increased the tempdb, and master to almost double the size
then we increased the memory to high amount.
does anyone have suggestion pls help since it running too slow, since we did an upgradeUpgrade from what?
To 6.5?
Turn on Profiler to see what's going on.
How's is you r box configured.
Is SQL the only service on the box?|||Sorry Brett, no profiler on MS-SQL 6.5.
I'd be interested to know what the hardware/OS/software configuration is. MS-SQL 6.5 would run on a bare-bones Pentium, and maybe even on a 486. Some of those machines had 512 Kb of RAM or less.
I don't know that we even know enough to ask good questions yet, much less offer suggestions for how to fix the problem(s).
Is an upgrade to hardware/software less than five years old possible?
-PatP|||Sorry for being so incomplete
I am on window 2000 server running 6.5 sql , had upgraded the vendor application that runs on 6.5 this server ( only thing on box)
ram 3 gb and server 1.4 mhz with raid drive
was running well till this upgrade now.
we increased temp db, master , memory (sql configuration)
size of database 20 gb|||When you use the NT Task Manager, is SQL Server actually running the CPU wild, or is it only part of your problem?
There was a known problem prior to sp5 where SQL Server would go mad trying to manage more than 2 Gb of RAM. I assume that you are at sp6, right?
Try to use sp_who to identify long running tasks, then DBCC INPUTBUFFER to determine what SQL statements those tasks are running.
-PatP|||Yes sql is causing the wild ness
and i taught that 6.5 has only uptill spack 5a
http://www.microsoft.com/sql/downloads/servicepacks.asp
My window 2000 server has service pack 4|||You can try to use SQL Trace to catch some of the activity (queries) in the server. SQL Trace is the SQL Profiler ancestor.
What sort of application is this? Can you take parts of it down to narrow your search? And also, has the vendor said anything like "Oh, yeah. I remember this happened to another client with that setup."|||It was not tested on 6.5 but on 2000 ,
Now they are saying|||If SQL-2000 is an option, go there, NOW!
then we increased the memory to high amount.
does anyone have suggestion pls help since it running too slow, since we did an upgradeUpgrade from what?
To 6.5?
Turn on Profiler to see what's going on.
How's is you r box configured.
Is SQL the only service on the box?|||Sorry Brett, no profiler on MS-SQL 6.5.
I'd be interested to know what the hardware/OS/software configuration is. MS-SQL 6.5 would run on a bare-bones Pentium, and maybe even on a 486. Some of those machines had 512 Kb of RAM or less.
I don't know that we even know enough to ask good questions yet, much less offer suggestions for how to fix the problem(s).
Is an upgrade to hardware/software less than five years old possible?
-PatP|||Sorry for being so incomplete
I am on window 2000 server running 6.5 sql , had upgraded the vendor application that runs on 6.5 this server ( only thing on box)
ram 3 gb and server 1.4 mhz with raid drive
was running well till this upgrade now.
we increased temp db, master , memory (sql configuration)
size of database 20 gb|||When you use the NT Task Manager, is SQL Server actually running the CPU wild, or is it only part of your problem?
There was a known problem prior to sp5 where SQL Server would go mad trying to manage more than 2 Gb of RAM. I assume that you are at sp6, right?
Try to use sp_who to identify long running tasks, then DBCC INPUTBUFFER to determine what SQL statements those tasks are running.
-PatP|||Yes sql is causing the wild ness
and i taught that 6.5 has only uptill spack 5a
http://www.microsoft.com/sql/downloads/servicepacks.asp
My window 2000 server has service pack 4|||You can try to use SQL Trace to catch some of the activity (queries) in the server. SQL Trace is the SQL Profiler ancestor.
What sort of application is this? Can you take parts of it down to narrow your search? And also, has the vendor said anything like "Oh, yeah. I remember this happened to another client with that setup."|||It was not tested on 6.5 but on 2000 ,
Now they are saying|||If SQL-2000 is an option, go there, NOW!
Subscribe to:
Posts (Atom)