Database structures changing and catalogs

[mbarka]

Hello,

I'm creating a database. This one changes every week : name of fields, new tables.

In the same time, I'm creating a Cognos catalogs, and it changes every week too, becuse of changing in the database.

How can I refresh the new database structure and use the new name of fields, or new tables, without create a new catalog?

I'm sorry for my bad english.  :-\

Thanks for your responses

M. Barka

[ngalemmo]

Every week?  Have you considered rethinking your database design?

[mbarka]

Sorry, but my boss want to increase some functionnality, and i have to add few columns, or modify columns names.
That's why I post my questions in here!

Thank you for your response.

Mehdi Barka

[cognosfreelancer]

Hello Mbarka

We would want your boss to be happy ;)

I would suggest that you create aliases in your catalog for all database tables.

Periodically you would need to carry out the 'Verify' operation to determine whether the catalog has fallen out of sync with the underlying database tables or not.

If it is the column that is not in sync you will need to delete and recreate the column.

If is the whole table then you will need to recreate the alias from the table. Make sure you copy the alias name to clipboard and paste it back.

Keep in mind two important things:

- you will have to recreate joins almost always

- You will need to create catalog aliases directly off the database tables. This means you should not bring in a database table to the catalog and create aliases off it. Failing to do this will make me unhappy  ;)but more importantly will prevent you from modifying catalog tables correctly.

This approach will ensure that your folders will continue to remain intact.

Hope this helps
NKT

[cognosfreelancer]

Correction...

do not delete the alias when the underlying table changes
rather, keep the alias and change columns as needed.

else

folders will change

NKT