A forum for technical support discussion related to Fogbugz.
I recently upgraded to FogBugz 4.0 after archiving some very old bugs from our 3.1.9 installation. Of course, as Murphy would have it, we have run into cases where we need to look at some of those old bugs.
Can I run the 3.1.9 installation on the now upgrdaded 4.0 machine without blowing away the new SQL Server database? I have a different database on that server containing the archived data.
Thanks in advance,
Why not just point your current installation at the old 319 database and let FB upgrade that for you? No need to rerun setup then...
Or even, run the 4.0 setup again for another install and point that new one at the 319 db. 4.0 can read a 319 db (it will upgrade it though).
Originally, I tried to just install 4.0 and have it upgrade my 3.x database. Unfortunately the setup timed out numerous times trying to upgrade the BugEvent table. It wasn't until I deleted about 7,000 cases (and their assocated 51,000 or so bug event rows) that it would upgrade. You may want to bump up your SQL timeout to about 60 seconds; it seemed to time out after about 5 or 10 seconds. If it wasn't for this, I'd still have all my bugs in one database.
Anyhow, if I understand your 2nd option correctly, I can just run setup again on the same server without interfering with my existing 4.0 installation on that server? I just want to make sure I understand completely before I do something wrong and screw up my existing installation.
Hmmm. I did another install of 4.0, and tried to point it at my original 3.x SQL Server database. It gave me the following error:
The database you specified could not be found.
I just realized that this won't work anyway, since the conversion fails.
I'm back to asking: How do I install 3.x on the same server? Just run a fresh install into a differnt prog files folder?
This topic is archived. No further replies will be accepted.Other recent topics