Re: Full-Text options disabled in management console

Well, I'm already a memeber of the local admin group and sql sysadmins
....but I tried using the SA login and had same issue.

Brad

"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:OrTBjJwNGHA.2828@xxxxxxxxxxxxxxxxxxxxxxx
I've run into this myself. Close down Enterprise Manager and reopen it and
this time connect using SA or a member of the Local Administrator group
which is also in the sysadmin role. I normally just use the command line
full-text indexing wizard or use the procs.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"Brad" <lane@xxxxxxxxxxxxxxxx> wrote in message
news:eBOm219MGHA.984@xxxxxxxxxxxxxxxxxxxxxxx
If I open a SQL 2000 database using the management console the Full-Text
options are grayed-out / disabled...even though Full-Text search service
is
started and I can create full-text catalogs using stored procedures in QA
and search using those catalog in QA. This problem occurs on my local
copy
of SQL 2000 (developer edition) and on server editions installed on
servers.
I am a sysadmin in all cases and I am an admin on the computers .

More information:
If I open enterprise manager console and navigate to a MS SQL 2000
database,
right click on the database "New Full-Text Catalog is grayed out/disabled.
If I navigate to a table in the database and right click on the table
"Full-Text Index Table" is grayed out/disabled....even though I can create
a
catalog on the same table using QA and search on that table using the
catalog.
If I right click on a full text catalog object the following menu options
are disabled/grayed out: New Full-Text Catalog, Rebuild Catalog, Stop
Population (at least this one makes sense) and Schedules.

I can run the full-text indexing wizard and create the index from the
command line.

My local pc is Win2003 server sp1 with SQL Server 2000 sp4
Server is Win2000 with SQL Server 2000 sp4

Any suggestions, hints or references to articles, kb or other would be
appreciated.

Brad







.

Relevant Pages

  • Re: Performance problems -- need guidance on scaling
    ... Thanks for the update on the FT Catalog corruption, ... will use, up to a max of 512Mb, if this memory is available. ... a server with 512 MB of RAM and a resource_usage value of 5 ... the data, you could, detach your SQL 2000 mdf & ldf files ...
    (microsoft.public.sqlserver.fulltext)
  • Re: freetexttable query never completes nor times out?
    ... Full text does not perform with a nested loop because the search is done for each iteration, if your server doesn't have much memory you will have a huge IO issue. ... When I get properties for the FT catalog, ... The company I am currently working for is a heavy consumer of SQL FTS ... dB (this time from the actual ASP page that passes the query to the ...
    (microsoft.public.sqlserver.fulltext)
  • Re: freetexttable query never completes nor times out?
    ... Full text does not perform with a nested loop because the search is done for each iteration, if your server doesn't have much memory you will have a huge IO issue. ... When I get properties for the FT catalog, ... The company I am currently working for is a heavy consumer of SQL FTS ... dB (this time from the actual ASP page that passes the query to the ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Performance problems -- need guidance on scaling
    ... So we're now CPU ... I have read that putting the catalog and SQL table on separate RAID ... Our current server will support only a single CPU. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: SqlServer 2000, MSSearch and Fulltext search problems
    ... The MSSearch service is a windows-specific utility and due ... SQL Server, ... the FT Catalog corruption can be workaround ...
    (microsoft.public.sqlserver.fulltext)