Audit and Error Log Tables

I've seen it done before that tables that contain Audit logs and Error data
are sometimes placed in a different database.
As some apps log user actions in quite a bit of detail these tables can get
quite big and make the database grow quite large.
I just wondered what peoples thoughts on this approach are. Other than the
size of the database does have a couple of massive tables have any impact on
the performance of the database.
TIA
MattC> I just wondered what peoples thoughts on this approach are. Other than
> the size of the database does have a couple of massive tables have any
> impact on the performance of the database.
Large audit tables won't negatively affect performance. You'll incur the
write overhead regardless of the database in which the tables reside.
The main issue with large tables is manageability. Audit tables are
particularly good candidates for SQL 2005 partitioning because they are
often large and can often be partitioned by date.
Hope this helps.
Dan Guzman
SQL Server MVP
"MattC" <m@.m.com> wrote in message
news:OVTeThWkHHA.4800@.TK2MSFTNGP02.phx.gbl...
> I've seen it done before that tables that contain Audit logs and Error
> data are sometimes placed in a different database.
> As some apps log user actions in quite a bit of detail these tables can
> get quite big and make the database grow quite large.
> I just wondered what peoples thoughts on this approach are. Other than
> the size of the database does have a couple of massive tables have any
> impact on the performance of the database.
> TIA
> MattC
>|||Hi,
We have a database that archives modified records to a separate database.
One drawback of that design is security management. Every time a new user
or domain group is granted write access to the main database, I have to
remember to add the login to the archive database as well.
Daniel Jameson
.............................
.
You don't have to agree with an artist's opinion
to appreciate the art with which he expresses it.
"MattC" <m@.m.com> wrote in message
news:OVTeThWkHHA.4800@.TK2MSFTNGP02.phx.gbl...
> I've seen it done before that tables that contain Audit logs and Error
> data are sometimes placed in a different database.
> As some apps log user actions in quite a bit of detail these tables can
> get quite big and make the database grow quite large.
> I just wondered what peoples thoughts on this approach are. Other than
> the size of the database does have a couple of massive tables have any
> impact on the performance of the database.
> TIA
> MattC
>