Quick Start Guide

Get started with Kinetica in the Azure Marketplace

Before You Start

Note that provisioning Kinetica through the Azure Marketplace will incur charges in your Azure subscription. These charges will depend on the type and size of the cluster you provision as well as the hours of usage. Once the provisioning is complete, the database will start running.


Azure Account

An Azure account is required to provision Marketplace applications, including Kinetica. If you have an Azure free account, you will need to upgrade to an Azure Pay As You Go Account before provisioning Kinetica.

Subscription Owner Role

Kinetica in Azure requires that you are an owner on the Azure Subscription in order to provision the cluster. Check your subscriptions in the Azure Portal to confirm your role.

Azure Resource Providers

Make sure you have the following resource providers enabled:

  • Microsoft.AlertsManagement
  • Microsoft.ContainerInstance
  • Microsoft.OperationsManagement

Azure Quota

Make sure you have an adequate quota in your Azure subscription and Azure region for the following resources:

  • Microsoft.Network

    • Static Public IP Addresses (1 per cluster deployment)
    • Public IP Addresses - Standard (1 per cluster deployment)
    • Public IP Addresses - Basic (1 per cluster deployment)
  • Microsoft.Compute

    The number of required cores for Standard ESv4 and Standard NVSv3 families depends on the cluster size and configuration:

    GPU AccelerationCluster SizeRequired Standard ESv4 CoresRequired Standard NVSv3 Cores


Choosing an Offer

There are two different offers in Azure for Kinetica, depending on your preferred consumption and payment model:

All other features and functions are the same between the two offers.

Kinetica Pay As You Go (PAYG)

Kinetica license fees are based on your hourly usage and the size of the cluster. Prices are the same for both Standard (CPU) and GPU-Accelerated deployments.

GPU AccelerationCluster SizePAYG cost/hour

Click the following links to review the PAYG offering in Azure and begin the provisioning process.

Kinetica Bring Your Own License (BYOL)

For customers with an existing Kinetica license, you can choose this option and input your existing Kinetica license key. You will not incur additional Kinetica license charges, although you will be charged for Azure infrastructure costs.

Click the following links to review the BYOL offering in Azure and begin the provisioning process.


The first step of the Azure provisioning process requires certain basic information about your Azure subscription and Kinetica deployment:

  • Subscription: The Azure Subscription you want to use for this deployment

  • Resource Group: The Azure Resource Group that should contain the Azure Managed Application for the Kinetica deployment.

  • Region: The Azure region where Kinetica should be deployed. The following regions are currently supported:

    RegionAzure Supported Region(s)
    AfricaSouth Africa North
    Asia PacificSoutheast Asia
    AustraliaAustralia East
    BrazilBrazil South

    North Europe

    West Europe

    France Central

    IndiaCentral India
    JapanJapan East
    United Arab EmiratesUAE North
    United KingdomUK South
    United States

    East US

    East US 2

    South Central US

    West US

    West US 2

  • Kinetica License Key: [BYOL Only] To provision Kinetica in Azure, enter your existing license key.

  • Kinetica Cluster Name: A label you can use to identify a specific Kinetica instance when you have multiple Kinetica deployments. This name will be used for the Managed Application in the Resource Group specified above. The name will also be visible in the Kinetica Workbench so that you can easily differentiate among Kinetica deployments.


    We recommend using a unique name for your cluster to ensure that deployments in the same resource group do not conflict.

  • Managed Resource Group: This identifier is pre-populated by Azure and should not be changed.



As a next step, you will choose the type and size of your Kinetica Cluster.


GPU Acceleration

This setting determines whether the deployment will use GPUs to accelerate the performance of your database. This option is recommended if you have use cases that would benefit from GPU performance, such as interactive visualization of large scale geographic data or high-cardinality joins.

Kinetica Cluster Size

This setting will determine the performance of your database. Each increase in size roughly corresponds to a doubling in performance. We recommend you start with smaller cluster sizes for testing and evaluation and then scale to larger sizes (as needed) for your production deployments.

Cluster SizeRecommended UsageRecommended Data Size
Extra Small (XS)Testing and development250 GB
Small (S)Trial evaluations500 GB
Medium (M)Production environments1 TB
Large (L)Production environments2 TB
Extra Large (XL)Production environments4 TB
Extra Extra Large (2XL)Production environments8 TB
Extra Extra Extra Large (3XL)Production environments>16 TB


