Using FogBugz On Demand? We've recently rolled out a new sidebar as part of taking FogBugz forward. Please see this article for details on what's new, what's changed, and where you can find all your favorite things.

Intro

Typically, these steps are used as preparation for a migration to On Demand from FogBugz For Your Server (a.k.a. self-hosting FogBugz). However, you may run these at any time.

Check for Rogue Cases

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 step is recommended to be performed by your database administrator.

Microsoft SQL Server

  1. Go to Microsoft SQL Server Management Studio
  2. Connect to your FogBugz database
  3. Run this transact-sql:
    1. DBCC CHECKDB ('YOUR_FOGBUGZ_DB_NAME') WITH NO_INFOMSGS;
    2. NOTE: replace YOUR_FOGBUGZ_DB_NAME with the name of your FogBugz database. Typically this is ‘fogbugz’ but can sometimes be ‘fogbugz1’ or ‘fogbugz2’, or something else if you’ve personally renamed the default database.
    3. You can read more about the DBCC CHECK_DB command here
  4. If the output shows errors, you’ll need run a database repair which may result in some degree of data loss. Most database administrators will run a command like so:
    1. DBCC CHECKDB ('YOUR_FOGBUGZ_DB_NAME') REPAIR_REBUILD WITH NO_INFOMSGS;
    2. NOTE: Of course, before making a database changes, please ensure you have a backup of your database. And make sure to replace YOUR_FOGBUGZ_DB_NAME with the name of your FogBugz database.
    3. Re-run the command from step #3 and please send the results to us

MySQL server

Run a mysqlcheck on the your FogBugz database. If it suggests you to repair the database, you will likely have to do so. Of course, before making a database changes, please ensure you have a backup of your database.

Check the Encoding and Collation Settings

Microsoft SQL Server

  1. Go to Microsoft SQL Server Management Studio
  2. Connect to your FogBugz database
  3. Right-click on your FogBugz database
  4. Choose Properties
  5. Click the General page on left
  6. Note the property Collation under Maintenance
  7. You should see the value SQL_Latin1_General_CP1_CI_AS
  8. 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)

Microsoft SQL Server 2005

Microsoft SQL Server 2008

Microsoft SQL Server 2008 R2