can I lower priority on threads in SQL Server 2005 (64 Bit)?

Question

Post reply

can I lower priority on threads in SQL Server 2005 (64 Bit)?

Musa-289130

Grasshopper

Points: 20
More actions
February 1, 2006 at 4:18 am

#166738

Hi Everyone,
I can have multiple jobs running on the SQL Server 2005 (64Bit) – slowing down the system, but need to keep an opening for a client 24/7 and not be late returning the records the client wants. If I somehow could lower the priorities on the jobs then the client would always have a higher priority.

Anyone know how this can be solved? please any help is appreciated.

thanks in adv.

Musa

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Johan Bijnens SSC Guru Points: 135376 More actions · Answer 1

Are you looking for set deadlock_priority low ?

This way the executed statement is prefered victim for deadlock handling.

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Musa-289130 Grasshopper Points: 20 More actions · Answer 2

I have been away for few days... but to no I’m not looking for set deadlock_priority low.

To give you an example which might be more easy to understand.

Lets say I have 3 jobs running on the SQL Server, all 3 running for hours – and using a lot of cpu. If I could lower the priority on those 3 jobs, then a new job with a higher priority should be able to finish off faster.

In my case I have one job which should be able to run any time on the day, and more than once a day, I also have many other jobs which would run daily, but time is not a matter for those jobs, it is only for the one I haven’t got control over. If I somehow could be able to set the priority lower for those jobs where time isn’t important and keep a normal priority on the one which really needs to finish fast, then my problem would be solwed.

best regards

Musa

Johan Bijnens SSC Guru Points: 135376 More actions · Answer 3

I was aware of the concept you had in mind , but I don't think this is implemented in sql2005.

I think Windows WLM is at service level, so will also not solve this kind of problems because sqlagent serves #-jobs.