sgvault db size

[scaiferw]

Good Afternoon;

Our DB Operations team is asking about the size of the sgvault database. Our repository consists primarily of binaries and documentation more than source code.

Is there any way to compress this, and if so can it be done without losing our history/rollback cabability?

Repository Information:
Revisions: 33978
Folders: 10245 (+6445 deleted)
Files: 53760 (+35079 deleted)
Tree Size: 193.6 GB
Disk Space Needed: 387.21 GB
Database Size: 269.06 GB

Thanks,

Rob

[Beth]

Some options you have are to either use obliterate to remove things not needed any more (warning: could break Export/Import), or you could separate the data out into multiple servers using our Folder Export Import tool.

[scaiferw]

Reading the Repository Information it would appear that there is a high proportion of deleted material - I assume it's still in the db occupying space.

1) Is there a way to mass expunge that deleted material?

2) Are there implications beyond losing the history, which I assume would be the most obvious consequence?

Thanks,

Rob

[Beth]

Yes, deleted items remain.

1) Obliterate removes deleted items.

2) Obliterate makes Vault Folder Export Import not work due to missing history.

If you're thinking of separating out pieces of the database, I'd suggest doing that first, and then you can obliterate. If you will never use the Export/Import, then feel free to use Obliterate. The one thing with Obliterate and branches is that you can only obliterate the source of the branches last. You can't branch, and then delete the origin of the branch, because it holds the history.