If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Content store tables architecture

Started by Cognos8, 01 Apr 2010 08:57:11 AM

Previous topic - Next topic

Cognos8

We are exploring the content store database.I want list of content store database tables and what each tables and column does. and datamodeling of the tables.

In Content store database as i understand we are not having BLOB all files jpg files  are getting stored in webserver. is this correct?

MFGF

Hi,

IBM do not publish the structure of the Content Store database, as they reserve the right to change it for any release.

MF.
Meep!

Cognos8

Ok fine , just wanted to know how many tables are there . what are they  separate with audit tables , metadata tables , etc.. can i get those info

cogadmin

If you can access database which has your content store, you can see all content store tables, columns and data stored in them.

IceTea

Maybe this helps you a little bit. ;)


Table name     Descrition
CMSYSPROPS    This table has the Content Store Version.
CMOBJNAMES    This table has the names of all the objects in the content store.
CMOBJPROPS1    Users, Roles \ Group Distribution list and contact information such as Email, phone number, Fax Given name etc are stored in this table
CMOBJPROPS2    Report scheduling information is stored. This table has fields like hour, day week etc
CMOBJPROPS3    Stores Screen Tip and Object description provided while creating the objects are stored here
CMOBJPROPS4    Stores the printer paper setting details like height and width of A3 , A4 , letter and 11X17 paper orientations
CMOBJPROPS6    Has the details of the all packages which were published using the FM.
CMOBJPROPS7    This table stores the XML of all reports and models. This is basically to maintain the metadata about the structure of the reports and models.
CMOBJPROPS10    Contact information is stored in this table. This table has columns like Contact Email and Contact.
CMOBJPROPS11    This table stores the data sources configuration details like connect string, the cube location etc.
CMOBJPROPS13    It stores the names of parameter passed to the range prompts
CMOBJPROPS14    Has details regarding the versions, creation time etc of the objects in the content store.
CMOBJPROPS16    This table provides the status of the multiple services of Cognos like LogService, MonitorService, ReportService, SystemService, JobService
CMOBJPROPS17    Stores performance details of each component like "query Studio, Analysis Studio, Event Studio" etc
CMOBJPROPS18    This table stores the drill path from the source to the final target report.
CMOBJPROPS20    Stores details regarding which are all the reports for which prompting has been enabled. And also has the details of which are the reports which has the default report options overridden.
CMOBJPROPS24    Stores the printer configuration details
CMOBJPROPS25    Stores the data regarding the objects deployed, like the deployed folder, the reports, the number of folders present in the deployment archive, etc
CMOBJPROPS26    This table stores the data about all the packages imported / exported in C8, with the properties selected during the process.
CMOBJPROPS27    Has the details regarding the data source created in the content store using Cubes.
CMOBJPROPS30    Stores the registration , service description etc details about portlets in this table
CMOBJPROPS31    Has the custom logging level for each of the Cognos services, CMID can be be linked to CMOBJNAMES for the names of each of the services
CMOBJPROPS32    Has the details of the stored procedures used as the query items in the FM model.
CMOBJPROPS33    Detail related to users, user groups user roles.
CMOBJPROPS34    Has the details regarding the drill through parameters of the drill through reports. The parameter assign values are present in coded format
CMOBJPROPS36    Has the list of all the Models published using framework manager
CMOBJPROPS37    This table has the details of the routing sets configured for server / load balancing for each package published in the content store
CMOBJPROPS38    Configuration details about number of items to retrieve in studios, for a package are saved under this table.
CMOBJPROPS39    Has values for properties of reports and views. PROPID can be linked to CMPROPERTIES for property names
CMOBJPROPS52    Contains the properties for the connections
CMOBJPROPS55    Has the URI for icons for each entry in Cognos Connection
CMLOCALES    Has the locale ids associated with each language supported by Cognos 8

A152257


dooberry

