kql database
75 TopicsFabric Eventhouse: Capacity policy for .ingest inline is hard-capped at 1 concurrent operation
Problem When using the KQL Activity in Fabric Data Pipelines to execute .ingest inline commands against an Eventhouse KQL database, the effective ingestion capacity is always 1 concurrent operation — regardless of the Fabric capacity SKU (tested on F2 and F8) and regardless of the cluster capacity policy setting. Running .alter-merge cluster policy capacity with ClusterMaximumConcurrentOperations: 16 succeeds without error, but .show capacity still reports an effective ingestion capacity of 1. Any pipeline pattern that executes .ingest inline within a parallel ForEach immediately hits 429 TooManyRequests / ControlCommandThrottledException errors. Highlighting that the capacity is 1. This makes the KQL Activity (KustoQueryLanguage type) unusable for parallel ingestion scenarios — which is an important use case in data pipelines (logging, event emission, watermark updates during parallel table processing). Question / Request Do you recognize this issue? if so I have the below request: Increase the effective ingestion capacity for Fabric Eventhouse to match what the capacity policy allows (respect ClusterMaximumConcurrentOperations)Solved434Views0likes11CommentsHow to fix a Bad shortcut name
Hi, I have (had) a shortcut in may KQL Database called "terminals". The shortcut was pointing to the wrong lakehouse, so I had to drop it and create again. However, every time I create it again it adds a counter to the shortcut name: "_1", "_2" and so on. It doesn't matter if the previous shortcut was already dropped, it stills add a counter. How can I fix this problem? If I wait between dropping the original shortcut and creating the new one, woult it solve the problem ? I already tried waiting, but it didn't work. I imagine it may be a matter of how long I need to wait - how long? Is there any other way to solve this? Kind Regards, Dennes4KViews1like6CommentsCopilot for EventHouse Queryset
Hi, RTI has introduced the preview feature of Copilot for the Eventhouse Queryset, but is there any way to automate the Copilot usage, via API endpoint or SDKs? The idea is to programmatically generate relevant and meaningful Kusto queries for business insights, from the tables and datasets present in the KQL DB in Eventhouse using Copilot. Thanks in advance!6.7KViews1like7CommentsFrom Rain Drops to Playability: Scoring Real-Time Weather Insights for FIFA World Cup 2026⚽
In this blog, I will walk you through how we can support the FIFA World Cup 2026 by organizing teams and players by delivering real-time, actionable weather insights. By predicting critical weather patterns - such as high humidity, extreme heat, and sudden rainfall - teams can proactively adjust their game-day strategies, and organizers can ensure optimal player safety. To bring this vision to life, we will build a comprehensive, real-time weather monitoring dashboard covering all 16 FIFA World Cup stadiums, powered entirely by the real-time analytics capabilities of Microsoft FabricDelay in Onelake Shortcut from Eventhouse to Lakehouse
I have a table in a KQL Database in an eventhouse that is hooked up to an Azure Eventhub. I have turned on One Lake storage for this table and added a shortcut to the lakehouse for this table. The table receives around 10-15k events per day and I have set the retention policy for the table to 30 days. The eventhouse table data was updating and getting reflected in the shortcut table within a few minutes when I first set it up. But now it takes almost an hour or more to see the latest event data in the shortcut table in my lakehouse. I turned the one lake availability off and then on again, and also tried updating the table policies but nothing seems to workSolved242Views1like4CommentsEventhouse vs Lakehouse - When to Use Which in Microsoft Fabric?
Microsoft Fabric offers multiple storage and analytical engines. This blog helps you make the right architectural choice early on and save them massive migration efforts later. In this blog, I’ll walk you through the differences between these two powerhouses, look at real-world challenges, map out concrete scenarios, and give you a definitive comparison framework so you can choose the right tool for the job.BCDR support for Fabric Eventhouse (KQL DB) – cross-region data replication and failover
Hi team, A few quick questions regarding BCDR options for Fabric Eventhouse (KQL): Does Fabric Eventhouse provide built-in cross-region redundancy/failover in case of regional outages? If yes, what is required to implement this, and what does the cost model look like? Does Fabric support native data replication/ copy capabilities? Specifically, is there support (or a roadmap) for: Azure Data Explorer (ADX/Kusto) → Fabric Eventhouse (KQL DB) Fabric Eventhouse (KQL DB) → Fabric Eventhouse (KQL DB) across regions (e.g., westcentralus ↔ westus) Could you please share any relevant documentation, known limitations, or guidance for these scenarios? Thanks in advance for your help!Solved1.4KViews2likes3CommentsDataFlow Gen 2 with KQL Engine Query URI as the destination
I'm trying to implement the Content Delivery Lifecycle using workspace Git integration- see https://learn.microsoft.com/en-us/fabric/cicd/git-integration/intro-to-git-integration I need the destination of my Data Flow to automatically pick up the right KQL Engine instance + connection, here: I can make it pick up the cluster URI from a library variable as show above. However, the problem that I have is that the connection name does not populate (also shown above). When I run the Data Flow (in this state) I get the error below:Solved1.4KViews0likes7Comments