Archiving changeSets

[Guest]

Is there any advice or recommended approach to archive liquibase changeSets.

Our problem is that a liquibase update is beginning to take a significant time even when the database is (almost) up-to-date.

Currently we have a tree of files and just run an update on the top-level one which includes all the rest. Obviously we can run against just a sub-tree of the latest changes (assuming most of our databases are more-or-less up-to-date) but there’s a chance to miss an update this way.

Is there another approach? Maybe backup the DB and start a brand new changelog?

Are there any configurations within the tool to handle archiving?

Tony.