Importance of custom table entries in dm_registered during migration

Hii all,

Can anybody please explain the importance of custom tables in the dm_registered as why they are created and what they mean and what their effect will be on migration.

Thanks and regards,

Sumit

Find more posts tagged with

Comments

christopher.imes

Sumit,

Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and questions can go unanswered for a long time.

You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "Documentum" (Developer Network) which would be the most relevant for this question.

Sumit_Kumar31

Thanks Chris

msroth

The dm_registered table holds definitions and links to database tables that are not part of Documentum's core database deployment. For example, if you had a set of tables that listed an agency's departments and department heads you could register these tables and then use them in DQL queries to determine whether a user was the head of a department. Depending upon how you are migrating your repository, and where the registered database tables reside, they may not migrate with the rest of the Documentum database, or may require special attention. I'm sure one of the DCTM guides discuss registered tables more thoroughly than this.

Sumit_Kumar31

Thanks Scott for your reply. It has been really helpful. However, i tried to find out more about the same in the DCTM guodes, but was not able to find anything. Could you please share me the link to any guide where i can get something more regarding teh same?

PanfilovAB


Scott Roth wrote:

The dm_resgistered table holds definitions and links to database tables that are not part of Documentum's core database deployment.

In our projects we had never used registered tables for external data, because we always prefer to put all sensitive information in repository objects, and, withal, we actively use registered tables to run queries against views based on documentum structures.

msroth

Both the Content Server Admin guide and the Content Server Fundamentals guide have info regarding registered tables (not a lot though). Look around on EDN, you'll find more.

pettitk

Example… For oracle… just adapt for SQL Server, if needed.

In a SQLPlus window:

CREATE TABLE mytable

( column1 VARCHAR2(64 BYTE),

column2 VARCHAR2(64 BYTE)

) ;

Insert into mytable (column1,column2) values ('test1’,’test2’);

In DQL:

update dm_registered objects set owner_table_permit=15, set group_table_permit=3, set world_table_permit=1 where Lower(table_name) = 'mytable';

select * from dm_dbo.mytable;

Note, regardless of how many columns, etc exist in your table, you don’t need to call them out in your register statement. You just need 1 entry (undocumented feature). The pt is to hookup the table w a registered objects. You will still be able to select on all the columns just fine. I just leave it how I have it, to make it easy.

You may want to play with the table permits, according to your need.

Good luck.