We have three very large nonprod repositories (over 3TB). Dev and Test, especially, do not need to be as large as they are. I understand shrinking the size is difficult because of referenced objects, released objects, etc. Looking at it from a different angle, I'm wondering if we can somehow export the structure and metadata but without the data and then import publications and objects to build a new small database.
I'm interested in this subject for production environments, too. Maintaining the repository for active content and having a method for removing inactive content has been a longstanding need for us, especially since Tridion Docs is not our legal repository for records retention. Keeping it lean has a lot of benefits, but historically, I don't think it's an area that has been taken up from a support or strategy standpoint.
I'm interested in this subject for production environments, too. Maintaining the repository for active content and having a method for removing inactive content has been a longstanding need for us, especially since Tridion Docs is not our legal repository for records retention. Keeping it lean has a lot of benefits, but historically, I don't think it's an area that has been taken up from a support or strategy standpoint.
Translate
