A Fine Slice Of SQL Server
Robert Cain follows up on a prior post:
In the conclusion of my last post, Fun With KQL – Datatable, I mentioned a
datatablecan also be useful when you need to do special calculations. I decided it really needed further explanation and created this post to dive in a bit deeper.If you haven’t read my
datatablepost yet, you should as I’ll refer back to it. Go ahead, I’ll wait.
Click through to see what Robert has in mind.
Comments closedRobert Cain continues a series on KQL:
As you’ve seen with the
joinin my Fun With KQL – Join post it can be useful to combine two tables in order to clarify the output. What if, though, you need data that isn’t in an existing table?That’s where the
datatableoperator comes into use. Thedatatableallows you to create a table of data right within the query. We’ll see a few useful examples in this post.
Read on to see how you can create one and what you can do with it.
Comments closedGuy Reginiano notes an update:
A new generation of cache recommendations for Azure Data Explorer is now available in the Azure portal!
This update introduces significant improvements, including enhanced logic, additional statistics for end users, an improved user interface, and a streamlined process for reviewing and applying recommendations. In this blog post, we will explore the new features and benefits offered by this latest update.
Read on to see where you can find these cache recommendations, as well as the types of recommendations you’re liable to receive.
Comments closedRobert Cain keeps bringing things together:
In my previous post, Fun With KQL – Union I covered how to use the
unionoperator to merge two tables or datasets together. Theunionhas a few helpful modifiers, which I’ll cover in this post.
Robert has some good examples, including one for IsFuzzy.
Robert Cain combines some tables:
In today’s post we will look at the
unionoperator. Aunionwill create a result set that combines data from two or more tables into a single result set.Unlike the
join, which was covered in my previous post Fun With KQL – Join, theuniondoes not combine the columns from each table into single rows. Rather it returns rows from the first table, then rows from the second table, then if supplied third, forth and so on.
Read on to see how union works as an operator and for several examples.
Robert Cain picks back up on a series:
I’m still working on my ArcaneBooks project, mostly documentation, so I thought I’d take a quick break and go back to a few posts on KQL (Kusto Query Language). In this post we’ll cover the
joinoperator.A
joinin KQL operates much as it does in SQL. It will join two datasets together into a single result.
Even so, there’s a little more to joins in KQL than in T-SQL, with innerunique being unique to KQL. The closest T-SQL analog would probably be a CROSS APPLY (SELECT TOP(1) ...) operation. KQL also uses join to combine the concepts of EXISTS and NOT EXISTS in SQL.
Chris Webb has had a busy month:
Maybe the fourth- or fifth-most exciting Power BI-related announcement last month (admittedly it was an exciting month) was that Log Analytics for Power BI datasets is now GA and you can now link multiple Power BI workspaces to a single Log Analytics workspace. This, for me, means that enabling Log Analytics has gone from being useful to essential for anyone interested in monitoring Analysis Services engine activity in an enterprise Power BI/Fabric deployment. It also works with Direct Lake datasets too!
Read on for a few KQL queries which allow you to get pertinent information from your Log Analytics workspace.
Comments closedDany Hoter looks at some KQL query plans:
Each visual on the page is going to summarize data from one or more queries and add the summarize part of the query.
If your model contains multiple tables in direct query with relations between them, the connector will generate joins between the tables.
Selecting values in filters will create multiple where conditions.
In order to see the final query and understand the performance implications of each query and the total query load created by a report, you need to use the command “.show queries” in the context of the database.
Click through for Dany’s notes on the topic, including a few tips on what to look for.
Comments closedAll of the above abilities are great additions to the Fabric service. But whats even more exciting is the new magic in Jupyter Notebooks. Yes, you read it right – we can now write KQL language in our Notebooks with the use of the new magic command “%kql”.
Click through for a quick demonstration of how it all works.
Comments closedAnshul Sharma announces season 2 to a great program:
Greetings, esteemed investigators and data enthusiasts! We are thrilled to announce the highly anticipated launch of Kusto Detective Agency Season 2. After the immense success of Season 1, with over 10,000 participants diving deep into the world of data investigation, we cannot thank you enough for your incredible support and enthusiasm!
Season 2 of Kusto Detective Agency is set to be an even grander adventure, filled with more challenges, mind-bending mysteries, and countless opportunities to showcase your analytical skills. Prepare yourself for a journey that will push the boundaries of your data prowess and reward you with an unforgettable experience.
I just finished season 1 yesterday and saw the link to season 2, but didn’t touch it yet. If you’re learning the Kusto Query Language, this is a series of challenges which will really push your skills. As I was going through season 1, there were several times when I’d say “I know exactly how to answer this in T-SQL but how do I answer it in KQL?” If your KQL skills aren’t great, there are plenty of people who have shown their answers online as well, so you can walk through it with them.
Admittedly, I want more Poppy the goldfish lore. The twist in challenge 5 was not something I’d expected.
Comments closed