diff --git a/data-explorer/kusto/query/assessment.md b/data-explorer/kusto/query/assessment.md index 472c0d4a1a..875571652f 100644 --- a/data-explorer/kusto/query/assessment.md +++ b/data-explorer/kusto/query/assessment.md @@ -12,6 +12,8 @@ You can query different kinds of data. The language is expressive, easy to read This article provides an explanation of the query language and offers practical exercises to get you started writing queries. To access the query environment, use the [Azure Data Explorer web UI](https://dataexplorer.azure.com/). To learn how to use KQL, see [Tutorial: Learn common operators](tutorials/learn-common-operators.md). +The most common kind of query statement is a tabular expression **statement**, which means both its input and output consist of tables or tabular datasets. Tabular statements contain zero or more **operators**, each of which starts with a tabular input and returns a tabular output. Operators are sequenced by a `|` (pipe). Data flows, or is piped, from one operator to the next. The data is filtered or manipulated at each step and then fed into the following step. + A Kusto query is a read-only request to process data and return results. The request is stated in plain text, using a data-flow model that is easy to read, author, and automate. Kusto queries are made of one or more query statements. There are two kinds of user [query statements](statements.md): @@ -24,11 +26,10 @@ All query statements are separated by a `;` (semicolon), and only affect the que For information about application query statements, see [Application query statements](statements.md#application-query-statements). -The most common kind of query statement is a tabular expression **statement**, which means both its input and output consist of tables or tabular datasets. Tabular statements contain zero or more **operators**, each of which starts with a tabular input and returns a tabular output. Operators are sequenced by a `|` (pipe). Data flows, or is piped, from one operator to the next. The data is filtered or manipulated at each step and then fed into the following step. It's like a funnel, where you start out with an an entire data table. Each time the data passes through another operator, it's filtered, rearranged, or summarized. Because the piping of information from one operator to another is sequential, the query operator order is important, and can affect both results and performance. At the end of the funnel, you're left with a refined output. -Why don't you see an example query. +Why don't you see an example query. > [!div class="nextstepaction"] > Run the query @@ -44,17 +45,17 @@ StormEvents |-----| | 28| -Did you know, KQL is case-sensitive for everything – table names, table column names, operators, functions, and so on. +Did you no, KQL is case-sensitive for everything – table names, table column names, operators, functions, and so on. This query has a single tabular expression statement. The statement begins with a reference to a table called *StormEvents* and contains several operators, [`where`](where-operator.md) and [`count`](count-operator.md), each separated by a pipe. The data rows for the source table are filtered by the value of the *StartTime* column and then filtered by the value of the *State* column. In the last line, the query returns a table with a single column and a single row containing the count of the remaining rows. -In contrast to Kusto queries, [Management commands](../management/index.md) are requests to Kusto to process or modify data or metadata. For example, the following management command creates a new Kusto table with two columns, `Level` and `Number`: +In contrast to Kusto queries, [Management commands](../management/index.md) are requests to Kusto to process or modify data or metadata. For example, the following management command creates a new Kusto table with two columns, `Level` and `Number`: ```kusto .create table Logs (Level:string, Text:string) ``` -Management commands have their own syntax, which isn't part of the Kusto Query Language syntax, although the two share many concepts. In particular, management commands are distinguished from queries by having the first character in the text of the command be the dot (`.`) character (which can't start a query). Why do we do it like this? This distinction prevents many kinds of security attacks, simply because it prevents embedding management commands inside queries. +Management commands have their own syntax, which isn't part of the Kusto Query Language syntax, although the two share many concepts. In particular, management comands are distinguished from queries by having the first character in the text of the command be the dot (`.`) character (which can't start a query). Why do we do it like this? This distinction prevents many kinds of security attacks, simply because it prevents embedding management commands inside queries. Not all management commands modify data or metadata. The large class of commands that start with `.show`, are used to display metadata or data. For example, the `.show tables` command returns a list of all tables in the current database. @@ -70,9 +71,9 @@ KQL is used by many other Microsoft services. For specific information on the us [Proactively hunt for threats with advanced hunting in Microsoft 365 Defender](/microsoft-365/security/defender/advanced-hunting-overview) [CMPivot queries](/mem/configmgr/core/servers/manage/cmpivot-overview#queries) -## Related content +## Related stuff -* [Tutorial: Learn common operators](tutorials/learn-common-operators.md) +* [Tytorial: Learn common operators](tutorials/learn-common-operators.md) * [Tutorial: Use aggregation functions](tutorials/use-aggregation-functions.md) * [KQL quick reference](kql-quick-reference.md) * [SQL to Kusto Query Language cheat sheet](sql-cheat-sheet.md)