Search the Community
Showing results for tags 'database'.
Found 1 result
Hello. We are using Plastic SCM Cloud with Unity for 1,5 years now and database size is growing up by time, although our Repository size doesn't increase at all. This happens because the database (and cloud storage) keeps multiple versions of all assets. For example we have 50+ versions of our scene assets and they are really big. And we almost never need the older versions of scenes. We no longer need the histories of most assets from 1 year ago. We currently have 600 changesets but the changesets 1 to 400 aren't required anymore. As I know there was a trim command to delete old changesets from the database, but I couldn't find any info about this in the documentation. In example, to delete all changesets from 1 to 400 and database would look like it started in changeset 401, keeping all changesets to 600. And I guess we can backup and locally keep the original database from our disk. And if we ever need a file from those early changesets, we can access it with plastic using those backups. (From this directory: C:\Program Files\PlasticSCM5\server\jet) Am I correct with these? And if there is such an operation available, whats it called? Are there some best practices on what to do with such scene files that are changed often, but old versions aren't important? What should we do to avoid them growing the database size so fast? Thank you,