Something to try : this will give you all of the dashboards in your content store (up to 6 folder levels deep from public folders). It requires a content store data connection in framework manager but works from the content store directly so you don't have to worry about them being moved:

Select co.name as "root folder"
   ,  dashboard
   , path

FROM (
select cmo.cmid, pcmid, storeid, name
FROM cmobjects cmo
INNER JOIN cmobjnames cmn
ON cmo.cmid = cmn.cmid
INNER JOIN cmstoreids cmstid
ON    cmo.cmid = cmstid.cmid
WHERE cmo.classid = '1'
AND cmn.localeid = 34
) co
LEFT JOIN
(
select cmo.cmid, pcmid, name, storeid
FROM cmobjects cmo
INNER JOIN cmobjnames cmn
ON cmo.cmid = cmn.cmid
INNER JOIN cmstoreids cmstid
ON    cmo.cmid = cmstid.cmid
WHERE cmo.classid = '1'
AND cmn.localeid = 34
) co1
on co1.pcmid = co.cmid
LEFT JOIN (
select cmo.cmid, pcmid, name, storeid
FROM cmobjects cmo
INNER JOIN cmobjnames cmn
ON cmo.cmid = cmn.cmid
INNER JOIN cmstoreids cmstid
ON    cmo.cmid = cmstid.cmid
WHERE cmo.classid = '1'
AND cmn.localeid = 34
) co2
on co2.pcmid = co1.cmid
LEFT JOIN (
select cmo.cmid, pcmid, name, storeid
FROM cmobjects cmo
INNER JOIN cmobjnames cmn
ON cmo.cmid = cmn.cmid
INNER JOIN cmstoreids cmstid
ON    cmo.cmid = cmstid.cmid
WHERE cmo.classid = '1'
AND cmn.localeid = 34
) co3
on co3.pcmid = co2.cmid
LEFT JOIN (
select cmo.cmid, pcmid, name, storeid
FROM cmobjects cmo
INNER JOIN cmobjnames cmn
ON cmo.cmid = cmn.cmid
INNER JOIN cmstoreids cmstid
ON    cmo.cmid = cmstid.cmid
WHERE cmo.classid = '1'
AND cmn.localeid = 34
) co4
on co4.pcmid = co3.cmid
LEFT JOIN (
select cmo.cmid, pcmid, name, storeid
FROM cmobjects cmo
INNER JOIN cmobjnames cmn
ON cmo.cmid = cmn.cmid
INNER JOIN cmstoreids cmstid
ON    cmo.cmid = cmstid.cmid
WHERE cmo.classid = '1'
AND cmn.localeid = 34
) co5
on co5.pcmid = co4.cmid
LEFT JOIN (
select cmo.cmid, pcmid, name, storeid
FROM cmobjects cmo
INNER JOIN cmobjnames cmn
ON cmo.cmid = cmn.cmid
INNER JOIN cmstoreids cmstid
ON    cmo.cmid = cmstid.cmid
WHERE cmo.classid = '1'
AND cmn.localeid = 34
) co6
on co6.pcmid = co5.cmid
INNER JOIN
(
SELECT
   name as dashboard
   , cmob.cmid
   , cmob.pcmid
   , 'http://cognos:80/cognos8/cgi-bin/cognosisapi.dll?b_action=dashboard&pathinfo=/cm&frag-header=true&path=storeID(%22'+storeid+'%22)' as path
FROM 
   cmobjects cmob
INNER JOIN
   cmobjnames cmobn
ON
   cmob.cmid = cmobn.cmid
INNER JOIN
   cmstoreids cmstid
ON
   cmob.cmid = cmstid.cmid
WHERE cmob.classid = 107
AND cmobn.localeid = 34
)db
on co6.cmid = db.pcmid
OR co5.cmid = db.pcmid
OR co4.cmid = db.pcmid
OR co3.cmid = db.pcmid
OR co2.cmid = db.pcmid
OR co1.cmid = db.pcmid
OR co.cmid = db.pcmid