February 17, 2010 at 4:36 pm
..and be VERY CAREFUL with those Login triggers. I once accidentally locked everyone (Including SA :Whistling:) out of a critical server because of an errant Login trigger configuration. Brush up on your DAC procedures... :w00t:
February 18, 2010 at 7:34 am
Ray,
I am very familiar with the DAC procedures. Which is the reason I gave up on Logon Triggers. I wanted to avoid running a profiler in the background to see which accounts are active. However, Especially on shared SQL environments it can take a while before someone logs into a particular database.
February 18, 2010 at 7:46 am
We are using sql server event notifications to capture the audit_login events.
cfr: http://www.sqlservercentral.com/articles/Administration/64974/
This works fine on all our servers, except for one that has +50 logins per second.
If you want a look at the involved DDL ....
have a look at http://www.sqlservercentral.com/Forums/Topic851938-1281-1.aspx
I recently altered the table and queue related sproc to take advantage of the checksum function because it raises its performance.
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 16, 2014 at 3:55 am
The default trace should give you an idea, depending on how long your logs go back.
Then/if the above bears no fruit.
Server-side trace to capture the ones you suspect of being disused.
Carlton
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply