Text Indexing Enabled by Default on Instance ColumnsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Text indexing is a platform capability that enables efficient searching across supported text-based fields. Customers may notice that text indexing is enabled for a number of columns on their instance even though it was not explicitly configured or enabled by them. This is expected behavior. For many supported columns, text indexing is enabled by default as part of the platform configuration to provide optimized search capabilities and improve the performance of text-based queries. Customers who do not require text indexing for specific columns can review the configuration and, where appropriate, disable text indexing. Why is text indexing enabled? Text indexing allows the platform to efficiently search and retrieve records based on the content of text fields. Without an appropriate text index, searches against large text-based columns may require the system to examine a larger number of records, which can result in increased database processing and longer query execution times. To provide an optimized out-of-the-box experience, text indexing is enabled by default for many supported columns. Therefore, seeing text indexing enabled does not necessarily indicate that it was manually configured or enabled by an administrator. The default configuration is intended to support common search and query use cases across the platform. Is text indexing intentionally enabled on my instance? If you observe text indexing enabled on a column that your team did not explicitly configure, this is generally expected platform behavior. Text indexing may be enabled by default on supported columns as part of the standard instance configuration. It is therefore possible for an instance to have text indexing enabled across multiple columns without any corresponding customer-initiated configuration change. Can text indexing be disabled? Yes. If text indexing is not required for a particular column or if the associated search functionality is not being used, customers may choose to disable it where supported. Here is the KB for disabling text index events : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0721202 When should text indexing be disabled? Text indexing should be evaluated based on the actual usage of the corresponding column. You may consider disabling text indexing when: The column is not used for text-based searches.The indexed content is not required for search functionality.The column contains a large volume of data but has limited search usage.Maintaining the text index introduces unnecessary database or system overhead.Performance analysis indicates that the text index is contributing significantly to resource consumption.The associated search functionality is not required for your use case. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Reduce unnecessary text index events from causing overhead on events processing