One Database, Multiple Apps

Hello all -

I have one medium-large production database here. Our system is hybrid but more similar to OLTP.  As far as I know quick inserts are not a problem.

I need to implement tracking software, where all I'd have to do from the database side is just collect records very quickly without impacting the speed of page views.  This tracking software connects via JDBC and really does not care about dbms versions.  I am thinking of just implementing a schema in my current database for this purpose and making the table as quick for inserts as possible (no primary key, minimal indexing, PCTUSED set appropriately, etc.) 

Honestly I can't think of a good reason for creating a separate database other than I'd be creating a bunch of configuration work for myself as well as modifying our backup and recovery strategy (which I am comfortable with doing).  Any reporting off this raw data will be done in a "reporting" database, or off Cognos cubes.    I thought about any advantages to having one database available when the other is down, and really there are none (if one is down, the entire application will not be available). 

Has anyone had to configure databases in this manner and if so, what other ideas came into play when deciding whether or not to have one database serve more than one application?  Thanks for any comments you may have.

Lisa Rutland Koivu
Oracle Database Administrator
Qode.com
4850 North State Road 7
Suite G104
Fort Lauderdale, FL  33319

V: 954.484.3191, x174
F: 954.484.2933 
C: 954.658.5849

"The information contained herein does not express the opinion or position of Qode.com and cannot be attributed to or made binding upon Qode.com." Received on Mon Mar 12 2001 - 11:11:41 CST