Share
Report
66Hi community,
I’m currently managing a Business Central SaaS environment that has reached 80% of its storage capacity. After performing a technical analysis, I identified that approximately 40% of our total storage consumption is being driven by the Tenant Media (2000000184) and Tenant Media Set (2000000185) tables.
I’m currently managing a Business Central SaaS environment that has reached 80% of its storage capacity. After performing a technical analysis, I identified that approximately 40% of our total storage consumption is being driven by the Tenant Media (2000000184) and Tenant Media Set (2000000185) tables.
We are looking for advice on the best way to handle this growth and clean up our storage safely. Specifically, I have a few questions:
- Handling Orphaned Records: Is there a standard, supported procedure or a recommended AL pattern to safely identify and remove "orphaned" records from Tenant Media that are no longer linked to any business record (e.g., deleted vendors, items, or documents)?
- Maintenance Tools: Besides standard Data Retention Policies, are there any native Codeunits or best practices you recommend for managing media cleanup without compromising data integrity?
- External Archiving: For high-volume environments, is it a common practice to offload attachments to external storage (like Azure Blob Storage) while keeping only a link in BC? If so, what are the recommended patterns for this architectural change?
I want to ensure we don't break any references or audit trails. Any insights, experiences, or cautionary tales regarding media management in BC SaaS would be greatly appreciated.
Thanks in advance for your help!
Categories:
I have the same question (0)
All responses (
Answers (
