Skip to content

Document Management has been storing documents directly in the Oracle database, and that's now driving significant database growth — backups and development-environment refreshes from production are both taking noticeably longer as a result. Is it worth moving the Document Management repository out of Oracle, and what should you expect if you do?

Answer

Moving to an FTP-based document repository (rather than continuing to store documents inside the Oracle database, or using a UNC-path repository) is a well-established, low-risk option — it's generally been found more robust than UNC, and it has the added benefit of letting you segregate document classes/servers behind separate firewalls if needed for compliance reasons, including restricting even IFS's own access at the network level. No functional difference has been reported within IFS itself after making this change — performance and access both work the same from the user's perspective whether documents are stored in Oracle or on FTP. One practical thing to plan for: the batch transfer process needs adequate disk space on the middleware server itself, since files are staged there temporarily before being moved to their final FTP destination. As a general principle, storing documents outside the Oracle database is the commonly recommended approach once document volume starts meaningfully driving up database size and backup/restore times.

← Browse Document management questions