Below is a list of available functions within the SQL Scanner window.
| Button or Menu | Function | 
| Group & Right-click Menu 
 | |
| Group & Right-click Menu | |
| Group Menu | |
| Group Menu | |
| Group Menu | |
| Group Menu | |
| Group Menu 
 | |
| Job Menu 
 | |
| Job Menu | |
| Job Menu | |
| SQL & Right-click Menu | |
| SQL & Right-click Menu | |
| SQL & Right-click Menu | |
| SQL Menu 
 | |
| SQL Menu | |
| SQL Menu | |
| Report Menu | |
| Report Menu | |
| Navigate Menu 
 | |
| Navigate Menu | |
| View Menu | |
| View Menu | |
| View Menu | |
| View Menu | |
| View Menu | |
| View Menu | |
| View Menu | |
| Edit Menu 
 | |
| Edit Menu 
 | |
| Edit Menu 
 | |
| File Menu | |
| Right-click Menu | |
| Right-click Menu | |
| Right-click Menu | |
| Right-click Menu | |
| Right-click Menu | View (Large Icons/ Small Icons/ List/ Details) | 
| Right-click Menu | |
| Right-click Menu | |
| Right-click Menu | |
| Right-click Menu | Save | 
| Right-click Menu | 
In order to render the SQL statement as a valid standalone SQL a number of conversions maybe applied to the SQL statement.
Note: If a conversion is applied, it may be necessary to reverse the changes after optimization when an alternative SQL is pasted back to the original source code.
During a trigger operation, two logical tables store deleted and inserted records. The deleted and inserted logical tables cannot be referenced outside the trigger body. Therefore to be able to optimize a SQL statement used in a trigger two temporary tables are used to simulate the inserted and deleted tables.
For example:
INSERT INTO EMP_SMALL (EMP_ID,
EMP_NAME,
EMP_SALARY)
SELECT A.EMP_ID,
A.EMP_NAME,
B.EMP_SALARY
FROM EMPLOYEE A,
Inserted B
WHERE A.EMP_ID = B.EMP_ID
SELECT *
INTO #inserted_simulation_table
FROM dbo.EMPLOYEE
WHERE 1 = 2
INSERT INTO EMP_SMALL (EMP_ID,
EMP_NAME,
EMP_SALARY)
SELECT A.EMP_ID,
A.EMP_NAME,
B.EMP_SALARY
FROM EMPLOYEE A,
#inserted_simulation_table B
WHERE A.EMP_ID = B.EMP_ID