Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
A database shortcut in Real-Time Intelligence is an embedded reference within a KQL database to a source database. The source database can be one of the following types:
- A KQL Database in Real-Time Intelligence
- An Azure Data Explorer database
The behavior of 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 Intelligence, 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. You can also use a database shortcut 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 Intelligence, the data consumer. The owner and the creator can be the same person.
The database shortcut connects in read-only mode, so you can view and run queries on the data that the source Azure Data Explorer database ingested. 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 source database owns the storage. The database shortcut views the data without needing to ingest it. Since the database shortcut is a read-only database, you can't modify the data, tables, and policies in the database except for caching policy, principals, and permissions.
Create database shortcut
A data consumer can create a database shortcut in Real-Time Intelligence from any source database in Azure Data Explorer by 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 of setting the hot cache policy are:
- Cost: The cost of cold cache can be dramatically lower than the cost of hot cache.
- Performance: Data in hot cache is queried faster, particularly for range queries that scan large amounts of data.
Important
The database shortcut setup requires a high level of trust between the involved parties, such as the leader database and the database shortcut (follower). You can establish the database shortcut even if the leader cluster is behind a virtual network (VNet) or has public access disabled. Ensure that you thoroughly review and accept the security posture of this setup.
Select the tab that corresponds with the way you'd like to create a shortcut.
Prerequisites
- A workspace with a Microsoft Fabric-enabled capacity.
- A source database. This database can be an Azure Data Explorer database or a KQL Database.
- An eventhouse.
Important
Both the source database and the database shortcut in Real-Time Intelligence must be in the same region, but they can be in different tenants.
Important
This method works with sources both in Azure Data Explorer and in Real-Time Intelligence.
Create a shortcut with a cluster URI
To create a shortcut by using a cluster URI and database name, make sure you have at least contributor permissions on the source data, and then follow these steps:
Browse to your workspace in Microsoft Fabric.
Open a new or existing eventhouse in Real-Time Intelligence.
Select the plus sign next to KQL databases.
Enter a name for your database shortcut.
Select Type > New shortcut database (Follower).
Select Next.
Select Method > Cluster URI.
Enter the URI of the source cluster. To find the URI of a KQL Database, see Copy URI.
Specify the source Database.
Optionally, modify the default cache policy.
Select Create.