Documentation forLog Analyzer
Analyzing logs is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Log Analyzer (LA). Hybrid Cloud Observability and LA are built on the self-hosted SolarWinds Platform.

LA pre-deployment notes for Microsoft Azure

Before deploying LA to Microsoft Azure, review the system requirements and the information below to help avoid installation and configuration issues.

LA officially supports the Azure SQL database and the Azure SQL managed instance. The SQL Data Warehouse and SQL Elastic database pool are not supported.

New installation

The installation process is the same as on-premise deployment. The LA database section of the Configuration Wizard accepts connections to the Azure SQL server. Azure supports SQL authentication and Azure Active Directory authentication methods.

You can select an existing database or let the Configuration Wizard create a new one.

  • The newly created database has a Standard S3 tier
  • An existing database needs to have at least Standard S3 or any of the vCore-based tiers

Azure SQL database has the Read Committed Snapshot Isolation (RCSI) level set by default, which is different from the default for on-premise RCSI level. The Configuration Wizard sets the isolation level to the same as the default on-premise database when creating a new database, but leaves it unchanged when an existing Azure SQL database is used.

Database migration

LA stores data in both the SolarWinds Platform and LA databases. The LA database migration process is the same as the SolarWinds Platform database. This topic focuses mainly on issues one may encounter when migrating the SolarWinds Platform database. The main difference is that migration from the Azure database to an on-premise database is not possible for the LA database, which means LA data is lost. However, all LA-specific settings, configurations and CBQoS data are migrated because they are stored in the SolarWinds Platform database.

You can migrate databases from SolarWinds Platform 2019.2 and higher.

Source Destination
MS SQL Server 2016 SP1 and higher

Azure SQL Server database with DTU Tier S3 and higher, or vCore Tiers

Azure SQL Server database with DTU Tier S3 and higher or vCore Tiers MS SQL Server 2016 SP1 and higher

Pre-migration checklist

Task Description
1 Upgrade SolarWinds Platform products to versions that support Azure SQL database and run the Configuration Wizard on all servers.

Determine if you are using In-Memory tables (only if you migrate from SQL 2016 SP1 or higher):


Before migration to Azure from on-premise, execute the following command on the LA database

  • After migration, the database uses Columnstore. At this point, you cannot migrate back if you have SQL 2016 RTM or lower where Columnstore isn’t supported.
  • Azure does not support file groups. After migration, everything is moved into the default primary file group.
  • The on-premise migration process for the LA database is the same as the SolarWinds Platform database.

Supported migration methods:

  • Export and import script
  • Microsoft SQL Server Management Studio
    1. Right-click a database.
    2. Select Deploy Database to Microsoft Azure SQL Database.
    3. The wizard guides you through the remaining steps.

      The server must already exist, but the wizard creates the database.

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.