Title: Message
|
Hi
all,
We've got a table in our DB thats a log table. Basically everytime anyone
does anything in our intranet site i'm logging it so we can use this data for
reporting and analysis etc.
We
recently archived 5million records in this table to csv file as the DBA was
freaking out about such a large table.
We
noticed no performance issues on the user end and not sure how the server was
coping but we had no outages for ages either.
In
your experience whats best practise here with log tables etc?? Now when i run my
reports (web interface) we don't have pre "archive" date data display which
kinda ruins the reporting experience.
Any
tips, suggestions on this would be great
thanks
matt
**********************************************************************
A new world of colour, sound and pictures awaits you:
Vodafone Live! More details at http://www.vodafone.com.au/live/
**********************************************************************"
This correspondence is for the named person's use only. It may
contain confidential or legally privileged information or both. "
No confidentiality or privilege is waived or lost by any "
mistransmission. If you receive this correspondence in error, please
immediately delete it from your system and notify the sender. You
must not disclose, copy or rely on any part of this correspondence
if you are not the intended recipient.
Any views expressed in this message are those of the individual sender,
except where the sender expressly, and with authority, states them to
be the views of Vodafone.
This email has been checked for viruses.
**********************************************************************************************
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
|
