it is technicaly possible and I already saw it but I don’t advise you to do such thing. In fact, audit database can increase quickly and, in the other hand, if you perform heavy queries on audit database you run the risk to break the tablespace. it is not a big deal on a dedicated audit database but if your cms and audit database are hosted on the same schema, your bo platform will be out of order…
Depending on how important these reporting information and audit information are to the company, your management might be shooting themselves in the foot by going cheap on Oracle licenses. It is a very bad idea to commingle the system database and audit database.
You can assign different tablespaces for the system database and audit database to avoid the resource conflict. But I can guarantee you to run into a lot of problem down the road.
Ask your dba and he will become crazy. Audit database must be setup (parameters) to store transactional data whereas the CMS database must be setup to store BLOB data …
Agreed, plus I would imagine your non-standard way of doing things would invalidate your support contract, as well as make BOXI perform badly - food for thought?
Chris, maybe I’m simplifiying things here, but wouldn’t it be as simple as moving the audit tables, to the new database, then repointing the connection on the server, then changing the path in the CMC?