Database bloated due to storing VCS history

Hi all,

Our TeamCity database has outgrown the built-in one, and we're now getting performance warnings. We tried turning on various cleanup settings, but it didn't seem to make any dent in the total size.

However, when doing a command line backup, the output displayed the number of rows in every table, and it turned out that "vcs_history" and "vcs_changes" were an order of magnitude larger than any other.

Is there any way of cleaning up these tables? I'm unsure what they're used for, and my reasoning says they just contain information duplicated from our VCS database, so can't be crucial unless TeamCity just flat out requires a copy of the VCS data in order to work.

Thanks,

Alex