A Fine Slice Of SQL Server
Robert Cain continues a series on KQL:
Performing DateTime arithmetic in Kusto is very easy. You simply take one DateTime data type object and apply standard math to it, such as addition, subtraction, and more. In this post we’ll see some examples of the most common DateTime arithmetic done when authoring KQL.
Read on for several examples of how it all works.
Comments closedRobert Cain continues a series on KQL:
The previous post in this series Fun With KQL – Extract, showed how we can use the
extractoperator to pull part of a string using regular expressions. I think you’d agree though, using regular expressions can be a bit tricky.If you have a string that is well formatted with recurring text you can count on, and want to pull one or more strings from it into their own columns, Kusto provides a much easier to use operator:
parse.
Robert includes a series of examples, including examples of things you cannot do.
Comments closedDany Hoter views data in Excel:
In a previous article Direct Query from Excel to Azure Data Explorer (microsoft.com) I described a way to mimic Direct Query access ala Power BI in Excel.
The method used in this article that allows the user to filter the imported data using values entered into cells in the grid.
In this article I would like to describe a way to really query Kusto data in real time without importing any data and without any volume limitations.
Read on to see how, though there’s a pretty big intermediate step.
Comments closedRobert Cain continues a series on KQL:
Almost all languages have the ability to extract part of a string. In C#, this is the
Substringmethod of a string. With SQL, it is theSUBSTRINGcommand.Kusto has an operator that will perform this same task, it is called
extract. In this post we’ll see some examples of using it.
Click through to see how extract works.
Robert Cain continues a series on KQL:
Like most query languages, the Kusto Query Language as the ability to sort the output. It works almost, but not quite, like you expect. So let’s take a look at the KQL
sortoperator.
Read on to get the general idea but also some of the nuance behind this operator.
Comments closedRobert Cain continues a series on learning the Kusto Query Language:
The
agofunction is very similar to thenowfunction, which was discussed in my previous post Fun With KQL – Now. In this article we’ll take a look atago, see how it works and how it differs fromnow.We’ll be using both the
nowfunction in this post, so if you aren’t familiar with them please go read my articles Fun With KQL – Print and Fun With KQL – Now.
Click through for proper use of ago().
Robert Cain doesn’t have time to wait:
What time is it? That’s what the KQL function
nowwill tell you. It will return the current date and time. It is mostly used in queries where you need data relative to the current date and time.
Read on to see how you can use it, including with offset intervals.
Comments closedMichal Bar has a few updates to the Azure Data Explorer web tool:
We are focused on continuously improving the results exploration experience in ADX web UI, to make it easy and intuitive. Our goal is to provide an easy-to-use UI so that you will not be required to re-write KQL queries in order to perform light-weight data exploration.
Click through to see how you can search and filter within the results pane (something I’d like to see in other Microsoft data platform tools like SSMS), create series panels on charts from KQL, and more.
Comments closedRobert Cain continues a series on KQL:
In this post we’ll cover the
The samples in this post will be run inside the LogAnalytics demo site found at https://aka.ms/LADemo. This demo site has been provided by Microsoft and can be used to learn the Kusto Query Language at no cost to you.
Importantly, this is an operator and not a statement. This is in contrast to languages like T-SQL.
Comments closedEvery visual shown in a report in PBI, contains some form of aggregation
The question is how the aggregations are calculated and at which step in the pipe of bringing the data from the data source to the report.
In this article, I’ll be using data coming from Azure Data Explorer aka Kusto aka ADX.
Most of the content is relevant for other sources as well.
Read on for the advice, which I’d call fairly unexpected—I actually expected the recommendation to go the other way for performance reasons.
Comments closed