Will IBM TRIRIGA support or recommend partitioning a table in multiple files for better & more stable performance?

Answer

There is no recommendation from IBM TRIRIGA support for database partitioning (multiple database files). This is up to the DBA to implement such technology changes, and to react and respond to any new problems introduced by partitioning. IBM TRIRIGA Support would not be able to assist with new problems that are introduced with these changes, and it would fall upon the DBA and the database vendor support to resolve any issues from database operation end.

The DM_Content (Document manager content table) keeps the attached files, including blob content (Binary Large Object). CAD drawing are stored in this table also. This is pure binary data there, so compression is not effective.

IBM TRIRIGA does not have any official document about handling that specific table, typically if you perform maintenance into system deleting old & not necessary records, the respective associated DM_Content records will be deleted as part of the Cleanup agent run. It is up to DBA to check if de-fragmentation (database maintenance) needs to occur on that table for releasing space (cost x benefit assessment).

From database perspective, partitioning the table into different database files and in different disks with separate IO channels, may contribute for better response since this will balance the IO operations in that table and find the required data with more efficiency. If there is a single DM_CONTENT table/BO database file, this will concentrate all IO operations against that disk,, and you may see bottlenecks on the IO processor runs, and this may cause IO time-out events due to database slow response. So in theory, having multiple database files (partitions), making sure they are in different disks and with different IO channels (and processors), may present a better IO performance, balancing the read/write operations performed concomitantly. But see, this is actually a DBA decision regarding this database tuning and technology, and thus not really under IBM TRIRIGA support scope.