show/hide this revision's text 6 note about lowercase table names

NB: Before you go through any of this, you should make sure there are no FogBugz-unfriendly settings in your MySQL instance and that there's adequate disk space (3x the dump file size) on the MySQL machine.

This guide is intended for people who want to move a MySQL FogBugz database over to a new MySQL installation.

If you are upgrading from a previous version of FogBugz at the same time as moving your database, please install the upgraded FogBugz code against the old database if this is applicable or feasible, log in once so FogBugz can do the upgrade, and then proceed to moving your database.

  1. Make sure that you're running the latest version of FogBugz before starting. You must be running at least FogBugz version 3.0.15.
  2. On the old MySQL server, run the following at the command-line:

    mysqldump fogbugz > createfb.sql

    (This assumes your database name is "fogbugz")
  3. Put the new file creatfb.sql somewhere accessible from the new server
  4. Install FogBugz on the new server and let it create a new MySQL database. Make sure it's working (even add a test case). If you're using the same FogBugz server and only moving the database, just get the new MySQL instance up and running.  Remember the FogBugz user and password that you set for the database.
  5. Once it's working, log into mysql on the new server as root.  The instructions assume your FogBugz database is called 'fogbugz'.  If not, replace 'fogbugz' here with the name of your database.

    mysql> drop database fogbugz;
    mysql> create database fogbugz;
    mysql> use fogbugz;
    mysql> source /path/to/createfb.sql
    mysql> grant all on fogbugz.* to fogbugzuser identified by 'fogbugzpassword';
    mysql> grant all on fogbugz.* to fogbugzuser@'localhost' identified by 'fogbugzpassword';

    Note the ' around the 'localhost' part.  You can replace localhost by the server name if your FogBugz server is on a different machine. All values in italics should be replaced with valid values for your environment.
  6. Then go back into FogBugz through your web browser. If you moved FogBugz, you will have to enter your order info to install licenses again.

If you changed platforms (switched between Windows and Unix/Linux), you will need to clear the passwords for your users and have them set them again. The hashing algorithm is different for the two platforms. You can do this with the following sql query:

UPDATE Person SET sPassword = ''

A platform may also require that you enable the "lowercase_table_names" setting in your my.ini or my.cnf file.

show/hide this revision's text 5 clarity on installing new instance

NB: Before you go through any of this, you should make sure there are no FogBugz-unfriendly settings in your MySQL instance and that there's adequate disk space (3x the dump file size) on the MySQL machine.

This guide is intended for people who want to move a MySQL FogBugz database over to a new MySQL installation.

If you are upgrading from a previous version of FogBugz at the same time as moving your database, please install the upgraded FogBugz code against the old database if this is applicable or feasible, log in once so FogBugz can do the upgrade, and then proceed to moving your database.

  1. Make sure that you're running the latest version of FogBugz before starting. You must be running at least FogBugz version 3.0.15.
  2. On the old MySQL server, run the following at the command-line:

    mysqldump fogbugz > createfb.sql

    (This assumes your database name is "fogbugz")
  3. Put the new file creatfb.sql somewhere accessible from the new server
  4. Get
  5. Install FogBugz and MySQL working on the new server and let it create a new MySQL database. Make sure it's working (even add a test case). If you're using the same FogBugz server and only moving the database, just get the new MySQL instance up and running.  Remember the FogBugz user and password that you set for the database.
  6. Once it's working, log into mysql on the new server as root.  The instructions assume your FogBugz database is called 'fogbugz'.  If not, replace 'fogbugz' here with the name of your database.

    mysql> drop database fogbugz;
    mysql> create database fogbugz;
    mysql> use fogbugz;
    mysql> source /path/to/createfb.sql
    mysql> grant all on fogbugz.* to fogbugzuser identified by 'fogbugzpassword';
    mysql> grant all on fogbugz.* to fogbugzuser@'localhost' identified by 'fogbugzpassword';

    Note the ' around the 'localhost' part.  You can replace localhost by the server name if your FogBugz server is on a different machine. All values in italics should be replaced with valid values for your environment.
  7. Then go back into FogBugz through your web browser. If you moved FogBugz, you will have to enter your order info to install licenses again.

If you changed platforms (switched between Windows and Unix/Linux), you will need to clear the passwords for your users and have them set them again. The hashing algorithm is different for the two platforms. You can do this with the following sql query:

UPDATE Person SET sPassword = ''
show/hide this revision's text 4 added 87 characters in body

NB: Before you go through any of this, you might should make sure there are no FogBugz-unfriendly settings in your MySQL instance and that there's adequate disk space (3x the dump file size) on the MySQL machine.

This guide is intended for people who want to move a MySQL FogBugz database over to a new MySQL installation.

If you are upgrading from a previous version of FogBugz at the same time as moving your database, please install the upgraded FogBugz code against the old database if this is applicable or feasible, log in once so FogBugz can do the upgrade, and then proceed to moving your database.

  1. Make sure that you're running the latest version of FogBugz before starting. You must be running at least FogBugz version 3.0.15.
  2. On the old MySQL server, run the following at the command-line:

    mysqldump fogbugz > createfb.sql

    (This assumes your database name is "fogbugz")
  3. Put the new file creatfb.sql somewhere accessible from the new server
  4. Get FogBugz and MySQL working on the new server (even add a test case). If you're using the same FogBugz server and only moving the database, just get the new MySQL instance up and running.  Remember the FogBugz user and password that you set for the database.
  5. Once it's working, log into mysql on the new server as root.  The instructions assume your FogBugz database is called 'fogbugz'.  If not, replace 'fogbugz' here with the name of your database.

    mysql> drop database fogbugz;
    mysql> create database fogbugz;
    mysql> use fogbugz;
    mysql> source /path/to/createfb.sql
    mysql> grant all on fogbugz.* to fogbugzuser identified by 'fogbugzpassword';
    mysql> grant all on fogbugz.* to fogbugzuser@'localhost' identified by 'fogbugzpassword';

    Note the ' around the 'localhost' part.  You can replace localhost by the server name if your FogBugz server is on a different machine. All values in italics should be replaced with valid values for your environment.
  6. Then go back into FogBugz through your web browser. If you moved FogBugz, you will have to enter your order info to install licenses again.

If you changed platforms (switched between Windows and Unix/Linux), you will need to clear the passwords for your users and have them set them again. The hashing algorithm is different for the two platforms. You can do this with the following sql query:

UPDATE Person SET sPassword = ''
show/hide this revision's text 3 clear passwords when changing platforms
show/hide this revision's text 2 added 257 characters in body
show/hide this revision's text 1