Invalid SQL
In some cases the scanned SQL statements are classified as invalid. They may fall into one of the following:
No privilege to tables or views
The logon user does not have privilege to the tables or views referenced even though the syntax of the SQL statement is correct.
Using the wrong database or user
You can declare the database and user used to scan for SQL statements. If these do not match with the SQL statement, it may be classified as invalid.
Dynamic SQL statements
The SQL Scanner is unable to identify SQL statements that are dynamically created if the text of the SQL statement is not all on one command line.
General Tab
General (General Tab)
View General - General page
The General page of the General tab of the Preferences window allows you to specify the general settings.
Character set (Default = English)
Character set
Specify the language set used to enter and display SQL and data. However, this setting does not affect the user interface language which is always in English.
Code Finder and Object Extractor (Default = checked)
Show extraction options
Specify whether to show the Extraction Criteria window when extracting object DDL in the Code Finder module and Objector Extractor module. The Extraction Criteria window allows the specification of the script information.
Display process description animation during optimization
Show process description (Default = checked)
Specify whether to show during the optimization process the animated explanation (displayed in the Information pane of the SQL Optimizer window) describing the optimization process.
Maximize window
Maximize the first window opened (Default = cleared)
Specify that the first window you open is maximized. Every window that you open after that also opens maximized.
If you "restore down" a window, then all open windows are "restored down" and any other window that is open is not maximized as it is open. Once all windows are closed, the next window that is open is maximized as it is opened.
Load Data Dictionary
Load database dictionary after database connection (Default = cleared)
Specify that the database dictionary is not automatically loaded into the memory of the computer every time you connect to a database. With this option unselected, the specific information that you need from the database is loaded when the SQL statement is parsed for functions such as scanning, optimization, and index generation. With this option unselected, the member lookup function used in text editing will not have all of the information about every database object.
SQL parameters
Enable SQL parameter history (Default = checked)
Specify to save the parameter information that you enter into the Parameters window so that next time that you are prompted to enter the values for the parameters, the data type and value that you last used for a parameter name are automatically entered for you. The parameter names are case sensitive, so dpt_id and DPT_ID are treated as two different parameters.
Maximum number of parameters (Default = 100, Range 10 - 9999)
Specify the maximum number of parameters that will be saved. When the maximum number is reached, the parameter name that is the longest unused will be removed from the file when a new parameter name is added.
Message (General Tab)
The Message page on the General tab of the Preferences window allows you to decide which confirmation messages to show.
Display confirmation messages
Show confirmation before closing Application (Default = checked)
Brings up a dialog field to confirm that you really want to exit the program.
Show confirmation before clearing optimized SQL statements (Default = checked)
Brings up a dialog field to confirm that you want to remove all the alternative SQL statements and reminds you that you can save them.
Show confirmation before saving data (Default = checked)
Specify whether to show a confirmation message when saving data (for example from the Run Result and Database Explorer [Data tab] windows).
Show confirmation for Run Result (Default = checked)
Specify whether to show the confirmation message to continue to retrieve records from the first result set before getting the second result set.
In the Run Result window, you can display multiple result sets. If there is a query already opened from the last time you executed the Run Result function, you are prompted to continue to retrieve all records from the first result set before getting the second result set.
Note: The time it takes to retrieve all records from the last query will depend on the SQL performance.
Display description message
Show message when SQL Collector is opened (Default = checked)
Specify whether to show a message each time the SQL Collector module is opened that tells you to use the SQL Inspector module if you have Adaptive Server 15.0 or later.