Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Long query - 100%CPU

Status
Not open for further replies.

francox

IS-IT--Management
Jul 19, 2001
26
CH
SQL 7.0 SP1 - NT 4.00 EE SP6a - Cluster - Multiprocessor(2)-VB 6.0 SP4.
Maybe a very stupid question,but I need to know if it is possible to assign a low priority to a VB exe that query for long time eating all the CPU (100% in task manager).
Thank you.
Franco
 
You could set SQL Server afinity to one single processor. John Fill
1c.bmp


ivfmd@mail.md
 

As far as I know, you can't set the priority for the query. The best thing you can do is determine why the query is consuming so much resource and is running so inefficiently. Terry L. Broadbent
faq183-874 contains some tips and ideas for posting questions in these forums. Please review it and comment if you have time.
NOTE: Reference to the FAQ is part of my signature and is not directed at any individual.
 
I didn't mean a query. You can do it only from Enterprise Manager. John Fill
1c.bmp


ivfmd@mail.md
 
Thank you again to all of you!
Maybe I need to expand a little my question.The fact is that this extremely complicated query run without problem in about 5 seconds on my "low cost" Intellistation E PRO 384 MB Ultra 160 SCSI.
The same query never succeed on our super "High cost" 2 node cluster Netfinity 7000 M10 fibre channel, 800 MB memory 2 processor, Raid disk...
We already tried to select only one processor for queries on the SQL Server processor properties, without results, the query never ends and the CPU is for very very long time at 100%.
We also want to try to change the value of the "cost threshold for parallelism Option", but I need to tell SQL Server to use all available processor and for that I need to stop and start SQL Server.
Maybe now it is a little bit more clear, in fact I d'ont think the query is the problem.
My fisrt question was posted only to see if it was possible,for the moment,to run it on a lower priority, but I am pretty sure that the problem has something to do with the processors and the parallelism parameters.
So again, if someone has some idea on what to do to resolve this problem, I will be very very thankfull.By the way...sorry for my English!
Regards.
Franco
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top