October 24, 2002 at 9:57 am
I've been trying to enable Full Text Indexing on my SQL Server 2000 box with no results.
I am using a small sample table called apps to search against a column named [App Name]which is of type char and contains 50 records This is what I have done:
The MSSearch service is running.
I have a unique index on the table.
I ran the Full-Text Indexing wizard.
-Selected Index
-Selected column to search against
-Created a catalog
-Received message stating that full-text
indexing wizard had completed
successfully.
Right-clicked table in EM, selected "F-T index table" then selected "Start Full Population"
Ran the two following queries in QA:
Select * from apps where contains([app name], '"Lab*"')
Select * from apps where [App Name] like 'Lab%'
The 'contains' query completes successfully yielding no records. The 'Like' query returns four records.
When I check the properties for the Full Text Catalog is gives me the following:
Name: ASDF
Location: c:\Program Files\Microsoft SQL Server... (Correct path)
Physical Catalog: SQL0000700006
Status: Idle
Item Count: 0
Catalog Size: 1 Mb
Unique Key count: 1
Last population date: (about 10 minutes before checking the properties.)
I've different variations on the query and set up an example against northwind exactly like an MSDN article said to and yielded the same results. Query runs successfully but returns no results.
Any suggestions?
"I met Larry Niven at ConClave 27...AND I fixed his computer. How cool is that?"
(Memoirs of a geek)
October 25, 2002 at 9:29 am
What service account do you use to start SQL Server? Is login Builtin\Administrators in your SQL Server logins?
October 25, 2002 at 10:11 am
MSSEARCH - Local system account
MSSQLSERVER - <domain>\SQLServ
SQLSERVERAGENT - <domain>\SQLServ
"I met Larry Niven at ConClave 27...AND I fixed his computer. How cool is that?"
(Memoirs of a geek)
October 25, 2002 at 11:42 am
Run sp_grantlogin 'NT Authority\System' and sp_addsrvrolemember @loginame = [NT Authority\System], @rolename = 'sysadmin' and you should be ok.
October 25, 2002 at 12:23 pm
Woops, I see I didn't answer both of your questions. The Builtin\Administrators was not in the Logins.
Thanks! That did it.
"I met Larry Niven at ConClave 27...AND I fixed his computer. How cool is that?"
(Memoirs of a geek)
October 25, 2002 at 12:24 pm
Would it have also worked if I had changed the login account on the MSSearch service to <domain>\SQLServ?
"I met Larry Niven at ConClave 27...AND I fixed his computer. How cool is that?"
(Memoirs of a geek)
October 25, 2002 at 12:39 pm
You can't change the service account for Search Service. It must be run by local system account. That is why I asked you whether BUILTIN\Administrators is in your SQL Server logins. By default, it is in the logins. Somehow for security purpose, many DBAs remove it from the SQL Server logins. In order to make Search Service function properly, 'NT Authority\System' account must be granted to access SQL Server with 'sa' privilege.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply