Use the Query Builder to create SQL queries as shown below:
Note: The Insert, Update and Delete statements (performed by the DB query) may cause an auto-commit to the DB (based on the DB driver’s definition).
Select the DB object (Table, View or Synonym) from the DB Tree and proceed with one of the following actions:
To remove a DB object from the Main window, you can either click the DB object and press Delete on your keyboard, right-click the DB object > Remove, or click the x located at the top-right corner of the DB object.
Note: Such removal automatically updates the SQL statement in the Query Display pane.
The following default SQL syntax appears in the Query Display pane -
Select * from [Table Name];
Select [Table Name.] * from [Table Name];
Note: As you can see in the above image, the [Table Name.] before * is explicitly specified, which can be useful in JOIN statements to avoid ambiguity. However, it is not required in most cases unless dealing with multiple tables with overlapping column names.
To remove columns from a DB object, perform either one of the following actions:
To add a JOIN operator to the SQL query, perform the following:
Each SQL statement, which is combined by the UNION operator, has a Q icon in the Main window. Clicking the Q icon of each SQL statement opens it in the Main window, where you can add DB objects and link them to each other in order to edit the SQL statement in the SQL query.
This table is located underneath the Query Builder's Main window, and it enables editing the SQL query. Its selected columns hold the same information as the graphical map, yet in a tabular format.
The Enable Pre-Execution Commands checkbox (located in the Query Settings toolbar) enables running commands on the selected DB before running the SQL query. When this checkbox is checked, the Pre-Execution Commands window opens. Note that when running the Query Builder on a Fabric interface, you should run the [Get Instance] command in the Pre-Execution Commands window, as the SQL query must run on an LU Instance level.
The Max rows setting determines the maximum number of rows that the SQL query can return, with a default of 10,000, which can be modified as required.
You can create and edit an SQL statement by either selecting the desired action from the Interface Explorer menu tree, typing it manually, or seeking guidance from the built-in AI Assistant. The latter two options are used for more complex queries.
In the Query Builder, adding an SQL statement to the Query Editor (top pane) can be done either manually or using the Interface Explorer Tree (left pane).
To add an SQL statement through the Interface Explorer Tree, right-click the relevant table or specific table fields ensuring that only the chosen fields are included. The available statements include SELECT, INSERT, UPDATE and DELETE.
Note: The Query Builder tool can be opened through the Interface Explorer view (as explained above and as can be watched below) as well as a pop-up window in the LU Schema, Graphit and Broadway.
In the Query Builder pop-up window, you can hover over a table in the tree and click on the arrow that appears on its right. Once clicked, a SELECT statement from that table is added to the Query Editor.
While writing your SQL statement in the Query Editor (top pane), you can be guided by 2 assistants - AI Assistant and Code Completion Assistant.
You can use the built-in AI Assistant to create SQL statements by entering your desired statement in natural language for the AI Assistant. To activate the AI Assistant, install from the Exchange one of the AI extensions (such as OpenAI, Anthropic, Gemini) and create an AI Interface based on it. To use the AI Assistant:
Click on the AI icon () in the upper-right corner of the Query Editor.
This pane is then split into two side-by-side editors: On the left - the SQL Editor, whereas on the right - the natural language statements Editor.
Write your desired statement in the right-side editor.
Choose the relevant schemas that you would like the AI Assistant to look at, via the Schema Filter select list. This action aims to avoid an overburdening process. In case there is only a single schema DB, it is selected automatically.
In order to see the selected schema(s), you can simply hover over Selected Schemas without reopening the Schema Filter select list.
![]()
Click on the SQL ← Text
button.
The query will then be generated and will appear in the SQL Editor (on the left).
The AI Assistant's explanations of how the SQL statement was created can be viewed by clicking the question mark icon that then appears above the SQL Editor.
You can also activate the AI Assistant in the opposite direction, which would explain an existing SQL query in natural language. To do that, click on the SQL → Text
button.
When the AI Assistant is activated within a DB select function, such as in Broadway DB Query actors or Graphit nodes, the natural language statement is saved as a comment alongside the SQL statement.
While manually editing SQL statements, you can be assisted by the Code Completion Assistant, which provides code completion suggestions. These completion suggestions are intended for schemas, tables, column names of the current interface, as well as sets of basic SQL clauses.
To use it, press CTRL+SPACE, similar to code programming.
A select list then opens, allowing you to choose the relevant statement.
An icon appears to the left of each item in the select list, where:
The Code Completion Assistant can also help you when looking for the standard SQL commands, such as Select
, AND
, WHERE
. The icon that represents them is: .
Notes and Tips
- Clearing the whole Query Editor can be done by clicking on the Clear button.
- The Query Editor can hold and execute several queries. When clicking on the Execute button, all queries will be executed, one by one, where the Results pane will show the results of the last query.
- If the Query Editor contains several queries and you wish to run some of them, there is no need to delete the others. To execute specific commands, select them and then click on Execute.
- You can add Fabric commands to the Query Editor and they will also be executed.
- When fabric is the selected data source interface, set the top bar fields prior to executing the query.
Use the Query Builder to create SQL queries as shown below:
Note: The Insert, Update and Delete statements (performed by the DB query) may cause an auto-commit to the DB (based on the DB driver’s definition).
Select the DB object (Table, View or Synonym) from the DB Tree and proceed with one of the following actions:
To remove a DB object from the Main window, you can either click the DB object and press Delete on your keyboard, right-click the DB object > Remove, or click the x located at the top-right corner of the DB object.
Note: Such removal automatically updates the SQL statement in the Query Display pane.
The following default SQL syntax appears in the Query Display pane -
Select * from [Table Name];
Select [Table Name.] * from [Table Name];
Note: As you can see in the above image, the [Table Name.] before * is explicitly specified, which can be useful in JOIN statements to avoid ambiguity. However, it is not required in most cases unless dealing with multiple tables with overlapping column names.
To remove columns from a DB object, perform either one of the following actions:
To add a JOIN operator to the SQL query, perform the following:
Each SQL statement, which is combined by the UNION operator, has a Q icon in the Main window. Clicking the Q icon of each SQL statement opens it in the Main window, where you can add DB objects and link them to each other in order to edit the SQL statement in the SQL query.
This table is located underneath the Query Builder's Main window, and it enables editing the SQL query. Its selected columns hold the same information as the graphical map, yet in a tabular format.
The Enable Pre-Execution Commands checkbox (located in the Query Settings toolbar) enables running commands on the selected DB before running the SQL query. When this checkbox is checked, the Pre-Execution Commands window opens. Note that when running the Query Builder on a Fabric interface, you should run the [Get Instance] command in the Pre-Execution Commands window, as the SQL query must run on an LU Instance level.
The Max rows setting determines the maximum number of rows that the SQL query can return, with a default of 10,000, which can be modified as required.
You can create and edit an SQL statement by either selecting the desired action from the Interface Explorer menu tree, typing it manually, or seeking guidance from the built-in AI Assistant. The latter two options are used for more complex queries.
In the Query Builder, adding an SQL statement to the Query Editor (top pane) can be done either manually or using the Interface Explorer Tree (left pane).
To add an SQL statement through the Interface Explorer Tree, right-click the relevant table or specific table fields ensuring that only the chosen fields are included. The available statements include SELECT, INSERT, UPDATE and DELETE.
Note: The Query Builder tool can be opened through the Interface Explorer view (as explained above and as can be watched below) as well as a pop-up window in the LU Schema, Graphit and Broadway.
In the Query Builder pop-up window, you can hover over a table in the tree and click on the arrow that appears on its right. Once clicked, a SELECT statement from that table is added to the Query Editor.
While writing your SQL statement in the Query Editor (top pane), you can be guided by 2 assistants - AI Assistant and Code Completion Assistant.
You can use the built-in AI Assistant to create SQL statements by entering your desired statement in natural language for the AI Assistant. To activate the AI Assistant, install from the Exchange one of the AI extensions (such as OpenAI, Anthropic, Gemini) and create an AI Interface based on it. To use the AI Assistant:
Click on the AI icon () in the upper-right corner of the Query Editor.
This pane is then split into two side-by-side editors: On the left - the SQL Editor, whereas on the right - the natural language statements Editor.
Write your desired statement in the right-side editor.
Choose the relevant schemas that you would like the AI Assistant to look at, via the Schema Filter select list. This action aims to avoid an overburdening process. In case there is only a single schema DB, it is selected automatically.
In order to see the selected schema(s), you can simply hover over Selected Schemas without reopening the Schema Filter select list.
![]()
Click on the SQL ← Text
button.
The query will then be generated and will appear in the SQL Editor (on the left).
The AI Assistant's explanations of how the SQL statement was created can be viewed by clicking the question mark icon that then appears above the SQL Editor.
You can also activate the AI Assistant in the opposite direction, which would explain an existing SQL query in natural language. To do that, click on the SQL → Text
button.
When the AI Assistant is activated within a DB select function, such as in Broadway DB Query actors or Graphit nodes, the natural language statement is saved as a comment alongside the SQL statement.
While manually editing SQL statements, you can be assisted by the Code Completion Assistant, which provides code completion suggestions. These completion suggestions are intended for schemas, tables, column names of the current interface, as well as sets of basic SQL clauses.
To use it, press CTRL+SPACE, similar to code programming.
A select list then opens, allowing you to choose the relevant statement.
An icon appears to the left of each item in the select list, where:
The Code Completion Assistant can also help you when looking for the standard SQL commands, such as Select
, AND
, WHERE
. The icon that represents them is: .
Notes and Tips
- Clearing the whole Query Editor can be done by clicking on the Clear button.
- The Query Editor can hold and execute several queries. When clicking on the Execute button, all queries will be executed, one by one, where the Results pane will show the results of the last query.
- If the Query Editor contains several queries and you wish to run some of them, there is no need to delete the others. To execute specific commands, select them and then click on Execute.
- You can add Fabric commands to the Query Editor and they will also be executed.
- When fabric is the selected data source interface, set the top bar fields prior to executing the query.