Hi,
I'm curious if it's possible to use the same database for both query and content store. I have seen no mention of this in any of the Cognos support documents.
If this isn't advisable, can anyone tell me why? There is a big push here for us to use the same database for both purposes (for resource allocation reasons).
Well, I'll jump in here with my two cents' worth....
The Content Store is Cognos' database: They determine what tables are there, what columns are in those tables and how they are indexed and otherwise configured.
Now, if you went in and added a table of your content, what is to prevent Cognos from writing over it in a future release? And even if you found out that would happen, what would be the effort required to re-write everything to use a different table name? And doing that once, how happy would your company be doing it over and over for each release, each update and each service patch you installed?
Bottom line: Make your own database and do whatever you want. I don't know of any "resource allocation" issues involved in making another database on the same server.
Regards,
Opher
If you are talking about a query database where you get your data for your reports you should keep this on a separate database. It is possible to have them on the same machine but keep the cognos content store and query database separate. Cognos uses the content store to keep metadata such as folders, security definitions, and even your reports.