Category: DQL

In Documentum, data is stored in various object types, with dm_document being one of the most frequently used. To effectively interact with this object type, Documentum provides different views, each serving a specific purpose. These views are designed to handle both single-valued (non-repeating) and repeating attributes, and they are accessed by different components of the…

Efficient data retrieval is critical in content management systems like Documentum, where large volumes of data are managed. One way to optimize query performance is by indexing key attributes. However, creating indexes on Documentum base tables requires careful consideration and proper methods. It is strongly recommended that all indexes be created within Documentum itself, not…

NOTE :This approach is useful only when dm_DMClean and dm_DMFilescan jobs are not run on the repository after the document is deleted. 1.       Query the dmr_content table to find the details of the deleted file SYNTAX : select r_object_id from dmr_content where full_format='<deleted document format>’ and set_file like ‘<Deleted document name>’  Example :  select r_object_id from dmr_content where…

select t.name,r.event,r.user_namefrom dmi_registry r, dm_type twhere r.is_audittrail = 1and t.r_object_id = r.registered_id select r.registered_id, r.event,r.user_namefrom dmi_registry rwhere r.is_audittrail = 1 How to get the deleted documents list in a cabinet using DQL in Documentum? select r_object_id from dm_cabinet where object_name = ‘Reports’0c0271838587137a SELECT * FROM dm_audittrail d, dm_audittrail lWHERE d.event_name = ‘dm_destroy’AND l.event_name = ‘dm_link’AND…

find all the workorders currently in progress: SELECT r_object_id, object_name, completion_status, mw.object_name, w.master_workorder_idFROM dmc_rps_work_order w, dmc_rps_master_work_order mwwhere completion_status = ‘PROCESSING’and mw.r_object_id = w.master_workorder_id SELECT r_object_id, object_name, completion_statusFROM dmc_rps_master_work_order mwwhere completion_status = ‘PROCESSING’ The following work order (6523) is in progress: dump: select distinct operation_name from dmc_rps_master_work_order select distinct operation_name, count(r_object_id)from dmc_rps_master_work_ordergroup by operation_name RETAINER_PROMOTION ……………………………..829RETAINER_QUALIFICATION…

Query (DQL) to find tables created recently: select * from dm_dbo.dm_sysobjects where “type” = ‘U’ order by crdate desc

Upgrading the compatibility level of your SQL Server 2016 database from 2008 (compatibility level 100) to 2016 (compatibility level 130) can provide significant benefits, including better performance and access to modern features. However, before deciding, it’s important to carefully weigh the pros and cons. Reasons to Upgrade Compatibility Level Potential Risks and Considerations Recommended Approach…

Yes, in MS SQL Server, you can run index rebuilds in parallel by using multiple CPU cores, but this is managed internally by SQL Server and depends on a few factors, such as the version of SQL Server, the edition (Enterprise vs. Standard), and system resources like CPU and memory. To explicitly run index rebuilds…

In this article, we will learn how to identify and resolve Index Fragmentation in SQL Server. Index fragmentation identification and index maintenance are important parts of the database maintenance task. Microsoft SQL Server keeps updating the index statistics with the Insert, Update or Delete activity over the table. The index fragmentation is the index performance…