We use Oracle DB for CMS system database. Is it OK to install Audit database into the same schema as CMS system DB is in? Or is it better to use a separate schema for Audit DB?
If I installed both in the same schema what problems I might experience in future?
I have checked BOB forum as far back as 2006 and found nothing useful. Also Auditor guide is not very helpful in this regard. This is the only thing they write about Audit DB vs system DB:
Marek,
Why would you want it that way? Wont you be better off having it separately?
Firstly, I am not sure if it will allow you to build auditing repository tables into the same schema as CMS.
If yes then in my view there can be couple of repercussions.
Like the backup and restore of CMS dump including auditing database. You may only want to restore CMS repository tables and so auditing will also be part of it(though it may be separated), there can be discrepancies and it wont be a quick and direct restore.
The database itself will grow too big over a period of time and there can be a performance issue(I am not a DBA expert but feel that it will be difficult to maintain two different types of information written in one single database schema)
Yep definitely the CMS must be in a different schema and even a different instance. Nothing must interrupt your CMS thus your BO user activity due to technical problems …
I will have these 2 databases separated. But for now, I can’t avoid having them in 1 Oracle instance. So they will be as separate schemas in 1 Oracle DB.
I’d recommend not only separating the audit and cms databases, but put them on separate servers. A classic issue is trying to do reporting on an OLPT system. Separating by instance helps, but if the server becomes resource constrained due to reporting against the Audit database you will affect the CMS database and BOE overall.
(BOB member since 2003-11-27)
(BOB member since 2005-07-18)
(BOB member since 2003-11-27)
(BOB member since 2006-10-23)