Create Table and register it to Documentum

Hi, regarding to registered tables, is it better to create a table in a external data base and register it to Documentum or create a table inside the repository database and then register it. In which scenarios one case would be better?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

sagar.singh

Hi,

I would like to say 3 points regarding your question:

creating table in documentum database: This approach will definately reduce your dependency on other DBA to perform any database related operation and also would reduce redundancy time for db operations. create a table in same database and register it in dctm.
creating table in external database: this will make you dependent on some other DBA and also need to create an additional db connection. If thinking in relative to approach 1, this should be avoided for performance reasons.
Create Object type with super type null: This is my suggested approach and best considered, as in this case you need not to create any registeration of table to dctm. If your requiremetn is just to store some values in the table and want to retrieve in your application.

Approach 1 and 2 should be used if you are having existing tables in database and want to use data in those tables. If you are creating the new solution better use the approach 3.

Regards,

Sagar

All comments

mszurap

Hi,

There are no hard requirements on this. I suppose by other database you meant another database user (schema). Using another database is a pain, don't do it if it is not really a requirement.

If your data is closely related to your documents (for example value lists) then I advise to put the table into the same schema. If not, then they can go into another schema.

If they are in the same schema, there are no permission issues, when needed you can move your data with one schema. Using two schemas means you need to keep both in a consistent state, move both if needed, and you need to give grants to the other user.

lastnitescurry

not quite the answer to your question but some info to guide your approach

http://johnnygee.wordpress.com/?s=registered

http://developer.emc.com/developer/devcenters/ContentManagement/dfe/registered_tables.htm

http://www.google.co.uk/search?q=Using+Registered+Tables+vs+Object+Types

atmo... my current project could do with pick list data in an external database, which Documentum and Sharepoint could both see and use..... for some reason the higher ups decided that a shared database was not needed and now we are having pain with data miss match I wonder how that could have happened

also in current project, have created one of our pick lists as an object because we needed repeating attributes.

also in current project, we could do with moving a pick list table to be an object as client wants value assistance in their pick list tables!!!

sagar.singh

Hi,

I would like to say 3 points regarding your question:

creating table in documentum database: This approach will definately reduce your dependency on other DBA to perform any database related operation and also would reduce redundancy time for db operations. create a table in same database and register it in dctm.
creating table in external database: this will make you dependent on some other DBA and also need to create an additional db connection. If thinking in relative to approach 1, this should be avoided for performance reasons.
Create Object type with super type null: This is my suggested approach and best considered, as in this case you need not to create any registeration of table to dctm. If your requiremetn is just to store some values in the table and want to retrieve in your application.

Approach 1 and 2 should be used if you are having existing tables in database and want to use data in those tables. If you are creating the new solution better use the approach 3.

Regards,

Sagar