Data export
Applies to: ✅ Microsoft Fabric ✅ Azure Data Explorer
Data export involves executing a Kusto query and saving its results. This process can be carried out either on the client side or the service side.
For examples on data export, see Related content.
Client-side export
Client-side export gives you control over saving query results either to the local file system or pushing them to a preferred storage location. This flexibility is facilitated through the use of Kusto client libraries. You can create an app to run queries, read the desired data, and implement an export process tailored to your requirements.
Alternatively, you can use a client tool like the Azure Data Explorer web UI to export data from your Kusto cluster. For more information, see Share queries.
Service-side export (pull)
Use the ingest from query commands to pull query results into a table in the same or different database. See the performance tips before using these commands.
Service-side export (push)
For scalable data export, the service offers various .export management commands to push query results to cloud storage, an external table, or an SQL table. This approach enhances scalability by avoiding the bottleneck of streaming through a single network connection.
Continuous data export is supported for export to external tables.
Note
The .export management commands are limited by the available data export capacity of your database. Run the .show capacity command to view the total, consumed, and remaining data export capacity.