May 29, 2009 at 4:09 am
I have an active event notification service tracking logins.
On one server this causes an issue.
Dropping that service takes more than 22 minutes.
SQL2005ee (x64) 9.00.3068
Any hints ?
(I cannot stop the instance 24/7)
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
June 1, 2009 at 6:44 am
This might be the SQL Server service. Probably not a good idea to kill the service behind the scenes.
June 1, 2009 at 11:59 pm
I didn't kill the sqlserver service !
I dropped the event service (sqlserver object).
DROP SERVICE S_Logon_Events_Service
There was a huge backlog because I defined to few quereaders.
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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply