A Fine Slice Of SQL Server
Michal Bar has an update for us:
Welcome to the July 2024 update. We are excited to announce new features and improvements in ADX web UI.
Continue reading to learn more about:
- Copy query with syntax coloring and KQL IntelliSense improvements
- Ad-hoc visual data exploration
- Dashboards real time refresh rate
- Enhanced data interaction for dashboard tiles
- Resize and move dashboard tiles using keyboard only
Click through to continue reading.
Comments closedHauke Mallow shares what is probably a bad idea:
Kusto is a fast and scalable database designed to ingest, store, and analyze large volumes of structured and semi-structured data. For non-structured data like images, Azure Storage is typically the best choice. Databases can reference image data on storage via a URL, meaning images are not directly stored in Kusto. However, there are scenarios where storing image data in Kusto is beneficial. In this blog post, we will explore when it makes sense to store images in Kusto, how to store them, and how to visualize this data using Azure Data Explorer dashboards or Power BI.
I suppose the main benefit would be displaying images in Azure Data Explorer, as that tool might not support loading in external images from a storage account or other sane location. But this feels more like a neat parlor trick than something I’d actively recommend.
Comments closedChris Webb digs into the numbers:
In the past I have blogged about how important the number of connections from a Power BI DirectQuery semantic model to a data source is for performance. It’s also true that in some cases opening a connection, or some of the operations associated with opening a connection, can be very slow. As a result it can be useful to see when your semantic model opens connections to a data source, and you can do this with Log Analytics.
Click through to see how you can do this and some of the information it provides.
Comments closedDennes Torres gets around a limitation:
Real-Time dashboards are a great feature in Real Time Intelligence experience to monitor our data. However, by default it’s made to work only with Kusto Databases. The options to create a real time dashboard or to define its data source only accept Kusto Databases.
What if we would like to see in real time the information we have in a lakehouse as well? Let’s discover a solution for this.
Read on for the solution.
Comments closedMichal Bar introduces a new feature:
We are excited to introduce the new Data Exploration feature, designed to enhance your ability to delve deeper into the data presented on any Dashboard.
If the information you’re seeking isn’t readily available on the dashboard, this feature allows you to extend your exploration beyond the data displayed in the tiles, potentially uncovering new insights.
Directly from a dashboard, you can refine your exploration using a user-friendly, form-like interface. This intuitive and dynamic experience is tailored for insights explorers seeking insights based on high volumes of data in near real time.
Click through to see the new feature in action.
Comments closedDennes Torres takes a peek at a service with a new name:
When everyone starts to announce Real-Time Intelligence in Microsoft Fabric as something new, I need to double check what’s happening: Am I crazy or is everyone else? Wasn’t this already there?
Finally, I realize that Real-Time Intelligence is a new name for Real-Time Analytics, and they are doing this so fast we don’t even have time to notice the difference.
What’s Real-Time Intelligence and what’s the difference from Real-Time Analytics?
Read on for those answers.
Comments closedVincent-Philippe Lauzon has an announcement:
Kusto databases, either in Fabric (KQL Database) or in Azure (Azure Data Explorer), are optimized for append ingestion.
In recent years, we’ve introduced the .delete command, allowing you to selectively delete records.
In February, we introduced the .update command in public preview. This command allows you to update records by deleting existing records and appending new ones in a single transaction.
Today, the .update is Generally Available (GA)!
Click through for more details, including a link to the documentation, where you can see several examples of the syntax.
Comments closedVincent-Philippe Lauzon shows off a feature now in public preview:
Kusto databases, either in Azure Data Explorer or in Fabric KQL Database, are optimize for append ingestion.
In recent years, we’ve introduce the .delete command allowing you to selectively delete records.
Today we are introducing the .update command. This command allows you to update records by deleting existing records and appending new ones in a single transaction.
This command comes with two syntaxes, a simplified syntax covering most scenarios efficiently and an expanded syntax giving you the maximum of control.
Read on for more information and a pair of examples of how updating works.
Comments closedJosephine Bush tracks what’s happening on that Azure SQL Database:
According to Microsoft, “Kusto Query Language (KQL) is a powerful tool to explore your data and discover patterns, identify anomalies and outliers, create statistical modeling, and more. The query uses schema entities that are organized in a hierarchy similar to SQLs: databases, tables, and columns.”
Note: KQL is case-sensitive for everything. Also, remember to refrain from querying everything just like you wouldn’t with SQL — don’t do the equivalent of SELECT * from gianttable.
Microsoft also has a lot of documentation with best practices and a quick reference guide to the Kusto commands. This blog post covers the ones I use the most.
Read on for a primer on the language, specifically some of the things you can do when reading Azure SQL Database audit information.
Comments closedBrian Bønk gets in on the Microsoft Fabric fun:
Microsoft has released the final piece of the current puzzle around the OneLake as a one-stop-shopping service for dat in Fabric. Until now we had only access to the KQL data in the KQL database.
With this addition, we can now finally say that OneLake is the one place for your data in Fabric.
Read on to see how you can make data in an existing KQL database usable in OneLake.
Comments closed