Is my full-text index option in sqlserver2008 grayed out?

Is my full-text index option in sqlserver2008 grayed out?

Is this a separate installation?

+8
sql-server-2008 full-text-search
source share
7 answers

You can enable it by running sp_fulltext_database .

+13
source share

Make sure the full text search feature is installed. Run the following database query:

SELECT SERVERPROPERTY('IsFullTextInstalled') 

A result of "0" ("Zero") means that full-text search is not installed on the server.

The result "1" (one) means full-text search installed on SQL Server.

If it is not installed, you need to restart SQL Server setup and add the full-text search feature. Here is a good article that shows how to Test and set up full-text search

+7
source share

You need to run this sproc system to enable full-text indexing:

 --enable fulltext index EXEC sp_fulltext_database 'enable' 
+4
source share

You do not specify which version of SQL Server you are using, but if it is SQL Express, you need to make sure that you have downloaded and installed SQL Server 2008 with advanced services. A β€œnormal” installation of SQL Server Express does not include full-text search (to minimize packet size). Browse and download the different versions here .

If you are using a non-express version, you need to make sure that you have installed the full-text search function - if you haven’t done so, run the installer and select "full-text search" on the function pages.

+2
source share

Where do you look that its gray? If in the database you need to go to the repository / full-text directories in the management studio to change the full-text settings in SQL Server 2008.

You can check it installed first by going to services; By default, it is disabled after installation. If it is not installed, you can change the installed components by adding uninstall programs.

0
source share

Try creating a new database because I had the same problem too. I just created a new database and am glad to see that a full-text index is included.

0
source share

I fixed the problem by restarting SSMS 18.1.

0
source share

All Articles