Deploy SolarWinds NTA to Microsoft Azure
As of version 4.6, SolarWinds NTA can be installed onto Microsoft Azure. For fresh installations, you can deploy the Main NTA server onto a Microsoft Azure VM and the NTA SQL Flow Storage database onto Azure SQL. In an existing Orion environment, you can migrate the deployment from on-premise to Azure or from Azure to on-premise.
SolarWinds NTA supports only Microsoft Azure SQL database. Microsoft Azure SQL Managed Instance, SQL Data Warehouse, and SQL Elastic database pool are not supported.
Fresh installation of SolarWinds NTA onto Microsoft Azure
The installation process is the same, as if you install SolarWinds NTA in an on-premise deployment. The NTA Flow Storage configuration part of the Configuration wizard accepts the connection to the Azure SQL server. Both SQL authentication and Azure Active Directory authentication methods are supported.
You can either select an existing database or let the Configuration wizard create a new one.
- A newly created database has the Standard S3 tier.
- An existing database needs to have at least Standard S3 or any of the v-Core based tiers.
By default, the Azure SQL database has READ COMMITTED SNAPSHOT ISOLATION (RCSI) enabled, while the on-premise Microsoft SQL database enables SQL READ COMMITTED ISOLATION by default. The Configuration wizard sets the isolation level to the same one as for default on-premise databases when creating a new database. If you use an existing Azure SQL database, the isolation level stays unchanged.
Supported Azure deployments:
- Main NTA Polling Engine on Azure VM.
- NTA SQL Flow Storage database on Azure SQL (can be co-located on one SQL server together with the Orion database).
- Additional polling engine on Azure VM in a different geographical location than the Main polling Engine.
- Additional polling engine on-premise.
Migration of SolarWinds NTA to and from Microsoft Azure
NTA stores data in both the Orion database and the NTA SQL Flow Storage database. The process for migrating the Flow Storage database from on-premise to Microsoft Azure is the same, as for migrating the Orion database.
- Migrating the NTA SQL Flow Storage database from Microsoft Azure to an on-premise database is not supported. You can only migrate the NTA Flow Storage database from an on-premise database to Microsoft Azure.
- Make sure you upgraded SolarWinds NTA to a version supporting Microsoft Azure SQL database (NTA 4.6 and later) and ran the Configuration wizard.
- If you use in-memory tables, check if the Azure database tier you selected supports In-memory OLTP storage. In case it doesn't, turn off the tables:
C:\Program Files (x86)\SolarWinds\Orion\ConfigurationWizard.exe.config
<add key="TimeSeries_MemoryOptimizedTables_Enabled" value="false"/>
- Run the Configuration wizard.
- Microsoft Azure does not support filegroups. After migration, everything is moved into the default PRIMARY filegroup.
- Stop Orion Services.
- Migrate the NTA Flow Storage database using Microsoft SQL Server Management Studio.
- Run the Configuration wizard on all servers.
- Start Orion Services.