CMS, Audit Database in the Application Database Schema

Hi,

I have a drive dedicated to the Application Data in SAN. It’s space is sufficient to have Application Database as well as CMS+Audit Database. Is it a good approach to store Application Database and CMS database the same Schema? What issues I can foresee?

Thank in advance for your help on this.

SG


gudurusk (BOB member since 2010-05-29)

Short answer is no.

You didn’t specify which database you are using, but there are two considerations I can think of:

  1. Audit tables grow constantly, and can potentially take up a lot more space than the CMS tables. If the audit, datamart, and CMS table share the same space, you could potentially have a problem in which the audit tables use up all available database space, thus causing the CMS to crash when it tries to write out its metadata. In Oracle, it’s possible to put specified tables in a schema on a separate tablespace, which would mitigate this issue.
  2. Assuming you have a universe over the datamart, then the CMS tables would be visible to universe designers (via the connection) or ad-hoc users (by modifying SQL). While there’s not much in the CMS tables that human-readable, it opens the door to possible vandalism.

Joe


joepeters :us: (BOB member since 2002-08-29)

It’s simply a bad practice to mash all your data into 1 schema. It makes backup/restore much more difficult.

At least sepearate the CMS and Audit into a different schema. Putting them on a different instance is even better.


Steve Krandel :us: (BOB member since 2002-06-25)

I installed BOE XI 3.1 using the New installation option and it installed and configured the CMS and Audit databases into MySQL.

Can someone tell me how I can re-install the Audit database so that it goes to Oracle and leave the CMS in MySQL? Also, is it recommended to keep the CMS and Audit DB in different database systems?

thanks!


gjwl_8 (BOB member since 2010-02-17)