| Storage of Web Logs in Oracle [message #76905] |
Thu, 26 February 2004 04:24  |
Peppermintp
Messages: 1
Registered: February 2004
|
Junior Member |
|
|
|
We have a home-grown web app that is using a third party tool to manage the access and logging of users for our web-site. This tool produces logs which are being stored in an Oracle database. Does anyone have a 'best-practices' solution for the proper storage of these logs? Should they be stored with our production database or on their own in a separate database?
|
|
|
|
| Re: Storage of Web Logs in Oracle [message #76908 is a reply to message #76905] |
Sat, 28 February 2004 10:33  |
andrew again
Messages: 2577
Registered: March 2000
|
Senior Member |
|
|
I don't see that it's any different from any other data, so would consider it using the same criteria as you would for any other data. Is it OK to have your data in distributed systems? Will it be OK if they ever go out of sync (backup & restore together or not)? Will the web logs complicate your backup due to their sze? Will they add more load than your server can comfortably handle?
I probably wouldn't index the logs if you want the overhead to be kept to a minimum - you won't query them "often".
--simple test for index overhead
drop table t1
create table t1 (col1 number, col2 number, col3 number, col4 number, col5 number);
insert into t1 (select object_id, object_id, object_id, object_id, object_id from all_objects)
-- 13 sec, 30753 records.
commit;
delete t1
-- 2 sec
drop table t1
create table t1 (col1 number, col2 number, col3 number, col4 number, col5 number);
-- NB using default TS, so no spread load.
create index t1_idx1 on t1(col1);
create index t1_idx2 on t1(col2);
create index t1_idx3 on t1(col3);
create index t1_idx4 on t1(col4);
create index t1_idx5 on t1(col5);
insert into t1 (select object_id, object_id, object_id, object_id, object_id from all_objects);
-- 24 sec, 30758 records
commit;
delete t1
-- 16 sec, 30758 records
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
