DTU Tier S3 or later

vCore Tiers

Not sure what version your products are? Log in to the SolarWinds Platform Web Console and check the footer.

Gen5:

• 4 vCores (small environment)
• 8 vCores (medium environments)
• 16 vCores (large environments)
• 40 vCores (extra large environments

Back up your SolarWinds Platform database. If you need help, please check your vendor's site for documentation and instructions.

If you have your database on a VM, create a snapshot or copy of your VM.

Run the following script on your SolarWinds Platform database to prevent redundant spaces in column names:

BEGIN TRANSACTION
    DECLARE @definition NVARCHAR(255)
    DECLARE @table NVARCHAR(255)
    DECLARE @constraint NVARCHAR(255)
    DECLARE @getConstraints CURSOR
    DECLARE @sqlCommand NVARCHAR(255)
    DECLARE @correctConstraint NVARCHAR(255)
    DECLARE @errorMsg VARCHAR(MAX)
    DECLARE @errorSeverity INT
    DECLARE @errorState INT
    DECLARE @columnName NVARCHAR(255)

    SET @getConstraints = CURSOR FOR
    SELECT t.name, c.Name, c.definition FROM sys.check_constraints c
    INNER JOIN sys.tables t ON t.object_id = c.parent_object_id
    WHERE c.name LIKE N'CHK_CiscoBuffers_Detail%' or c.name LIKE N'CHK_CiscoBuffers_Hourly%' or c.name LIKE N'CHK_CiscoBuffers_Daily%'
	or c.name LIKE N'CHK_CPULoad_Detail%' or c.name LIKE N'CHK_CPULoad_Hourly%' or c.name LIKE N'chk_CPULoad_Daily%'
	or c.name LIKE N'CHK_LoadAverage_Detail%' or c.name LIKE N'CHK_LoadAverage_Hourly%' or c.name LIKE N'CHK_LoadAverage_Daily%'
	or c.name LIKE N'CHK_ResponseTime_Detail%' or c.name LIKE N'CHK_ResponseTime_Hourly%' or c.name LIKE N'CHK_ResponseTime_Daily%'
    or c.name LIKE N'CHK_VolumeUsage_Detail%' or c.name LIKE N'CHK_VolumeUsage_Hourly%' or c.name LIKE N'CHK_VolumeUsage_Daily%'
	 or c.name LIKE N'CHK_InterfaceErrors_Detail%' or c.name LIKE N'CHK_InterfaceErrors_Hourly%' or c.name LIKE N'CHK_InterfaceErrors_Daily%'
	 or c.name LIKE N'CHK_InterfaceTraffic_Detail%' or c.name LIKE N'CHK_InterfaceTraffic_Hourly%' or c.name LIKE N'CHK_InterfaceTraffic_Daily%'
	
    BEGIN TRY
        OPEN @getConstraints
        FETCH NEXT
        FROM @getConstraints INTO @table, @constraint, @definition
        WHILE @@FETCH_STATUS = 0
        BEGIN
            IF (CHARINDEX('LoadAverage',@table) > 0)
		SET @columnName = 'TimeStampUTC'
	    ELSE
                SET @columnName = 'DateTime'

            IF (CHARINDEX(@columnName + ' ', @definition) > 0)
            BEGIN
                SET @sqlCommand = 'ALTER TABLE [dbo].['+ @table +'] DROP CONSTRAINT ['+ @constraint +']';
                EXEC (@sqlCommand)

                SET @correctConstraint = REPLACE(@definition, @columnName + ' ', @columnName)
                SET @sqlCommand = 'ALTER TABLE [dbo].['+ @table +'] WITH CHECK ADD CONSTRAINT ['+ @constraint +'] CHECK '+ @correctConstraint;
                EXEC (@sqlCommand)
            END
            FETCH NEXT
            FROM @getConstraints INTO @table, @constraint, @definition
        END

        COMMIT TRANSACTION;
    END TRY
    BEGIN CATCH
        SELECT @errorMsg = Error_Message() + ' ' + @sqlCommand, @errorSeverity = Error_Severity(), @errorState = Error_State()
        RAISERROR (@errorMsg, @errorSeverity, @errorState);
        IF @@TRANCOUNT > 0
            ROLLBACK TRANSACTION;
    END CATCH

    CLOSE @getConstraints
    DEALLOCATE @getConstraints

If the following issue occurs when exporting the database to the bacpac format, back up your database and run the following script.

Error SQL71501: Error validating element [dbo].[Cortex_CS_Orion_ApiPoller_ApiPoller_Metrics]: View:
[dbo].[Cortex_CS_Orion_ApiPoller_ApiPoller_Metrics] has an unresolved reference to object 
[dbo].[Cortex_CS_Orion_ApiPoller_ApiPoller_Metrics_Detail_legacy].

Reorganize Views to fix export issues

DECLARE @tableName NVARCHAR(255)
 DECLARE @constraint NVARCHAR(255)
 DECLARE @getCortexTables CURSOR
SET @getCortexTables = CURSOR FOR
select distinct TableName from dbm_TimeSeriesConfig where Tablename like 'Cortex_CS_%'


if (select count(1) from dbm_DatabaseProperties where [Key]='TimeSeries.Driver' and Value='LegacyToColumnStore')=1
BEGIN



    BEGIN TRY
        OPEN @getCortexTables
        FETCH NEXT
        FROM @getCortexTables INTO @tablename
        WHILE @@FETCH_STATUS = 0
        BEGIN
		 exec dbm_CreateViews @tablename
		 print 'Recreating Cortex views'
		 FETCH NEXT
        FROM @getCortexTables INTO @tablename
		END
    END TRY
	BEGIN CATCH
		ROLLBACK TRANSACTION;
		print 'Problem with recreating Cortex views'
	END CATCH;

END

If you encounter the following issue when exporting to bacpac, create a login for the user or delete the user. See the topic on troubleshooting orphan users in Microsoft help (©2020 Microsoft, obtained from https://docs.microsoft.com/en-us/sql/sql-server/failover-clusters/troubleshoot-orphaned-users-sql-server?view=sql-server-ver15 on September 29, 2020).

Error SQL71564: Error validating element [Username]: The element [Username] has been orphaned from its login and cannot be deployed.

To migrate to Azure SQL:

Run the Deploy Database to Microsoft Azure SQL Database task.

You can also use the Export Data-tier Application to save the database file to a drive or to the Azure storage and then go to SQL Studio on the Azure SQL server and Import Data-tier Application.

To migrate to Azure Managed Instance:

1. Use the Export Data-tier application to save the database file to a drive or to the Azure Storage.
2. Go to SQL Studio on the Azure Managed Instance server and use the Import Data-tier Application.

5. Run the Configuration wizard on all servers

Perform the following instructions on all servers in your SolarWinds Platform environment to update the location for the SolarWinds Platform database:

• Main SolarWinds Platform server (main polling engine)
• Every Additional Polling Engine
• Additional web server

If you are using a custom port for your SQL server, see Using Orion with a MS SQL server listening on a custom port.

1. Run the Configuration wizard to update the database location.
2. On Database Settings, specify your new database server in the SQL Server field.
3. To use SQL authentication, select Switch user (Windows, Azure Active Directory or SQL Server Authentication), provide the SA account credentials, and click Next.
4. Select Use an Existing Database and select or type the existing database name, and click Next. If you are prompted to use the existing database, click Yes.
5. Select Create a New Account, and provide a New Account name. Creating a new account ensures that Orion has required access to your migrated database. The New Account must be a member of the securityadmin server role. The sysadmin role and the sa user account are always members of securityadmin.
6. Provide and confirm an account Password, and click Next.

   Make sure your password meets the Azure password requirements so that the wizard doesn't fail because of an invalid password.

7. Click Finish to complete the update.

Back up your SolarWinds Platform database. If you need help, please check your vendor's site for documentation and instructions.

If you have your database on a VM, create a snapshot or copy of your VM.

1. Use the Export Data-tier Application to save the database file to a drive or to the Azure storage.
2. In the SQL Server Management Studio, Import Data-tier Application.

4. Run the Configuration Wizard on all servers

Perform the following instructions on all servers in your SolarWinds Platform environment to update the location for the SolarWinds Platform database:

• Main SolarWinds Platform server (main polling engine)
• Every Additional Polling Engine
• Additional web server

If you are using a custom port for your SQL server, see Using Orion with a MS SQL server listening on a custom port.

1. Run the Configuration wizard to update the database location.
2. On Database Settings, specify your new database server in the SQL Server field.
3. To use SQL authentication, select Switch user (Windows, Azure Active Directory or SQL Server Authentication), provide the SA account credentials, and click Next.
4. Select Use an Existing Database and select or type the existing database name, and click Next. If you are prompted to use the existing database, click Yes.
5. Select Create a New Account, and provide a New Account name. Creating a new account ensures that Orion has required access to your migrated database. The New Account must be a member of the securityadmin server role. The sysadmin role and the sa user account are always members of securityadmin.
6. Provide and confirm an account Password, and click Next.

   Make sure you password meets the Azure password requirements so that the wizard doesn't fail because of an invalid password.

7. Click Finish to complete the update.