Post reply

how to Audit/Record each and every statement run through SSMS.

  • October 9, 2017 at 11:14 am

    #402583

    Hi Team,
    Is there any better way to store the audit information run through ssms? Please suggest

  • October 9, 2017 at 11:51 am

    #1962872

    dastagiri16 - Monday, October 9, 2017 11:14 AM

    Hi Team,
    Is there any better way to store the audit information run through ssms? Please suggest

    Better than what?

  • October 9, 2017 at 1:34 pm

    #1962883

    dastagiri16 - Monday, October 9, 2017 11:14 AM

    Hi Team,
    Is there any better way to store the audit information run through ssms? Please suggest

    Just for yourself, or a centralised solution for everyone?

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • October 10, 2017 at 9:02 am

    #1963034

    Do you mean data captured from SQL Audit? Or do you mean track all activity that is executed through SSMS? If it's the latter, you can set up some auditing/extended events to look for the program name from sys.dm_exec_sessions, but this isn't guaranteed. It might be good enough for you, but be aware that this could be a problem.

    Typically the name is " Microsoft SQL Server Management Studio - Query", but this might be different across different SSMS versions.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply