Getting started with Kusto

Azure Data Explorer is a service for storing and running interactive analytics on big data.

It's based on relational database management systems, and supports entities such as databases, tables, and columns. Complex analytical queries are made using the Kusto Query Language. Some query operators include:

  • calculated columns
  • searching and filtering on rows
  • group by-aggregates
  • join functions

The service offers excellent data ingestion and query performance:

  • It sacrifices the ability to do in-place updates of individual rows and cross-table constraints or transactions.
  • The service supplements, rather than replaces, traditional RDBMS systems for scenarios such as OLTP and data warehousing.
  • Structured, semi-structured (for example, JSON-like nested types), and unstructured (free text) data are handled equally well.

Interacting with Azure Data Explorer

The main way for users to interact with Azure Data Explorer (Kusto):

Kusto queries

A query is a read-only request to process data and return the results of this processing, without modifying the data or metadata. Kusto queries can use the SQL language, or the Kusto query language. As an example for the latter, the following query counts how many rows in the Logs table have a value in the Level column equal to the string Critical:

| where Level == "Critical"
| count


Queries can't start with the dot (.) character or the hash (#) character.

Control commands

Control commands are requests to Kusto to process and potentially modify data or metadata. For example, the following control command creates a new Kusto table with two columns, Level and Text:

.create table Logs (Level:string, Text:string)

Control commands have their own syntax, which isn't part of the Kusto Query Language syntax, although the two share many concepts. In particular, control commands are distinguished from queries by having the first character in the text of the command be the dot (.) character (which can't start a query). This distinction prevents many kinds of security attacks, simply because it prevents embedding control commands inside queries.

Not all control commands modify data or metadata. The large class of commands that start with .show, are used to display metadata or data. For example, the .show tables command returns a list of all tables in the current database.