Overview

Despite our best efforts, data in On-Premise databases can become a bit glitchy at times due to issues in the customer environment, which can lead to data inconsistencies. Most of the time, System Administrators can "live with it" or are even unaware of those cases or do not find it a hassle. However, it is strongly recommended to run the necessary quality checks to make sure that the database is healthy, particularly before running a migration or upgrade on Fogbugz. Also, from a maintenance perspective, it is a good practice to keep the database in good shape, ensuring the optimum performance and reliability of the application.

Read on to learn more about checking data quality in your FogBugz database.

Procedure

The steps outlined in this article are typically used as preparation for a migration to On-Demand from FogBugz For Your Server (a.k.a. self-hosting FogBugz) or FogBugz On-Premise. However, you may run these at any time as part of your system maintenance.

It is recommended that any database updates are done by a database administrator. Please ensure you have a backup of your database before making any changes.

Check for Rogue Cases First

Follow our guide to check for and fix rogue cases. Please let us know when no rogue cases exist in your database.

Check the Logical and Physical Integrity of Your Fogbugz Database

This procedure is recommended to be performed by your database administrator.

Microsoft SQL Server

Go to Microsoft SQL Server Management Studio.
Connect to your FogBugz database.
Run the following transact-SQL:
```
DBCC CHECKDB ('YOUR_FOGBUGZ_DB_NAME') WITH NO_INFOMSGS;
```
Replace YOUR_FOGBUGZ_DB_NAME with the name of your FogBugz database. On FogBugz for Your Server (FBFYS), typically this is fogbugz but can sometimes be fogbugz1 or fogbugz2, or something else if you have renamed the default database. On newer FogBugz On-Premise versions, this is usually trial1 but can be trialN, depending on the setup.
- You can read more about the DBCC CHECK_DB command in the article DBCC CHECKDB (Transact-SQL).
If the output shows errors, you need to run a database repair, which may result in some degree of data loss. Most database administrators will run a command like the one below:
```
DBCC CHECKDB ('YOUR_FOGBUGZ_DB_NAME') REPAIR_REBUILD WITH NO_INFOMSGS;
```
Note: Make sure to replace YOUR_FOGBUGZ_DB_NAME with the name of your FogBugz database. Again, it is crucial to have a backup of your database before making any changes.
Re-run the command in Step 3.
Send the results to us.

MySQL server

Run a mysqlcheck on your FogBugz database. If it suggests repairing the database, you will likely have to do so. Before making any database changes, please ensure you have a backup of your database.

Check the Encoding and Collation Settings

Microsoft SQL Server

Go to Microsoft SQL Server Management Studio.
Connect to your FogBugz database.
Right-click on your FogBugz database.
Choose Properties.
Click the General page on the left.
Note the property Collation under Maintenance.
You should see the value SQL_Latin1_General_CP1_CI_AS.
Please let us know if your collation setting is different.

MySQL server

Check your settings against the settings in this MySQL settings article, and please let us know of any differences. If you are preparing for an import to FogBugz On-Demand, the results of these queries will determine if any extra steps are necessary.

Remove Full-Text Catalog (Full-Text Search)

Select the appropriate version of your database and follow the steps provided in the articles to remove the full-text catalog.