> on the way, with a fully normalised & relational (we'll say
> it is for arguments sake!) Oracle database running the show
> underneath. I've got a db table dedicated to keeping logs of
> the activity this application will produce, which in keeping
> with the relational model has about 5 links to other tables.
>
> Bearing in mind this log table will store a significant
> amount of data when the applications fully operational - and
> the data will act as an audit trail - do you recommend:
>
> a) Keep the table relational with the rest of the
> database (5 table links, potential for slow querying to
> produce reports)
> b) Have the table as a 'dump' whereby all data except
> the primary key is inserted and there are not relational
> links (faster querying for reports)
> c) Any other suggestions?
Generally, it isn't usually important for logging to fit within a relational
framework. Given that every significant event may produce a log entry, you
typically want to focus on the efficiency of logging operations. That said,
there are probably plenty of exceptions to these generalizations.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
