Network Management

Rapid growth of SQL Server full-text logs after migrating the SolarWinds Platform database to SQL Server 2025

The article would help resolve the issue of rapid growth of SQL Server full-text logs

First published date

6/19/2026 4:17 PM

Last published date

6/19/2026 4:17 PM

Overview

After migrating the SolarWinds Platform SQL database from SQL Server 2016 to SQL Server 2025, SQL Server full-text crawl logs (SQLFT*.LOG) grow extremely rapidly and can consume large amounts of disk space (for example, a single SQLFT*.LOG file reaching 74 GB). The growth is driven by repeated full-text index population failures against the SolarWindsOrionLog database, and if left unmanaged can cause stability issues on the SQL Server.

Product section

Orion Platform

Cause

  • SQL Server 2025 (17.x) introduced a new full-text index architecture and removed the legacy word-breaker and filter binaries used by the previous ("version 1") full-text indexes.

  • After a migration or in-place upgrade, existing catalogs and indexes remain marked as index_version = 1, but the version 1 binaries those indexes depend on no longer exist on disk.

  • Each time the full-text gatherer attempts to auto-populate the SolarWindsOrionLog tables, it cannot locate the required filter binaries and fails with 0x80070002.

Resolution

These steps should be performed by your DBA.

 

Target Database: SolarWindsOrionLog

 

1. Upgrade to version v2 (Recommended), or
2. Change compatibility back to v1.

 

Visit the official Microsoft documentation below for the steps:

Database Engine: Breaking Changes - SQL Server 2025 | Microsoft Learn

https://learn.microsoft.com/en-us/sql/database-engine/breaking-changes-to-database-engine-features-in-sql-server-2025?view=sql-server-ver17#fu