Create a database shortcut

A database shortcut in Real-Time Analytics is an embedded reference within a KQL database to a source database. The source database can be one of the following:

  • A KQL Database in Real-Time Analytics
  • An Azure Data Explorer database

The behavior exhibited by the database shortcut is similar to that of a follower database.

When is a database shortcut useful?

If you have data in an Azure Data Explorer database and want to use this data in Real-Time Analytics, you can create a database shortcut to expose this data. This feature is also useful to segregate compute resources to protect a production environment from nonproduction use cases. A database shortcut can also be used to associate the costs with the party that runs queries on the data.

How does a database shortcut work?

The owner of the source database, the data provider, shares the database with the creator of the shortcut in Real-Time Analytics, the data consumer. The owner and the creator can be the same person.

The database shortcut is attached in read-only mode, making it possible to view and run queries on the data that was ingested into the source Azure Data Explorer database. The database shortcut synchronizes changes in the source database. Because of the synchronization, there's a data lag of a few seconds to a few minutes in data availability. The length of the time lag depends on the overall size of the source database metadata.

The source and database shortcuts use the same storage account to fetch the data. The storage is owned by the source database. The database shortcut views the data without needing to ingest it. Since the database shortcut is a read-only database, the data, tables, and policies in the database can't be modified except for caching policy, principals, and permissions.

Create database shortcut

A data consumer can create a database shortcut in Real-Time Analytics from any source database in Azure Data Explorer using an invitation link, or by using a cluster URI and database name. The data consumer can control how much data is cached by setting the cache policy. The main implications setting the hot cache policy are:

  • Cost: The cost of cold cache can be dramatically lower than of hot cache.
  • Performance: Data in hot cache is queried faster, particularly for range queries that scan large amounts of data.

Select the desired tab that corresponds with the way you'd like to create a shortcut.

Prerequisites

Important

Both the source database and the database shortcut in Real-Time Analytics must be in the same region, but can be in different tenants.

Important

This method works with sources both in Azure Data Explorer and in Real-Time Analytics.

To create a shortcut using a cluster URI and database name, make sure you have at least contributor permissions on the source data, and then follow these steps:

  1. Browse to your workspace in Microsoft Fabric.

  2. Open a new or existing event house in Real-Time Analytics.

  3. Select the plus sign next to KQL databases.

    Screenshot in event house of adding a new KQL database.

  4. Enter a name for your database shortcut.

  5. Select Type > New shortcut database (Follower)

    Screenshot of new database dialog for creating database shortcut in Real-Time Analytics.

  6. Select Next.

  7. Select Method > Cluster URI.

  8. Enter the URI of the source cluster. To find the URI of a KQL Database, see Copy URI.

  9. Specify the source Database.

  10. Optionally, modify the default cache policy.

    Screenshot of new database shortcut from a cluster URI dialog in Real-Time Analytics.

  11. Select Create.

Once the shortcut is created, you're taken to the database details view of the new database shortcut.

Screenshot of resulting database shortcut in Real-Time Analytics.

Delete database shortcut

  1. Within your workspace, find the KQL database shortcut you wish to delete.

  2. Select the More menu [...] > Delete.

    Screenshot of deleting item of database shortcut.

Your database shortcut has now been deleted. Once a database is deleted, it can't be recovered. You can, however, create a new database shortcut from the same source database.