SQL Scanner helps identify problematic SQL statements in your database environment by automatically extracting statements from your source code. SQL Scanner retrieves and analyzes the execution plans for the extracted statements and classifies them according to complexity. You can then optimize statements classified as problematic using SQL Optimizer. SQL Scanner can extract and analyze statements from the following:
| Database Objects | Database objects with embedded SQL statements which includes stored procedures, triggers, views, rules, and defaults. |
| Single Command Line Dynamic (SCLD) Files and Database Objects |
Database objects and files that contain SCLD SQL statements including Java or Visual Basic source code. Notes: SCLD SQL statements are the only type of dynamic SQL statements that SQL Scanner can extract directly from source code. |
| Microsoft SQL Server Profiler Files | Trace files and tables created using Microsoft SQL Server Profiler. You can use SQL Server Profiler to capture SQL statements while the applications are running. |
| Text/Binary Files | Text and binary files that contain embedded SQL statements. |
| COBOL Files | COBOL source code that contains embedded SQL statements. |
|
Notes: If your application generates dynamic SQL statements at run time, use SQL Server Profiler to capture the statements and store the output in a trace file or trace table. Afterwards, use SQL Scanner to extract and analyze the captured statements. | |
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
