Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 14 additions & 11 deletions data-explorer/create-table-wizard.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,15 @@
---
title: Create a table in Azure Data Explorer
title: Create a Table in Azure Data Explorer
description: Learn how to easily create a table and manually define the schema in Azure Data Explorer with the table creation wizard.
ms.reviewer: aksdi
ms.topic: how-to
ms.date: 11/13/2024
ms.date: 02/02/2026
# Customer intent: As a data engineer, I want to create an empty table in Azure Data Explorer so that I can ingest data and query it.
---

# Create a table in Azure Data Explorer

Creating a table is an important step in the process of [data ingestion](ingest-data-overview.md) and [query](/azure/data-explorer/kusto/query/tutorials/learn-common-operators) in Azure Data Explorer. The following article shows how to create a table and schema mapping quickly and easily using the Azure Data Explorer web UI.
Creating a table is an important step in the process of [data ingestion](ingest-data-overview.md) and [query](/azure/data-explorer/kusto/query/tutorials/learn-common-operators) in Azure Data Explorer. The following article shows how to create a table and schema mapping quickly and easily by using the Azure Data Explorer web UI.

> [!NOTE]
> To create a new table based on existing data, see [Get data from file](get-data-file.md) or [Get data from Azure storage](get-data-storage.md).
Expand All @@ -21,39 +22,41 @@ Creating a table is an important step in the process of [data ingestion](ingest-
* Sign in to the [Azure Data Explorer web UI](https://dataexplorer.azure.com/) and [add a connection to your cluster](web-query-data.md#add-clusters).

> [!NOTE]
> To enable access between a cluster and a storage account without public access (restricted to private endpoint/service endpoint), see [Create a Managed Private Endpoint](security-network-managed-private-endpoint-create.md).
> To enable access between a cluster and a storage account without public access (restricted to private endpoint or service endpoint), see [Create a Managed Private Endpoint](security-network-managed-private-endpoint-create.md).

## Create a table

1. In the navigation pane, select **Query**.

1. Select **+ Add** > **Table** or right-click on the database where you want to create the table and select **Create table**.

:::image type="content" source="media/create-table-wizard/add-table.png" alt-text="Screenshot of the Add Table option in the left navigation pane.":::

## Destination tab

The **Create table** window opens with the **Destination** tab selected.

1. The **Cluster** and **Database** fields are prepopulated. You can select different values from the dropdown menu.
1. The portal prepopulates the **Cluster** and **Database** fields. You can select different values from the dropdown menu.
1. In **Table name**, enter a name for your table.

> [!TIP]
> Table names can be up to 1024 characters including alphanumeric, hyphens, and underscores. Special characters aren't supported.
> Table names can be up to 1,024 characters including alphanumeric, hyphens, and underscores. Special characters aren't supported.

1. Select **Next: Schema**
1. Select **Next: Schema**.

## Schema tab

1. Select **Add new column** and the **Edit columns** panel opens.
1. Select **Add new column**. The **Edit columns** panel opens.
1. For each column, enter **Column name** and **Data type**. Create more columns by selecting **Add column**.

:::image type="content" source="media/create-table-wizard/edit-columns.png" alt-text="Screenshot of Edit columns pane, in which you input the column name and data type in Azure Data Explorer.":::

1. Select **Save**. The schema is displayed.
1. Select **Save**. The portal displays the schema.
1. Select **Next: Create table**.

:::image type="content" source="media/create-table-wizard/create-table.png" alt-text="Screenshot of create emptytable wizard with schema input in Azure Data Explorer.":::
:::image type="content" source="media/create-table-wizard/create-table.png" alt-text="Screenshot of create empty table wizard with schema input in Azure Data Explorer.":::

A new table is created in your target destination, with the schema you defined.
The portal creates a new table in your target destination, using the schema you defined.

## Related content

Expand Down
16 changes: 8 additions & 8 deletions data-explorer/dashboard-visuals.md
Original file line number Diff line number Diff line change
@@ -1,23 +1,24 @@
---
title: Dashboard-specific visuals
title: Dashboard-specific Visuals
description: Visualizations available in Azure Data Explorer web UI or dashboards
ms.reviewer: gabil
ms.topic: how-to
ms.date: 02/21/2024
ms.date: 02/02/2026
---

# Dashboard-specific visuals

All visualizations that are created in the context of the [render operator](/azure/data-explorer/kusto/query/render-operator) are available in dashboard visualizations. However, the following visualizations are only available in [Azure Data Explorer dashboards](azure-data-explorer-dashboards.md), Real-Time Dashboards, or [Azure Data Explorer web UI](/azure/data-explorer/add-query-visualization), and not with the render operator.
All visualizations that you create in the context of the [render operator](/azure/data-explorer/kusto/query/render-operator) are available in dashboard visualizations. However, the following visualizations are only available in [Azure Data Explorer dashboards](azure-data-explorer-dashboards.md), Real-Time Dashboards, or [Azure Data Explorer web UI](/azure/data-explorer/add-query-visualization), and aren't available by using the render operator.

To learn how to customize any dashboard visuals, see [Customize Azure Data Explorer dashboard visuals](dashboard-customize-visuals.md)

For general information on dashboards in Azure Data Explorer, see [Visualize data with Azure Data Explorer dashboards](azure-data-explorer-dashboards.md).

## Funnel chart

A funnel chart visualizes a linear process that has sequential, connected stages. Each funnel stage represents a percentage of the total. So, in most cases, a funnel chart is shaped like a funnel, with the first stage being the largest, and each subsequent stage smaller than its predecessor.
A funnel chart visualizes a linear process that has sequential, connected stages. Each funnel stage represents a percentage of the total. In most cases, a funnel chart is shaped like a funnel, with the first stage being the largest, and each subsequent stage smaller than its predecessor.

The following example visualizes the progression of Server requests, showing the total number of sessions, requests, and their completion status. It highlights the drop-off from sessions to requests and the proportion of completed versus incomplete requests.
The following example visualizes the progression of server requests, showing the total number of sessions, requests, and their completion status. It highlights the drop-off from sessions to requests and the proportion of completed versus incomplete requests.

### Example query

Expand Down Expand Up @@ -56,13 +57,13 @@ funnelData

A heatmap shows values for a main variable of interest across two axis variables as a grid of colored squares.

To render a heatmap, the query must generate a table with three columns. The data used for the value field must be numeric. The columns that will be used for x and y values use the following rules:
To render a heatmap, the query must generate a table with three columns. The data used for the value field must be numeric. The columns that you use for x and y values must follow these rules:

- If the values in column *x* are in the `string` format, the values in the column *y* must also be in the `string` format.
- If the values in column *x* are in the `datetime` format, the values in the column *y* must be numeric.

> [!NOTE]
> We recommend specifying each data field, instead of letting the tool infer the data source.
> Specify each data field instead of letting the tool infer the data source.

The following example shows the distribution of the five most frequent SQL metrics across different metric types. It highlights which metric types are most common for each SQL metric, making it easy to identify activity patterns in the top metrics.

Expand All @@ -72,7 +73,6 @@ The following example shows the distribution of the five most frequent SQL metri
let topMetrics = TransformedServerMetrics
| summarize TotalCount = count() by SQLMetrics
| top 5 by TotalCount; // pick only the 5 most common metrics

TransformedServerMetrics
| where SQLMetrics in (topMetrics | project SQLMetrics)
| summarize Count = count() by SQLMetrics, MetricType
Expand Down
30 changes: 14 additions & 16 deletions data-explorer/get-data-file.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Get data from a file
title: Get Data From a File
description: Learn how to get data from a local file in Azure Data Explorer.
ms.reviewer: sharmaanshul
ms.topic: how-to
Expand All @@ -8,7 +8,7 @@ ms.custom: sfi-image-nochange
---
# Get data from file

Data ingestion is the process used to load data from one or more sources into a table in Azure Data Explorer. Once ingested, the data becomes available for query. In this article, you learn you how to get data from a local file into either a new or existing table.
Data ingestion is the process of loading data from one or more sources into a table in Azure Data Explorer. Once ingested, the data is available for query. In this article, you learn how to get data from a local file into either a new or existing table.

For general information on data ingestion, see [Azure Data Explorer data ingestion overview](ingest-data-overview.md).

Expand All @@ -20,50 +20,48 @@ For general information on data ingestion, see [Azure Data Explorer data ingesti

## Get data

1. From the left menu, select **Query**.
1. From the left navigation pane, select **Query**.

1. Right-click on the database where you want to ingest the data. Select **Get data**.

:::image type="content" source="media/get-data-file/get-data.png" alt-text="Screenshot of query tab, with right-click on a database and the get options dialog open." lightbox="media/get-data-file/get-data.png":::

## Source
## Select data source

In the **Get data** window, the **Source** tab is selected.

Select the data source from the available list. In this example, you're ingesting data from a **Local file**.

:::image type="content" source="media/get-data-file/select-data-source.png" alt-text="Screenshot of get data window with source tab selected." lightbox="media/get-data-file/select-data-source.png":::
:::image type="content" source="media/get-data-file/source.png" alt-text="Screenshot of get data window with source tab selected." lightbox="media/get-data-file/source.png":::

[!INCLUDE [ingestion-size-limit](includes/cross-repo/ingestion-size-limit.md)]

## Configure
## Configure data ingestion

1. Select a target database and table. If you want to ingest data into a new table, select **+ New table** and enter a table name.
1. Select a target database and table. To ingest data into a new table, select **+ New table** and enter a table name.

> [!NOTE]
> Table names can be up to 1024 characters including spaces, alphanumeric, hyphens, and underscores. Special characters aren't supported.
> Table names can be up to 1,024 characters, including spaces, alphanumeric characters, hyphens, and underscores. Special characters aren't supported.

1. Either drag files into the window, or select **Browse for files**.
1. Drag files into the window, or select **Browse for files**.

> [!NOTE]
> You can add up to 1,000 files. Each file can be a max of 1 GB uncompressed.
> You can add up to 1,000 files. Each file can be a maximum of 1 GB uncompressed.

:::image type="content" source="media/get-data-file/configure-tab.png" alt-text="Screenshot of configure tab with new table entered and one sample data file selected." lightbox="media/get-data-file/configure-tab.png":::
:::image type="content" source="media/get-data-file/configure.png" alt-text="Screenshot of configure tab with new table entered and one sample data file selected." lightbox="media/get-data-file/configure.png":::

1. Select **Next**
1. Select **Next**.

## Inspect

The **Inspect** tab opens with a preview of the data.

To complete the ingestion process, select **Finish**.

:::image type="content" source="media/get-data-file/inspect-data.png" alt-text="Screenshot of the inspect tab." lightbox="media/get-data-file/inspect-data.png":::
:::image type="content" source="media/get-data-file/inspect.png" alt-text="Screenshot of the inspect tab." lightbox="media/get-data-file/inspect.png":::

Optionally:

* Select **Command viewer** to view and copy the automatic commands generated from your inputs.
* Use the **Schema definition file** dropdown to change the file that the schema is inferred from.
* Change the automatically inferred data format by selecting the desired format from the dropdown. See [Data formats supported by Azure Data Explorer for ingestion](ingestion-supported-formats.md).
* [Edit columns](#edit-columns).
* Explore [Advanced options based on data type](#advanced-options-based-on-data-type).
Expand All @@ -78,7 +76,7 @@ Optionally:

## Summary

In the **Data preparation** window, all three steps are marked with green check marks when data ingestion finishes successfully. You can view the commands that were used for each step, or select a card to query, visualize, or drop the ingested data.
In the **Data preparation** window, all three steps show green check marks when data ingestion finishes successfully. You can view the commands that each step used, or select a card to query, visualize, or drop the ingested data.

:::image type="content" source="media/get-data-file/summary.png" alt-text="Screenshot of summary page with successful ingestion completed." lightbox="media/get-data-file/summary.png":::

Expand Down
Loading