FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

Moving trial database to live FB install?

I will be setting up my live FB on an internal win2003 server (SQL Server is on another system, not the 2003 box).

When I get the trial db:

a) Do I just attach or restore it into the prod SQL server?

b) Will it include file attachments and all that jazz?

Thanks!
Woofster Send private email
Wednesday, March 30, 2005
 
 
We have a lovely guide with lots of screenshots that walks you through this:

http://www.fogcreek.com/FogBugz/KB/dbsetup/ImportingSQL2000.html

Let me know if you have any questions about this. Yes, you'll attach the MDF file, and it will have your attachments.
Dmitri Kalmar Send private email
Wednesday, March 30, 2005
 
 
OK, that document is perfect EXCEPT:

a) It indicates that I will need to define full text indexing on the BugEvent table. However this was already there after attaching the db.

b) It indicates there should be a job scheduled to build/maintain the index, but there is not.


What is the next step?

Thanks!
Woofster Send private email
Wednesday, March 30, 2005
 
 
You're absolutely right. That doc is out of date, it refers to the way things were in 3.0.

I've walked through the whole process myself, updating the language in that doc and putting in all new screenshots.

Take a look at the last step - well, step 6 - that's the new way to handle FTS.
Dmitri Kalmar Send private email
Thursday, March 31, 2005
 
 
So, you're too kind, it was far from perfect but now it should be! :)
Dmitri Kalmar Send private email
Thursday, March 31, 2005
 
 
OK....

But Step 6 is not applicable.... the only option I have under Full Text Indexing on that table is 'Define Full Text Indexing...'

So next step is ?

Thanks!
Woofster Send private email
Thursday, March 31, 2005
 
 
Oh right - my SQL Server still had FTS set up from a previous database named fogbugz.

Here's lots of pretty new screenshots:

http://www.fogcreek.com/FogBugz/KB/dbsetup/ImportingSQL2000.html
Dmitri Kalmar Send private email
Friday, April 1, 2005
 
 
Ahhhhhhhhhhh

Much better. Thank you! I can now get all the way through the wizard.

The docs you posted say to index the 'bugevent' table.

When I do a full text search in FB now, I get this error:

 >>>>>>>>>
Cannot use a CONTAINS or FREETEXT predicate on table 'Bug' because it is not full-text indexed.

No cases were found that matched.
 <<<<<<<<<

This means ?
Woofster Send private email
Friday, April 1, 2005
 
 
I'm wondering, did you previously run FogBugz Setup 4.0 and tell it to use SQL Server? Or did you not run setup and instead set things up manually? Or did you run setup and tell it to use Access?
Dmitri Kalmar Send private email
Friday, April 1, 2005
 
 
Please see the docs again, I've added steps for setting up FTS on the Bug table as well.

http://www.fogcreek.com/FogBugz/KB/dbsetup/ImportingSQL2000.html
Dmitri Kalmar Send private email
Friday, April 1, 2005
 
 
(Just see the very bottom of the doc, that's all that I added)
Dmitri Kalmar Send private email
Friday, April 1, 2005
 
 
That took care of it, thank you.

>> did you previously run FogBugz Setup
>> 4.0 and tell it to use SQL Server?

I did this:

1) Installed FB4, new install, SQL Server
2) Installed db I downloaded from the live trial site
3) In IIS Admin, created new site (to change the port), got into trouble
4) You advised me to run the installer again and choose Update
5) I did this, it fixed '3' and appeared not to touch the db.

I am not sure at what point the full text indexing was missing. It could have been already at '2'
Woofster Send private email
Friday, April 1, 2005
 
 
Okay, thanks for the details.
Dmitri Kalmar Send private email
Monday, April 4, 2005
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.