This article helps users migrate their FogBugz database from one Microsoft SQL Server instance to another. This process is a common scenario when the hardware supporting the database is getting old, making it necessary to move the database to a newer/different system.
Whatever the source of your database, the easiest way to get it to the new location is to make an MS SQL database backup and then restore that backup to the new location.
- For FogBugz to access this new database, we must make sure that it has the appropriate permissions. At the server level, navigate to Security > Logins and look for the user that FogBugz will use to authenticate (this is usually the user that the IIS Application Pool is running as).
- If you see the user then right-click on it and choose Properties and skip the rest of this paragraph. If you don’t see the user then right-click on Logins, select New Login and define the user’s login name (assuming you are using SQL Auth, then it will be either HOST\username or DOMAIN\username).
- In the Properties window, go to User Mapping. Check the box to map the FogBugz user to the FogBugz database and then check the db_owner box for the role membership.
- If you move from SQL 2005 to SQL 2008, you will want to change the compatibility mode for the database so it runs natively as SQL 2008 if you have installed or will install Kiln.
- When you move your database, you need to tell FogBugz where it is by updating the
sConnectionStringkey in the Windows Registry:
HKEY_LOCAL_MACHINESOFTWARE\Fog Creek Software\FogBugz\[your FogBugz install directory]
If you are running FogBugz in 32-bit mode on a 64-bit machine:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fog Creek Software\FogBugz\[your FogBugz install directory]
sConnectionStringkey will have a value as shown below. You will need to change the
Initial Catalogto refer to your new database location:
Server=SQL_SERVER;Initial Catalog=fogbugz;Integrated Security=SSPI;MultipleActiveResultSets=true;