![]() ![]() Number of rows - number of rows produced. Produces a part of the input sequence after sorting, typically a result of an ORDER BY. Sort keys - expression defining the sorting order. Window Functions - list of window functions computed. Grouping Key Sets - list of grouping setsĪggregate Functions - list of functions computed for each group, e.g. Represents constructs such as GROUPING SETS, ROLLUP and CUBE. Grouping Keys - if GROUP BY is used, this lists the expressions we group by.Īggregate Functions - list of functions computed for each aggregate group, e.g. ![]() Can represent SQL constructs such as GROUP BY, as well as SELECT DISTINCT. Groups input and computes aggregate functions. Non-equality join predicates might result in significantly slower processing speeds and should be avoided if possible. Object Name - the name or type of the accessed object. an Information Schema table or the result of a previous query). Represents access to an internal data object (e.g. Stage name - the name of the stage where the data is read from. Can be a part of queries that scan data from stages directly, but also for data-loading COPY queries. Represents access to data stored in stage objects. TimeLimit - provided timeLimit parameter. Generates records using the TABLE(GENERATOR(.)) construct. Number of values - the number of produced values. List of values provided with the VALUES clause. Table alias - used table alias, if presentĮxtracted Variant paths - list of paths extracted from VARIANT columns Attributes:įull table name - the name of the accessed table, including database and schema. 41.95M from Join to Aggregate ).ĭata Access and Generation Operators ¶ TableScan Each link provides the number of records that were processed (e.g. Links represent the data flowing between each operator node. ![]() Operator-specific additional information (e.g. The operator node, allowing for easy visual identification of performance-critical operators. This information is also reflected in the orange bar at the bottom of Percentageįraction of time that this operator consumed within the query step (e.g. Aggregate and Join in the screenshot above).įor descriptions of all the types, see Operator Types below. ID can be used to uniquely identify an operator within a query profile (e.g. They are responsible for different aspects of data management and processing, including data access, transformations and updates.Įach operator node in the tree includes some basic attributes: Operators are the functional building blocks of a query. The tree provides a graphical representation of the operator nodes that comprise a query and the links that connect each operator: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |