locked
Too many records in the Security Log (Type “Success Audit”) RRS feed

  • Question

  • I have VB.Net application. It uses SQL Server 2005 as back-end. In the application data access component opens and closes connection to the server for every database call (stored procedure). By default settings application uses connection pooling.

    System Administrator reports that security log is flooded with “Success Audit” records that generated by the application users.

    1. Is it normal to have security log record for every database call (even with connection pooling)?
    2. As number of users increases, how it could impact security auditing, and performance of the Windows Server?
    Tuesday, July 21, 2009 2:56 PM

Answers