Good morning, please, has anyone used logins audit without using the Profile?

My client needs an audit that displays the logins that connected to the bank and after they disconnected.

In the case the profiler believe it is too heavy to keep active all the time collecting.

Do you have anything that might help us in this case?

thank you Carol Lavecchia

  • 1
    Are they actual separate logins according to SQL Server, or are they using an application-based login system but the application itself always connects as a single login? I can't imagine every bank customer has a SQL principal... Dec 22, 2017 at 19:11

3 Answers 3


Seems like a perfect use case for Login Auditing. This will require a restart of the SQL Server.

Then, I would use xp_readerrorlog to view the results. Something like:

xp_readerrorlog, @p1 = 1, @p3 = 'Login'

I'd recommend the use of SQL Server Audit.


You can check the configure the SQL server security to log the sucessuful login (right-click on the server / Property / Security / click on the log option you want).

You will then be able to track the user that log on the instance by looking at the SQL server Log (xp_readerrorlog, @p1 = 1, @p3 = 'Login')

For the disconnection, you can create a server audit with the "logout_group" as the audit action type.

You can make the audit log in the application log or in a file.

Hope that helps.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.