Joe, The recommended method is using a separate central repository for this kind of audit volume. The audit log archiving feature (see DB Audit's manual) is the method for that. Incremental logs can be shipped near real-time from different database servers and even different database systems and loaded into the central repository. The repository can be then used for reporting and alerting. You can use any supported database system for the central repository, however MS SQL is the easiest to manage. Please use database tools discussion board for all DB Audit related questions
http://www.softtreetech.com/cgi_bin/mconfig.cgi?index : I read in the FAQ… : Q: Where is the audit log stored?
: A: Audit log is stored within audit trail tables created in your database.
: For multi-database servers like SQL Server or Sybase ASE, DB Audit can
: install audit trail tables in the database being audited or in a different
: database on the same server. : If we are looking at monitoring 10’s of instances of databases can all of the
: information be put in one database on a different server, if so, how is
: that configuration attained, because due to the level of auditing that we
: might be tasked with we don’t want to consume unnecessary space on our
: production databases if the audit log tables can be placed on other
: hardware that has a sole purpose of storing audit data.
|
