Full-Text Search
On this page
Alloy Navigator creates its own full-text catalogs on SQL Server, and their layout is fixed. When the full-text index is missing, search still works, only slower and with slightly different matching. For how technicians search, see Find Records.
You check the state of full-text search on the System Performance page of the Admin Center and of the Settings App.
Check the state of full-text search
Full-text search counts as working when full-text search is installed on SQL
Server and the last index the Automation Server creates, the index on the
Name column of Service_Catalog_Items, exists. The Admin
Center and the Settings App make the same check.
In the Admin Center
The Full-text search section of the System Performance page shows one of these messages:
| Message | Meaning |
|---|---|
| "Full-Text Search is enabled." | Full-text search works. |
| "Full-Text Search is unavailable." and "The Full Text Search component is not installed on your SQL Server instance." | Full-text search does not work. The page also shows this when full-text search is installed on SQL Server but the index is not complete yet. |
| "Full-Text Search is not working." | The page could not get the state from the server. |
The section has no controls.
In the Settings App
Before you begin:
- Your account holds the administrative right for the System Performance page.
To check the state of full-text search:
- In the Settings App, open General > System Performance.
- Look at the Full-text search group. It reads "Full-Text Search is enabled." or "Full-Text Search is disabled."
- When an error of the last attempt is kept, the group shows a View details link. Click it to read the error in the Full-Text Search Details window.
Full-text catalogs
Eight catalogs each cover one table with long text. A ninth, shared catalog,
ObjectCatalog, covers the name column of fifteen further tables.
| Catalog | Table | Indexed columns |
|---|---|---|
IncidentCatalog |
Incidents |
Description, Summary, Resolution, Notes |
ProblemCatalog |
Problems |
Description, Summary, Notes |
Change_RequestCatalog |
Change_Requests |
Description, Summary, Notes |
Service_RequestCatalog |
Service_Requests |
Description, Summary, Notes |
Work_OrderCatalog |
Work_Orders |
Description, Summary, Resolution, Notes |
ActivityCatalog |
Activity |
Details |
KB_ArticleCatalog |
KB_Articles |
Title, Content_Text, Notes |
ContractCatalog |
Contracts |
Description, Title, Notes |
ObjectCatalog |
Computers, Hardware, Software_Licenses, Documents, Networks, Configurations, Services, Tracked_Software, Library, User_Groups, Organizational_Units, Assets, Service_Catalog_Items |
Name |
ObjectCatalog |
Locations |
Location |
ObjectCatalog |
Persons |
Full_Name |
Every indexed column except Content_Text holds a field that technicians
see. Where the field is rich text, the index covers its plain-text part.
Content_Text is the plain-text copy of a Knowledge Base article's rich-text
Content field. The Web App keeps it as a hidden field, so it never appears on
a form or as a column there, and a match in it is a match in the article's
Content field.
The field labels below are those of a new 2026.1 database created with the Default Workflow; see Default Workflow Configuration. An upgraded database need not have these labels, and an administrator may have changed them.
- The fields in the
Description,Summary,Resolution,Notes,Details,Title,Name, andLocationcolumns have the default labels Description, Summary, Resolution, Notes, Details, Title, Name, and Location. - The field in the
Full_Namecolumn has the default label Full Name. - The article's
Contentfield is labeled Content.
How the index is created
On a healthy installation, nobody enables full-text search by hand: the active Automation Server creates the index shortly after it becomes active.
- Two minutes after the Automation Server becomes active, at service start or when a standby server takes over, it checks whether full-text search is installed on SQL Server. If it is, the Automation Server creates the catalogs and indexes that are missing.
- After a database restore or a database move, the index comes back at the next start of the Automation Server.
- Before it creates the real indexes, the Automation Server tries a query on a temporary catalog and removes that catalog again. A SQL Server that accepts a catalog but cannot answer a full-text query therefore fails early, and any failure turns full-text search off again instead of leaving it half built.
- A failure is reported as an Automation Server runtime error with the context "Enabling Full-Text Search.". The text of the failure is stored, and it is cleared when enabling succeeds.
What happens without full-text search
Search does not fail when the index is missing. Every field is then searched for the text anywhere in it, instead of for words that start with the text. You notice slower searches and slightly different matches, not an error.