You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/workshop/db2i/index.mdx
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -506,7 +506,9 @@ All schemas have the ability to filter objects in a schema to find something spe
506
506
507
507
### Intro
508
508
509
-
Visual Explain is.....
509
+
Visual Explain is an essential tool for anyone who wants to use SQL Query Engine (SQE) insight to understand the performance characteristics of their SQL.
510
+
Visual Explain is often referred to as VE. SQE, as a cost-based optimizer, considers many factors before settling on the "plan" for query implementation.
511
+
By using VE during development and unit tests, IBM i application developers can gain crucial performance insights, and tune their SQL prior to promotion.
510
512
511
513
<Asidetype="note">
512
514
For this section, we are using the sample database. If you're doing this workshop as part of a lab, the sample data will be created for you automatically. You can use `qsys.create_sql_sample` to create the same sample data if you are using your own system.
@@ -563,7 +565,7 @@ If we love the advice SQE is showing us, we can click on the ‘Generate SQL for
563
565
<CardGrid>
564
566
<Card>
565
567
566
-
We might want to revise the index name before executing, if we indeed decide to establish the index.
568
+
We might want to revise the index name before executing if we indeed decide to establish the index.
567
569
568
570
</Card><Card>
569
571
@@ -598,7 +600,7 @@ To see the full VE details, click on ‘Display details’.
598
600
599
601
Use the Command+Option+f key sequence to cause the VE search bar to magically appear.
600
602
601
-
Type in goal to find all occurrences of of “goal” within the VE detail. The SQL optimization goal is one of many interesting tidbits to be found within VE detail.
603
+
Type in goal to find all occurrences of “goal” within the VE detail. The SQL optimization goal is one of many interesting tidbits to be found within VE detail.
602
604
603
605
</Card><Card>
604
606
@@ -636,7 +638,7 @@ As mentioned in the part before, all nodes can be hover on for more detail. When
636
638
637
639
<br />
638
640
639
-
It is possible to configure which nodes will be highlighted in the Explain results. As depicted in the screenshot below, click the ⚙️ (cog/settings) in the Visual Explain view. This will open a new tab with settings, where options can be toggled which control which nodes will be highlighted.
641
+
It is possible to configure which nodes will be highlighted in the Explain results. As depicted in the screenshot below, click the ⚙️ (cog/settings) in the Visual Explain view. This will open a new tab with settings, where options can be toggled which controls which nodes will be highlighted.
640
642
641
643
</Card><Card>
642
644
@@ -781,7 +783,7 @@ SET SYSIBMADM.SELFCODES = '*ALL';
781
783
782
784
Notebooks are documents that contain a mix of rich Markdown, executable code snippets, and accompanying rich output. These are all separated into distinct cells and can be interleaved in any order. They are great storytelling devices, allowing you to interleave Markdown elements like images, math equations, and explanatory text with your code. Notebooks can be a perfect way to share and explain your ideas with coworkers or the public community.
783
785
784
-
Notebooks support executing SQL statements and rendering tables, CL results and charts from Db2 for IBM i data directly in cell results.
786
+
Notebooks support executing SQL statements and rendering tables, CL results, and charts from Db2 for IBM i data directly in cell results.
785
787
786
788
Checkout [this Visual Studio Code blog](https://code.visualstudio.com/blogs/2021/11/08/custom-notebooks) for more information Notebook support.
787
789
@@ -803,7 +805,7 @@ Above and below all cells will be two buttons to either:
803
805
* Add a code cell, or
804
806
* Add a markdown cell.
805
807
806
-
Each cell has a language asscoiated with it, which determines how the cell will be executed.
808
+
Each cell has a language associated with it, which determines how the cell will be executed.
807
809
808
810
</Card><Card>
809
811
@@ -816,7 +818,7 @@ Each cell has a language asscoiated with it, which determines how the cell will
816
818
<CardGrid>
817
819
<Card>
818
820
819
-
Based on the language tagged in the cell determines how the cell will be executed and result will be rendered. By default, when using SQL, a table will be produced. Other types include CL and markdown.
821
+
Based on the language tag in the cell determines how the cell will be executed and result will be rendered. By default, when using SQL, a table will be produced. Other types include CL and markdown.
820
822
821
823
On each cell is a ▶️ (play) button which will execute the cell, or you can use the keyboard shortcut Control+Enter. SQL statements will get executed in the selected job inside of the SQL Job Manager.
822
824
@@ -926,4 +928,4 @@ Under the ▶️ (play) button is 'Open as Notebook'. Selecting that will open t
0 commit comments