Question

Are there any special instructions to migrate a FogBugz database from SQL Server 2000 to 2008. Any pitfalls to watch for?

What we thought we would do is create the 2008 instance on the same box as 2000 (this is a Server 2003 machine). Detach the database in 2000 and move it to the 2008 instance. Someone mentioned problems with the 2000 compatibility mode for databases in general though. Should we create a new database in SQL Server 2008 and import the data?

Once the data is moved, what do we have to do for FogBugz to find the new database server and database?

Looking for recommendations to make this transition go as smooth as possible.

Rick Schummer

Answer 1

Don't import the data. It will just work. (I have done this myself.)

The steps typically are (this is for moving SQL DB from SQL Server A to B, applies whether or not the SQL version is changing).

1. Shut down the FogBugz Maintenance Service on.

2. Shut down the old SQL Server service on A. If this cannot be done, set the FB DB on server A to READ ONLY and rename the FB DB, so nothing attaches to it accidentally.

3. Attach the db on SQL B

4. Check if any userid's or SID's in the DB need to be remapped. You may need to reset the dbowner or other user ids. See this kb: http://support.microsoft.com/kb/224071

5. Confirm that you can now log into to SQL B using SQL Management Studio (it is best to authenticate the same way FB will).

6. If you can auth OK, now set the connection string on the FB system to point to B. This is done on the FB web server. You can do this in the registry, in a location similar to this:

   HKEY_LOCAL_MACHINE\SOFTWARE\Fog Creek Software\FogBugz\C:/Program Files/FogBugz/website

   Note the sConnectionString element. That is the connection string.

7. Start the FogBugz Maintenance Service

8. Voila! FB is now running on the new DB server.