Trim duplicate finder data from the database

Hi

We are finally trying to migrate our server from the internal database to MySQL (before we consider upgrading from 6.5.4 to 7.0), but there is so much data (millions of rows) in the duplicate finder table that it is proving unweildy to convert. Is it possible to throw away that data before starting the migration?

Thanks,
Graeme.

6 comments
Comment actions Permalink

Hello,

you can truncate duplicates-related tables if you agree to lose the duplicates history.

There are 6 tables that hold duplicates data:

project_files

fragments

duplicate_results

duplicate_fragments

duplicate_diff

duplicate_stats

If you've truncated all of them when the TeamCity server was shut down, TeamCity should survive it OK.

0
Comment actions Permalink

Excellent, thankyou, we will give that a try.

0
Comment actions Permalink

Could you tell me the best tools to use to do this?
I've tried the hsql databasemanager - but it only shows properties, no tables.
Thanks
Andy

0
Comment actions Permalink

I'm using DbVisualizer. You can download a trial version of it: http://www.dbvis.com/products/dbvis/download

As of the HSQL database manager - if you attempted to open an internal database of TeamCity by the database manager from HSQL 2.x, the database may be corrupted. Please ensure that the database is not corrupted. And, don't forget to backup database files (just make copies of them).

0
Comment actions Permalink

Hi

We have successfully migrated to MySQL now, but we couldn't use the method you suggested. We had to provide a username and password to open the HSQL database so we used "SA" with no password, and we were unable to see any of the tables so couldn't trim them.

Instead we looked at a database backup we already had and found that there is a CSV file for each table, so we deleted the rows from the relevant files and imported that database into a fresh MySQL database and reconfigured TeamCity to connect to it. So far it seems to have worked!

Thanks for your help!
Graeme

0

Please sign in to leave a comment.