Scan SQL
SQL Scanner extracts SQL statements embedded in database objects, captured from SQL Profiler, or stored in application source code and binary files. Use the Add Scanner Jobs wizard to create scan jobs using statements from any of these sources.
To create a scan job
- Select the Scan SQL tab in the main window.
-
Click Add Scanner Job from the Welcome pane.
Tip: You can navigate directly to the embedded SQL statement for a particular format by clicking one of the links from the Welcome pane.
-
Select a connection to use for the scan job. Review the following for additional information:
Select Connection Description Connection
Click
to select a previously created connection.
Tip: Click
to open the Connection Manager to create a new connection. See Connect to SQL Server for more information.
Select Database and User Description Database
Click Set User
Click -
Select the page for the type of statement you want to add to the scan job. Review the following for additional information:
Database Objects Page Description Database Objects
Select a database object and click
to add the object to scan.
Tip: Click
SQL Profiler Page Description Available trace files/table
Click Database
Click Set User
Click Source Code Page Description Source code type
Select Text/Binary files or COBOL programming source code to indicate the source code type. Add by file
Click and browse to the files you want to scan.
Add by directory
Click
Note: Select the Include Sub-directory checkbox to scan sub-directories.
Connection for scanning
Select the database and user name settings. Note: SQL Scanner helps you manage scan jobs by organizing them into groups. Use the Group Information page to create a new group or to add the current scan job to an existing group.
-
Select the Group for the scan job you created in the Scanner node of the Task pane once SQL Scanner finishes scanning.
-
Select the scan job in the Group node.
-
Identify problematic SQL statements in the SQL List pane. See View SQL Classification for more information.
-
Select SQL statements to send to SQL Optimizer for optimization. See Send to Optimize SQL for more information.
Filter Database Objects
To filter a database object
-
Click
-
Review the following for additional information:
Database Click Schema Click Object Type Click Filter Enter the filtering criteria using the % wildcard and click
.
Important: The filtering criteria is case sensitive so you must match the uppercase or lowercase characters of the database object name.
Notes:
- The % is used to represent multiple characters.
- Select the Exclude filter checkbox to exclude database objects that meet the filtering criteria instead of including them.
-
Select the database objects to add to your scan job.
Scan Source Code with Temp Tables
SQL Scanner looks for CREATE TABLE, SELECT INTO, or other SQL statements that create and modify temporary tables when scanning source code that uses temporary tables. Once SQL Scanner locates these statements, it automatically creates or modifies the temporary tables if you selected the Create Scanner Temp Table checkbox in the Scanner Options page. SQL Scanner automatically drops the temporary tables after scanning the source code.
Review the following for additional information:
Source Code
select EMP_ID,
EMP_NAME
into #a
from EMPLOYEE
select *
from #a
Extracted SQL displayed in the SQL Text pane
SQL1:
select EMP_ID,
EMP_NAME
into #a
from EMPLOYEE
SQL2:
select *
from #a
SQL Scanner displays the DDL for creating the temporary tables in the Temp Table tab of the SQL Information pane. This includes the DDL found by SQL Scanner or the DDL used to create the user-defined temporary table.
select EMP_ID,
EMP_NAME
into #a
from EMPLOYEE
Use Temporary Tables in Scan SQL
Use Temporary Tables
Creating temporary tables to extract data from permanent tables is a technique you can use to improve SQL statement performance. When SQL Optimizer rewrites a SQL statement, it may use this technique to generate some of the alternatives. The following is an example of an original SQL statement rewritten to use temporary tables.
Original SQL
SELECT *
FROM A
WHERE A.KEY IN (SELECT B.KEY
FROM B)
SQL Alternative
SELECT DISTINCT COL1 = B.KEY
INTO #TEMP1
FROM B
SELECT *
FROM A, #TEMP1
WHERE A.KEY = #TEMP1.COL1
Notes:
-
Since temporary tables are session related, you need to create temporary tables for each new session.
-
SQL Scanner uses separate SQL Server sessions than SQL Optimizer. Therefore, temporary tables you create in SQL Scanner are not available when you send a statement to SQL Optimizer.