Error during Configuration Wizard: "The index/statistics is dependent on column 'IPNodeId'" on IPAM_Node when upgrading to SolarWinds Platform 2026.1 and later

2/25/2026 3:26 PM

8/10/2026 10:06 PM

During an upgrade to SolarWinds Platform 2026.1 or later that includes IP Address Manager (IPAM) — for example, from 2025.4 to 2026.1, from 2024.2.1 to 2026.2, or from 2024.4 to 2026.2.2 — the Configuration Wizard may fail during the database configuration step, whether the upgrade is started from the Web UI or run directly via the Configuration Wizard on the server.

The following error message can be displayed. The blocking object may be reported as an index:

Database configuration failed:
•  Error while executing script- The index '<index_name>' is dependent on column 'IPNodeId'.
ALTER TABLE ALTER COLUMN IPNodeId failed because one or more objects access this column.

As one or more statistics objects (note that multiple statistics objects can be listed in a single error):

Database configuration failed:
•  Error while executing script- The statistics '_dta_stat_1471447345_1_28_27_5' is dependent on column 'IPNodeId'.
The statistics '_dta_stat_1471447345_2_1_3_28' is dependent on column 'IPNodeId'.
The statistics '_dta_stat_1471447345_1_3_28_27_5' is dependent on column 'IPNodeId'.
The statistics '_dta_stat_1471447345_2_3_28_27_1_5' is dependent on column 'IPNodeId'.
ALTER TABLE ALTER COLUMN IPNodeId failed because one or more objects access this column.

In the Configuration Wizard log (for example, under C:\ProgramData\SolarWinds\Logs\Orion), you may see entries similar to the following:

ERROR CwAuditLogger - SolarWinds Platform Database FAILED
Database configuration failed:
•  Error while executing script- The index 'missing_index_1961319_1961318_IPAM_Node' is dependent on column 'IPNodeId'.
ALTER TABLE ALTER COLUMN IPNodeId failed because one or more objects access this column.

If the upgrade was started through the Web UI (Settings > My Deployment > Updates), the Web UI will show a generic "Database configuration failed" message and remain on the failure screen. Opening the Configuration Wizard directly on the primary polling engine and re-running it reproduces the same error and log entries, confirming the failure is not specific to the Web-UI upgrade path.

This prevents the upgrade from completing successfully and halts the Configuration Wizard, leaving the SolarWinds Platform unavailable until the issue is resolved.

Hybrid Cloud Observability

This issue occurs because upgrading to SolarWinds Platform 2026.1 or later includes a database migration that changes the data type of the IPNodeId column on the [dbo].[IPAM_Node] table (for example, from int to bigint).

If there is an existing index or statistics object on IPAM_Node that still depends on IPNodeId when this migration runs, SQL Server blocks the ALTER COLUMN operation and returns an error stating that the object is dependent on that column.

Key points:

• The blocking object is not part of the standard SolarWinds Platform/IPAM schema.

• It is typically:

  • a custom index or statistics object created manually by a DBA, or

  • an object auto-generated by external/automated optimization tools (for example, SQL Server Database Engine Tuning Advisor — recognizable by the _dta_stat_... or _dta_index_... naming pattern, or missing_index_... naming used by the missing-index feature).

• SQL Server does not allow a column definition to be changed while dependent objects (such as indexes, constraints, or statistics) still reference it.

• Because of this, the ALTER TABLE ... ALTER COLUMN IPNodeId statement fails, and the upgrade cannot proceed. This has now been confirmed to occur on upgrades to 2026.1, 2026.2, and 2026.2.2 — the migration step is not limited to the 2026.1 release.

Resolution

Note the following for each query below:

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

To resolve the issue, identify and drop the custom index(es) and/or statistics object(s) that depend on IPNodeId before rerunning the Configuration Wizard.

1. Back up the SolarWinds database

Take a full backup of the SolarWinds database on your SQL Server.

2. Identify the objects that depend on IPNodeId

Connect to the SQL Server instance hosting the SolarWinds database using SQL Server Management Studio (SSMS).

Run the following to find dependent indexes (adjust the database name if necessary):

USE [SolarWindsOrion]; -- change to your SolarWinds DB name if different
SELECT i.name AS IndexName, t.name AS TableName, c.name AS ColumnName
FROM sys.indexes i
JOIN sys.index_columns ic ON i.object_id = ic.object_id AND i.index_id = ic.index_id
JOIN sys.columns c ON ic.object_id = c.object_id AND ic.column_id = c.column_id
JOIN sys.tables t ON i.object_id = t.object_id
WHERE t.name = 'IPAM_Node' AND c.name = 'IPNodeId' AND i.is_primary_key = 0; -- exclude primary key

 If the error names statistics objects (for example, _dta_stat_...) rather than an index, also run:

USE [SolarWindsOrion]; -- change to your SolarWinds DB name if different
SELECT s.name AS StatsName, t.name AS TableName, c.name AS ColumnName
FROM sys.stats s
JOIN sys.stats_columns sc ON s.object_id = sc.object_id AND s.stats_id = sc.stats_id
JOIN sys.columns c ON sc.object_id = c.object_id AND sc.column_id = c.column_id
JOIN sys.tables t ON s.object_id = t.object_id
WHERE t.name = 'IPAM_Node' AND c.name = 'IPNodeId' AND s.user_created = 1;

Note the index or statistics name(s) returned. Work with your DBA to confirm that any such object is custom/auto-generated and not required for external reporting or other business logic.

3. Drop the blocking object(s)

After confirming it is safe to remove, drop the blocking object(s). Replace <index_name> / <stats_name> with the actual name(s) from step 2. There can be more than one object listed in the error — drop all of them.

For an index:

USE [SolarWindsOrion]; -- change to your SolarWinds DB name if different
IF EXISTS (
    SELECT 1 FROM sys.indexes
    WHERE name = '<index_name>' AND object_id = OBJECT_ID('dbo.IPAM_Node')
)
BEGIN
    DROP INDEX [<index_name>] ON [dbo].[IPAM_Node];
END

 For a statistics object:

USE [SolarWindsOrion]; -- change to your SolarWinds DB name if different
IF EXISTS (
    SELECT 1 FROM sys.stats
    WHERE name = '<stats_name>' AND object_id = OBJECT_ID('dbo.IPAM_Node')
)
BEGIN
    DROP STATISTICS [dbo].[IPAM_Node].[<stats_name>];
END

Only drop non-standard, custom indexes/statistics. Do not drop primary keys or known shipped IPAM indexes unless specifically instructed by SolarWinds.

4. Re-run the Configuration Wizard

Run the SolarWinds Configuration Wizard again (either through the Web UI upgrade flow or directly on the server) and allow the database configuration step to complete. After the custom object(s) are removed, the ALTER COLUMN IPNodeId operation should succeed and the upgrade can finish successfully.

Prevent Future Occurrences

SolarWinds does not recommend creating custom indexes or statistics on SolarWinds database tables (including IPAM_Node), because they can interfere with future upgrades and schema changes. If you use third-party tuning or optimization tools (including SQL Server's Database Engine Tuning Advisor or missing-index recommendations), consider excluding the SolarWinds database from automatic index/statistics creation, or review any recommendations carefully before applying them.