Auto-archive to secondary database instead of file storage?

General
1

We’re currently using Pega’s auto-archive feature with file storage as the destination, but it’s causing problems for our reporting once cases are archived, they’re no longer queryable through standard report definitions or BI tools.

Is it possible to configure auto-archive to write to a secondary, client-owned database (e.g., our enterprise data warehouse or a dedicated archive DB) instead of file storage? If so, what’s the recommended approach and are there any limitations compared to the file storage option?

2

I think you’ll find the information you want here? I don’t have much to share on pro’s or con’s as I have never used secondary external repository on my projects (just discussed and planned too)

3

As far as I know, the archived cases willl be stored in the File Storage (Amazon S3 bucket) by default. To store in client owned database, it requires custom implementation.