Database Schemas of Applications in Cognos Planning

 When you create a contributor application, its data and structure is stored in the database which you configure the PAD with. Application is created with 2 schema in database similar to the name below.

1. “application name separated with under scores”

2. “application name separated with under  scores”_table

For example if your application name is “go expense contributor” then there will be 2 schema in database for this application.

1. go_expense_contributor – This contains the application’s detailed structural information. Everything you see, be it the jobs of application under job management or the access details of e-list items, is stored in this schema.

2. go_expense_contri_table – this contains the publish tables and their structural details.

Important tables to note in these schema are specified below

 AdminOption-

this table contains all the admin details like application’s PAD name, PAD GUID, PAD Namespace, Sql/other database file location, import details (block size, location, options etc.), application display name, current users, db version etc.

You can change the display settings of application or other details by updating this table.

IM_ tables-

IM tables are import tables. When you want to load the data from some external source for example a file or a database, you use IM tables as a staging area to load data.

One IM_ table is created for each cube in the application. If there are 5 cubes in the app. there will be 5 IM_ tables, one for each.

IM tables can be loaded from some database or from a text file. To load the data from a text file, you can use the “Import Data” feature in CAC.

To load the data from a database, you should use SQL to insert the data into IM_ tables.

IE_ tables-

There is one IE table per analyst model cube. These tables store the error details of import.

NodeState table-

This table is used for saving and reviewing the e-list nodes on the web contributor. Annotation information, editing user’s information (e.g. date, time, GUID) lock information etc. is kept in this table. Data for e-list nodes is saved in xml format.

Job table-

This table contains one row for each job currently in the job management tree node in contributor (CAC)

_table

As I mentioned before, this schema hosts publish tables and their structural details. There are mainly 3 types of tables to notice.

Et_ tables-

These are publish tables and 1 table is created for each published cube.

It_ tables-

These contain the structural details of the publish tables and one table is created for each dimension of published cube.

Cy_ tables-

These contain the structural details of the publish tables and one table is created for each dimension of published cube.

Sy_ tables-

These are system tables and contain the structural details of the publish tables and one table is created for each dimension of published cube.

Source by Rich Panama

Leave a Reply

Your email address will not be published. Required fields are marked *