

Troubleshooting

Full-Text Index Option Disabled

When right-clicking the table that you want to create the full-text index on, the option "Full-Text Index" is disabled.

This probably means that the service for full-text searches in SQL databases is not installed. To check if that is the case, execute the following statement:

SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled')

If it returns 0 the service is not installed. Run the SQL Server installation again and make sure to include the full-text searching feature.

Missing Full-text Index

An error is thrown by SQL Server when creating the stored procedure csp_addon_documentsearch_finddocuments:

Cannot use a CONTAINS or FREETEXT predicate on table or indexed view 'dbo.file' because it is not full-text indexed.

This means that a full-text search index must be created on the column dbo.file.data. Try to repeat step 1 in the Installation instructions.

Useful SQL Commands

Below is a SELECT statement for showing some information about the full-text index. It is however a bit unclear exactly what some of them (TableFulltextDocsProcessed, TableFulltextFailCount and TableFulltextItemCount) show.

declare @id int
select @id = id FROM sys.sysobjects where [Name] = 'file'
select 'TableFullTextBackgroundUpdateIndexOn' as 'Property', objectpropertyex(@id, 'TableFullTextBackgroundUpdateIndexOn') as 'Value'
union select 'TableFullTextChangeTrackingOn', objectpropertyex(@id, 'TableFullTextChangeTrackingOn')
union select 'TableFulltextDocsProcessed', objectpropertyex(@id, 'TableFulltextDocsProcessed') 
union select 'TableFulltextFailCount', objectpropertyex(@id, 'TableFulltextFailCount') 
union select 'TableFulltextItemCount', objectpropertyex(@id, 'TableFulltextItemCount') 
union select 'TableFulltextKeyColumn', objectpropertyex(@id, 'TableFulltextKeyColumn') 
union select 'TableFulltextPendingChanges', objectpropertyex(@id, 'TableFulltextPendingChanges') 
union select 'TableHasActiveFulltextIndex', objectpropertyex(@id, 'TableHasActiveFulltextIndex')