show/hide this revision's text 5 Replaced migration notes with instructions to contact support.

Back Up!

Back up your database before the move. Keep the backup of your original DB after the move in case you discover problems later, in particular missing Attachments.

Mind the Versions!

It's very important that you move your data between databases that were created by the same version of FogBugz. e.g.

Contact Fog Creek Support

If you are using an older version of FogBugz, upgrade it to the latest version before the move. If you can't do that, make sure to install the same version for the destination considering migrating your database .

Try ESF Database Migration Toolkit. It can migrate data from MS SQL Server to MySQLor back in 3 steps.

http://www.easyfrom.net/download/

From , please contact Fog Creek : Once you have the database converted, you should migrate the data itself into a FogBugz-generated schemasupport at customer-service@fogcreek.com. This The migration process can be accomplished by using an empty FogBugz database. Then, you quite fragile and our support team can use this script to generate a file that will contain the correct SQL to select all the data out of each table into the empty schema.

Note that plugin table names have the ixPlugin value in them, which is determined by the order they were installed in FogBugz. You may have provide detailed guidance specific to manually change the table names so that the fresh destination database matches the source databaseyour needs.

SET @old_database = 'fogbugz_converted';SET @new_database = 'fogbugz_final';SELECT CONCAT(  "SELECT '",TABLE_NAME, "'; ",  " TRUNCATE ",@new_database,".", TABLE_NAME,"; ",  " INSERT INTO ", @new_database,".",TABLE_NAME,"(", GROUP_CONCAT(COLUMN_NAME ORDER BY ORDINAL_POSITION), ") ",  " SELECT ", GROUP_CONCAT(COLUMN_NAME ORDER BY ORDINAL_POSITION), " FROM ",@old_database,".", TABLE_NAME,"; ",  " SHOW WARNINGS;") AS Statement FROM INFORMATION_SCHEMA.COLUMNS     WHERE TABLE_SCHEMA = @new_database       AND TABLE_NAME NOT IN ('dbcopier','dbupdate','dbsession','dbsessiondata','version','fblock','fragmentcache','fragmentdependency','id','indexdelta','indexfile','indexfilepage','trainingrequest')       AND COLUMN_NAME NOT LIKE 'FILTER_%'     GROUP BY TABLE_NAME INTO OUTFILE 'c:\\dump.sql';
show/hide this revision's text 4 plugin table names

Back Up!

Back up your database before the move. Keep the backup of your original DB after the move in case you discover problems later, in particular missing Attachments.

Mind the Versions!

It's very important that you move your data between databases that were created by the same version of FogBugz. e.g. If you are using an older version of FogBugz, upgrade it to the latest version before the move. If you can't do that, make sure to install the same version for the destination database.

Try ESF Database Migration Toolkit. It can migrate data from SQL Server to MySQL or back in 3 steps.

http://www.easyfrom.net/download/

From Fog Creek: Once you have the database converted, you should migrate the data itself into a FogBugz-generated schema. This can be accomplished by using an empty FogBugz database. Then, you can use this script to generate a file that will contain the correct SQL to select all the data out of each table into the empty schema.

Note that plugin table names have the ixPlugin value in them, which is determined by the order they were installed in FogBugz. You may have to manually change the table names so that the fresh destination database matches the source database.

SET @old_database = 'fogbugz_converted';


SET @new_database = 'fogbugz_final';


SELECT CONCAT(
  "SELECT '",TABLE_NAME, "'; ",
  " TRUNCATE ",@new_database,".", TABLE_NAME,"; ",
  " INSERT INTO ", @new_database,".",TABLE_NAME,"(", GROUP_CONCAT(COLUMN_NAME ORDER BY ORDINAL_POSITION), ") ",
  " SELECT ", GROUP_CONCAT(COLUMN_NAME ORDER BY ORDINAL_POSITION), " FROM ",@old_database,".", TABLE_NAME,"; ",
  " SHOW WARNINGS;") AS Statement 
FROM INFORMATION_SCHEMA.COLUMNS 
    WHERE TABLE_SCHEMA = @new_database 
      AND TABLE_NAME NOT IN ('dbcopier','dbupdate','dbsession','dbsessiondata','version','fblock','fragmentcache','fragmentdependency','id','indexdelta','indexfile','indexfilepage','trainingrequest') 

      AND COLUMN_NAME NOT LIKE 'FILTER_%' 
    GROUP BY TABLE_NAME 
INTO OUTFILE 'c:\\dump.sql';


SOURCE c:\\dump.sql
show/hide this revision's text 3 don't lose your attachments, folks

Back Up!

Back up your database before the move. Keep the backup of your original DB after the move in case you discover problems later, in particular missing Attachments.

Mind the Versions!

It's very important that you move your data between databases that were created by the same version of FogBugz. e.g. If you are using an older version of FogBugz, upgrade it to the latest version before the move. If you can't do that, make sure to install the same version for the destination database.

Try ESF Database Migration Toolkit. It can migrate data from SQL Server to MySQL or back in 3 steps.

http://www.easyfrom.net/download/

From Fog Creek: Once you have the database converted, you should migrate the data itself into a FogBugz-generated schema. This can be accomplished by using an empty FogBugz database. Then, you can use this script to generate a file that will contain the correct SQL to select all the data out of each table into the empty schema.

SET @old_database = 'fogbugz_converted';


SET @new_database = 'fogbugz_final';


SELECT CONCAT(
  "SELECT '",TABLE_NAME, "'; ",
  " TRUNCATE ",@new_database,".", TABLE_NAME,"; ",
  " INSERT INTO ", @new_database,".",TABLE_NAME,"(", GROUP_CONCAT(COLUMN_NAME ORDER BY ORDINAL_POSITION), ") ",
  " SELECT ", GROUP_CONCAT(COLUMN_NAME ORDER BY ORDINAL_POSITION), " FROM ",@old_database,".", TABLE_NAME,"; ",
  " SHOW WARNINGS;") AS Statement 
FROM INFORMATION_SCHEMA.COLUMNS 
    WHERE TABLE_SCHEMA = @new_database 
      AND TABLE_NAME NOT IN ('dbcopier','dbupdate','dbsession','dbsessiondata','version','fblock','fragmentcache','fragmentdependency','id','indexdelta','indexfile','indexfilepage','trainingrequest') 

      AND COLUMN_NAME NOT LIKE 'FILTER_%' 
    GROUP BY TABLE_NAME 
INTO OUTFILE 'c:\\dump.sql';


SOURCE c:\\dump.sql
show/hide this revision's text 2 added 1367 characters in body
show/hide this revision's text 1