Full Text not working

I cannot get fulltext indexing to work, nor can I get any error messages to
indicate whats wrong. Here's what I did (for the pubs database)
1. From the top menu, select Tools, Full Text Indexing.
2. Click next on the opening screen.
3. On the "Select a Database" screen, choose pubs.
4. For the next screen, select "titles" as the table and click next.
5. Keep the default unique index; there is only one on the pubs table.
6. In the next screen, select Title and Notes as the fields to be indexed.
7. On the "Select a Catalog" screen, because this is the first Catalog on
the server, we are prompted for a name. In this example, "demo" is used as
the Catalog name.
8. Click next.
9. Click Finish.
10. From Enterprise Manager, expand Full-Text Catalogs
11. Right click and select "Start Full Population."
12. The catalog is now complete.
If I type sp_help_fulltext_catalogs everything looks ok.
If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
I get a 1 which means ok.
If I type
SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
I get 0 rows
Same if I enter
SELECT title, notes
FROM titles
--where notes like '%quick%'
WHERE CONTAINS (notes, ' quick ')
of course entering
SELECT title, notes
FROM titles
where notes like '%quick%'
gets me the record I want. Anyone have any ideas what I can check?
BTW I did this on another server and it works. The server is works is using
SQL Server developer edition. The server that doesn't work is my production
box using SQL Server standard edition
Thanks for the help.
Francis,
Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
the item listed...might compare with CONTAINS in SQL BOL...same SP?
HTH
Jerry
"Francis" <Francis@.discussions.microsoft.com> wrote in message
news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>I cannot get fulltext indexing to work, nor can I get any error messages to
> indicate whats wrong. Here's what I did (for the pubs database)
> 1. From the top menu, select Tools, Full Text Indexing.
> 2. Click next on the opening screen.
> 3. On the "Select a Database" screen, choose pubs.
> 4. For the next screen, select "titles" as the table and click next.
> 5. Keep the default unique index; there is only one on the pubs table.
> 6. In the next screen, select Title and Notes as the fields to be
> indexed.
> 7. On the "Select a Catalog" screen, because this is the first Catalog on
> the server, we are prompted for a name. In this example, "demo" is used as
> the Catalog name.
> 8. Click next.
> 9. Click Finish.
> 10. From Enterprise Manager, expand Full-Text Catalogs
> 11. Right click and select "Start Full Population."
> 12. The catalog is now complete.
> If I type sp_help_fulltext_catalogs everything looks ok.
> If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> I get a 1 which means ok.
> If I type
> SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> I get 0 rows
> Same if I enter
>
> SELECT title, notes
> FROM titles
> --where notes like '%quick%'
> WHERE CONTAINS (notes, ' quick ')
>
> of course entering
>
> SELECT title, notes
> FROM titles
> where notes like '%quick%'
>
> gets me the record I want. Anyone have any ideas what I can check?
>
> BTW I did this on another server and it works. The server is works is
> using
> SQL Server developer edition. The server that doesn't work is my
> production
> box using SQL Server standard edition
> Thanks for the help.
>
>
>
|||Thanks Jerry. I have tried various combinations like
SELECT title, notes
FROM titles
WHERE CONTAINS (notes, 'quick')
or using double quotes with spaces in front of and behind the work quick.
I have also set up other full text indexes on this and other tables and other
databases on this server and it doesn't seem to work.
"Jerry Spivey" wrote:

> Francis,
> Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> the item listed...might compare with CONTAINS in SQL BOL...same SP?
> HTH
> Jerry
> "Francis" <Francis@.discussions.microsoft.com> wrote in message
> news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>
>
|||Thanks for the help. I found the problem in KB317746;
I executed the workaround described:
EXEC sp_grantlogin [NT Authority\System]
EXEC sp_addsrvrolemember @.loginame = [NT Authority\System]
, @.rolename = 'sysadmin'
and all is well now.
"Francis" wrote:
[vbcol=seagreen]
> Thanks Jerry. I have tried various combinations like
> SELECT title, notes
> FROM titles
> WHERE CONTAINS (notes, 'quick')
> or using double quotes with spaces in front of and behind the work quick.
> I have also set up other full text indexes on this and other tables and other
> databases on this server and it doesn't seem to work.
>
> "Jerry Spivey" wrote: