Michael L John wrote:
Why don't you ask this question in the original thread?
That's almost funny, Michael... how many times have we seen people say "start a new thread for a different question" even if it's a related question?
I'm with you that there's nothing wrong with asking a question on a related thread. Most folks that answer questions monitor for all questions and additional posts anyway.
Shifting gears to the question at hand... one fairly easy method is to change the server setting to capture all logins in the SQL Server error log. Some find that annoying because it can hide problems if you don't now how to filter or you don't now how to read the contents of a log file using a bit of unsupported but commonly used code. I agree that's a bit of a mess but it is fairly safe.
Another way is to make login triggers for the server. The spooky part there is that if you do it wrong, you won't be able to log into the server. Still, the correct methods are fairly well documented if you Google for them. I do recommend testing any solution on a "burner" instance before applying to a real server.
You can also buy software that will do all of this for you and take it out of reach of DBAs if you need audit information for potential court appearances or SEC guaranteed audits, etc.