Configuration Wizard failing after migrating database from on-premises to AzureSQL

This issue occurs when migrating the SolarWinds Platform database from an on-premises SQL Server to AzureSQL. AzureSQL supports only the default PRIMARY filegroup, so all database objects are moved there during migration. However, metadata may still reference other filegroups such as ENTITIES or TIMESERIES, causing the Configuration Wizard to fail.

Symptoms

ERROR IoC+<>c - Failure during modifying schema. System.Data.SqlClient.SqlException (0x80131904): dbm_EnsureMEObjects: dbm_CreateMEObjects: dbm_CreateMETypeTable: Invalid filegroup 'ENTITIES' specified. CREATE TABLE CLM_AwsVpnConnectionData_man_1
(
     [Id] bigint NOT NULL,
     [VpnConnectionId] nvarchar(max) NULL ,
     [Name] nvarchar(max) NULL ,
     [VpnGatewayId] int NULL ,
     [CustomerGatewayId] nvarchar(max) NULL ,
     [TransitGatewayId] nvarchar(max) NULL ,
     [Category] nvarchar(max) NULL ,
     [CoreNetworkArn] nvarchar(max) NULL ,
     [CoreNetworkAttachmentArn] nvarchar(max) NULL ,
     [CustomerGatewayConfiguration] nvarchar(max) NULL ,
     [GatewayAssociationState] nvarchar(max) NULL ,
     [AccountId] int NULL ,
     [RegionId] int NULL ,
     [RemoteCidr] nvarchar(max) NULL 
) ON [ENTITIES];NONE, 

Another example error:

2025-08-23 08:09:11,360 [16] ERROR IoC+<>c - Failure during modifying schema. System.Data.SqlClient.SqlException (0x80131904): dbm_EnsureMEObjects: dbm_CreateMEObjects: dbm_CreateMETypeTable: Invalid filegroup 'ENTITIES' specified. CREATE TABLE Cloud_Aws_SqlDatabaseData_man_1
(
     [ID] bigint NOT NULL,
     [ResourceId] nvarchar(255) NOT NULL DEFAULT '',
     [FirstSeenUtc] datetime2 NULL ,
     [DbInstanceArn] nvarchar(255) NULL ,
     [Engine] nvarchar(255) NULL ,
     [Address] nvarchar(255) NULL ,
     [VpcId] nvarchar(255) NULL ,
     [AvailabilityZone] nvarchar(255) NULL ,
     [AllocatedStorage] int NULL ,
     [Region] nvarchar(255) NULL ,
     [DbInstanceClass] nvarchar(255) NULL ,
     [CloudAccount] bigint NOT NULL DEFAULT 0
) ON [ENTITIES];NONE,

This issue occurs because AzureSQL supports only the PRIMARY filegroup. During migration, all database objects are moved to this default filegroup. However, the SolarWinds Platform metadata may still contain references to other filegroups such as ENTITIES and TIMESERIES. This mismatch causes the Configuration Wizard to fail when it attempts to create or modify tables specifying invalid filegroups.

Recommended Solution

Workaround (If Upgrade Is Not Possible)

-- 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.

UPDATE dbm_ManagedEntitiesProcessingConfig
   SET [Filegroup] = 'PRIMARY'
  WHERE [Filegroup] != 'PRIMARY';

UPDATE dbm_TimeSerieProcessingConfig
   SET [Filegroup] = 'PRIMARY'
  WHERE [Filegroup] != 'PRIMARY';

UPDATE dbm_DatabaseProperties
   SET [Value] = 'PRIMARY'
 WHERE [Key] = 'TimeSeries.FileGroup';

 UPDATE dbm_DatabaseProperties
   SET [Value] = 'PRIMARY'
 WHERE [Key] = 'Entities.FileGroup';

4. Re-run the configuration wizard.

If the problem persists after the fixed version, please file a SolarWinds support ticket.