Not all sizes and configurations are available with the Pay-As-You-Go offer. See the table below, under Hardware Configurations, for size availability per offer.

Hardware Configurations

The following tables show the Azure infrastructure (VMs and Managed Disks) that will be deployed for the database for different sizes and configurations, as well as the availability per offer of each configuration.

All configurations use P40 2 TiB Managed Disks.

SizeVM Series# VMs# DisksPAYGBYOL
XSE20s v411XX
SE48s v412XX
ME48s v424XX
LE48s v448XX
XLE48s v4816 X
2XLE48s v41632 X
3XLE48s v43264 X
SizeVM Series# VMs# DisksPAYGBYOL
XSNV24s v312XX
SNV24s v324XX
MNV24s v348XX
LNV24s v3816 X
XLNV24s v31632 X
2XLNV24s v33264 X
3XLNV24s v364128 X


In addition to the above database infrastructure, additional Azure resources (2x E8s v4) will be provisioned for other components including the Workbench UI.

User Information

In this step, you will define the initial administrator username and password for your Kinetica cluster, as well as contact information for support.



In this step, you can choose to use the default network configuration or configure advanced options. If you are testing or evaluating Kinetica, you can select the Default Network Configuration option. If you intend to peer the Kinetica network with another Azure network, you should choose Advanced Network Configuration and review the settings. For more information on the Advanced Network Configuration, see the corresponding Azure documentation for details on the specific settings:



The settings under Advanced Network Configuration cannot be changed after provisioning.

After provisioning, you will be able to configure network security groups and rules. For instance, you could add rules to limit access to specific IP addresses or ranges.


Basic Networking Configuration


Advanced Networking Configuration


This is a standard step for provisioning Azure resources that allows you to specify your own custom tags for the resources associated with this cluster deployment.


Provisioning Time Warning

The provisioning process for Kinetica in Azure currently takes between 60 and 90 minutes.

Review & Create

In this final screen, you can review the terms and agreements for the Kinetica Cluster and the settings you have specified.

Once you click Create, the provisioning process will start.


The Kinetica cluster will start running as soon as the provisioning process completes and you will start to incur costs from the associated Azure infrastructure.

img/prov.step_create.png img/prov.step_create_in_progress.png

Validating the Cluster Deployment

After the provisioning process is complete, you should see an indication that the deployment is complete:


If the provisioning process was not successful, please contact Kinetica support <support@kinetica.com>.

Get the Workbench URL

After your deployment is complete, click on Go to resource to navigate to the Managed Application. Alternatively, you can also search for the Managed Application that you just provisioned (the name will be the Kinetica Cluster name you entered on the first page of the provisioning process).


Click on Parameters and Outputs under Settings in the left sidebar. The hostname is at the bottom of the list:



This is the hostname (e.g. kinetica-sdw-prsmowx4jmuqe.eastus.cloudapp.azure.com) you will use to connect to the Workbench. See Connecting to the Kinetica Cloud Workbench for connection instructions.

Workbench Orientation

On the left side of the screen, you will see a tabbed panel called the Explorer. The Explorer has three main views: Data, Workbooks, and Files. We will only cover the Data and Workbooks panels for the purposes of this tutorial.


The Data panel contains all of the data you have in Kinetica, like tables/views, graphs, and data sources. Data objects are sorted by type, allowing you to minimize or expand each section, and filter the object names using a text input. Right-click any object to inspect, modify, preview the data on a map, or delete the object.


The Workbooks panel contains all of your SQL workbooks and the contained worksheets in Kinetica. Worksheets allow you to explore the data in Kinetica by running SQL and visualizing the output in a chart or a map. Worksheets can contain SQL Blocks, Text Blocks, and Map Blocks. You can run a single block at a time, or run all of them in sequence from top to bottom. Kinetica ships with a Quick Start Guide workbook, that will show you how to create data sources, run integrated analytics, and visualize the results.


Quick Start Workbook

Let's open the Quick Start Guide workbook and begin ingesting data, running analytics, and visualizing the results.

Next Steps

Your journey with Kinetica has only just begun! For a walkthrough of the Quick Start Guide workbook, or for in-depth articles about Kinetica's functionality, see these links below: