Something strange happens if I try and do the following:
If I use the containstable function, with top_n_rank, along with an
extra "and where" clause, then the top_n_rank does not seem to return
the correct number of rows.

When i query key words , i can get the docname,doctype
etc.
Can i get some texts near the searching words ? like the
result fo google !

Full-text indexing was manually set up to work on the development server.
Now, I need to write a SQL script to programmatically set up Full-text
indexing on the staging server and then on the production server.
The SQL script must be rerunnable. It should handle the scenario where

Given the query:
Select *
from A
left outer join B on A.bid=B.id

I have a Text field in my database that has data along with the HTML tags.
I dont want to search these HTML tags on my FUll text Search.
Example Data
< Font color='red'> Blah</Font>

I have set up an Active Directory, Certificate Services on Windows 2003
Server. I am running SQL 2000 Server. AD and Certificate Services were
installed correctly.
My goal is to be able to use SSL when connecting to SQL Server via Query

I have a table setup running full-text index in sql server 2000. After
finishing 12 hrs long of initial full population, I immediately turned on the
"change tracking, update index in background". The full text index population
restart all over again even though there is no data ...

I have a 1.5 million row table with a text field.  Can
anybody think of a way to remove any duplicate rows where the text field
contains the same data (and a
way which will not take days to run!)

I've been digging around trying to find out how to allow my FTS
implementation deal with punctuation and "special" characters in a way that
fits my needs, but can't find a definite answer. I'm leaning towards trying
to switch to the Neutral Word Breaker setting to see if it will ...

How difficult is it to implement the full text searching capability provided
by SQL server if it wasn't implemented to start with?  Currently I have an
application that allows searching based on user profile fields.  However
it's not taking advantage of the full text indexing.

I have full text search enabled on two large tables, the first one has 3
million records (FT index column length is around 512-1025 char), and the
other one has around 1.6 records (FT index column length is around 50-120
char)

I configure a table with FT index , but when i search the
table , nothing returned , why ?
Windows 2003 EE (Chinese Edition)
SQL Server 2k + SP3 (Chinese Edition)

When searching for this street using this parameter:
'L''Avenue De La Reine Elizabeth'
I get a result ( The record contains 'L''Avenue De La Reine Elizabeth The
Second',)

We're about to deploy a new application, based primarily on FTS.
Because it is an isolated use, I'd like to take advantage of the FTS
features in Yukon.  Is Yukon stable enough to go into a limited
production environment?  I understand that there is at least one more

I am eargerly awaiting my MSDN Universal, until then I am very
interested to know if Yukon will allow a View to be FT Indexed ? I am
working on a scenario right as we speak that may be worth pushing off
for the moment if SQL 2005 Will support these