Post reply

Database Activity Monitoring/Auditing

  • September 1, 2006 at 5:30 am

    #367304

    I'm wondering if anyone has tried to set up auditing on databases that are particularly active, and generate a lot of extraneous information in the normal operation of the application.  For example, the 'sa' account may be used by the application to create and drop tables, move data around, generating tens of thousands of records in the process.  It may also act on behalf of the user, effectively masking who was doing what.

    I'm curious what products may have been used, and what kind of filtering you apply.  I'm even curious who may have segregated duties to lessen the requirement for monitoring.

    Thanks.

  • September 4, 2006 at 8:00 am

    This was removed by the editor as SPAM

  • September 4, 2006 at 6:41 pm

    #658449

    The way we've set up auditing is to Create a local windows group and put Global group (which has all the domain users) and grant the loacl group execute permission on sps.

    Then Create triggers on the table to capture the users. This has worked fine for us.

    Hope this helps

    Sreejith

  • September 4, 2006 at 7:11 pm

    #658453

    Thanks Sreejith.  I appreciate that, and knowing any other ways people have handled things.

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

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