best practices for rebuilding full text search

Hi
We are working with a sql server 2000 using full text search, which works
well so far. However, we are not sure which is the best way to ensure the
full text search is always working properly. As changes to the database
should be immediatly reflected in a search query, we have change tracking
enabled. But should we now rebuild the fulltext catalogue from time to time.
We are thinking about creating a job that runs every two months that
completly rebuilds the full text index.( exec sp_fulltext_catalog
N'OurFullTextCataloge', N'start_full' )
Would you suggest to do this or is having change-tracking enabled enough?
Thanks for any answer.
Greetings
Daniel
Having change tracking should be enough.
There should be no reason for you to rebuild other than adding or removing a
noise word list.
"Daniel Knpfel" <d.kn@.iph.ch> wrote in message
news:eXcSOhLjHHA.4772@.TK2MSFTNGP05.phx.gbl...
> Hi
> We are working with a sql server 2000 using full text search, which works
> well so far. However, we are not sure which is the best way to ensure the
> full text search is always working properly. As changes to the database
> should be immediatly reflected in a search query, we have change tracking
> enabled. But should we now rebuild the fulltext catalogue from time to
> time. We are thinking about creating a job that runs every two months that
> completly rebuilds the full text index.( exec sp_fulltext_catalog
> N'OurFullTextCataloge', N'start_full' )
> Would you suggest to do this or is having change-tracking enabled enough?
> Thanks for any answer.
> Greetings
> Daniel
>
>
sql

beginner - case sensitive query

Hi

We are taking case sensitive data, and loading it into an Access 2000 database using an OBDC. We then use VB 6 to produce an SQL .exe file which manipulates the data into new tables for the CR.

We have a a select statement where we have
SELECT ....
INTO A_POS
FROM POS LEFT JOIN CHTAB ON POS.STATUS = CHTAB.STATUS

The trouble is the client has the codes "F" and "f" in the CHTAB.STATUS, so I am producing duplicate A_POS records for any POS record with a status of "F".

Any suggestions as to how I can check the case sensitivity in Access so I create clean tables?

Thanks.
_Do you want to make all "f" to "F"?
Post some sample data and the result you want|||Unfortuneately, we are a software house, so we can't go and demand our clients change the codes. One client had all their company structure codes in upper case, and when they changed the company structure, they kept all the same codes, but changed them to lower case. Thus on the database "MELB" and "melb" could appear in one historic view, and have totally different properties.
I have an Organisation chart file ORG, which is keyed by the field OFFICE. I also have an employee positions file, POS. One of its attributes is OFFICE. Both "MELB" and "melb" are valid, but distinct, office codes.
My select statment is:-

select ... from POS LEFT JOIN ORG WHERE POS.OFFICE = ORG.OFFICE

And I need to somehow tell the script that I want the matching to be case sensitive, so I only pick up the correct upper (or lower) case office, not both.

Thanks