Post reply

Disabling writing to Windows Application Event Log

  • October 1, 2010 at 8:50 am

    #142104

    Hi, I was asked to stop the windows event log on a couple servers from being filled up with "succesful login" messages from SQL Server.

    I set the audit level to "failure only". This stopped the messages from appear in the SQL Logs but not the Windows logs.

    How do I stop SQL from writing to the Windows Application event log?

    Looking in books online I found references to "if it is enabled" but not actually how to enable/disable it.

  • October 1, 2010 at 8:57 am

    #1230279

    right click on the servername...properties...the security tab:

    change to failed logins only, and i think you are all set.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • October 1, 2010 at 9:27 am

    #1230310

    As I mentioned I did try that, but it only affected the SQL Logs, not the Windows Logs.

  • October 1, 2010 at 1:22 pm

    #1230468

    Was the SQL Server instance restarted after making these changes?

    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @pradeepadiga

  • October 1, 2010 at 3:21 pm

    #1230559

    Adiga (10/1/2010)

    Was the SQL Server instance restarted after making these changes?

    Yes, it's rebooted nightly.

  • October 5, 2010 at 11:12 am

    #1231911

    bump

  • October 5, 2010 at 10:58 pm

    #1232228

    Just a guess. Is there another instance of SQL Server running on that server?

    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @pradeepadiga

  • October 6, 2010 at 6:55 am

    #1232467

    Are the login events originating from sql server or from Windows/Active Directory?

  • October 6, 2010 at 10:13 am

    #1232765

    After looking into this more I found out that the server people were incorrect... the change DID fix the problem, and the messages they saw were from BEFORE I made the change.

    Thanks to those that tried to help.

Viewing 9 posts - 1 through 8 (of 8 total)

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