January 13, 2009 at 6:19 am
Feedback:
I've upgraded the dev servers to SP3 and got the approval to re-test it in cooperation with one of our biztalk devs.
After I activated the "old" logon trigger again, the issue no longer occurred.
So I guess it may have been related to the bug and fix mentioned earlier.
After the test I removed the logon trigger, because the proper way of handling this is asynchronously.
The lessons learned still apply !
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
January 13, 2009 at 11:26 am
Thanks for the update and appreciate your working attitude, i.e. never leave anything unsolved.
January 4, 2011 at 6:45 am
Event notification works. I use a server-side trace for login events to get the same sort of data, mainly just because I've been doing that for eons at this point and am comfortable with it.
Definitely a good article.
Another thing to keep in mind, that was mentioned in the article, but I didn't see anything in the dicussion on it: Don't rely on people in testing. I use traces of real activity to make sure things like this won't have unintended consequences.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
January 6, 2011 at 12:19 am
Thank you for you comment.
I need to add 2 comments to the article:
1) You need to setup queue monitoring !
If things fail, your server may blow up really fast, depending on the number of logins occuring.
msdb may grow, or the db where you defined your queues
2) Until now, SSB did freeze on 4 of our +200 instances.
Mostly the reason was the query on the queue received a "insufficient memory to complete the query" notification, causing the sproc to fail. Queue blew up, until disk got full !
If was a hell of a job to analyse the root cause and to clean it up.
I needed to beg for more ram on these very small systems, but they got fixed 😉
In a single case, the sproc was just to slow to cope with the queue load. After the modification to using the checksum column, things are running smoothly. :w00t:
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
October 29, 2021 at 10:42 am
Please also read the follow up article "Logon monitoring in SQL Server and Azure Managed Instances - Adopting Extended Events"
Another enhancement to avoid the downsides of notification service queues
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 5 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply