|Subject:||WinSQL pauses for a long time while writing SQL queries|
|Creation date:||7/29/09 5:05 PM|
|Last modified on:||12/12/18 10:09 AM|
Users often complain about WinSQL not responding while typing queries, especially if they are connecting to a large database. This pause is caused by WinSQL's Intelli-tip feature that tries to run a query in the back-ground.
WinSQL's Intelli-Tip feature tries to determine what objects are available in the database as you type your queries. There are two type of intelli-tips:
|If your database contains thousands of
tables, it may take a long time to fetch the initial catalog. However,
once the catalog is fetched in memory, it can be much faster.
Meta Data lookup occurs right after SELECT, FROM, WHERE, INSERT, UPDATE, and DELETE clause. This is when WinSQL tries to fetch available fields and table names from the database to assist users to type their queries.
Data Lookup occurs after the operator is specified in a WHERE clause. For example, right after the following string is typed.
select * from Customer where Company =
As soon as an operator is encountered in the WHERE clause, WinSQL tries to fetch the data for that field.
The section on the right hand side deals with Data Lookup. Select a desired value from the Enable/Disable Data Lookup combo box to configure Data Lookup. The table below describes each value.
|Disable data lookup||Select this option to completely disable data lookup|
|Enable for every column||Select this option if you are connecting to a small database. WinSQL will try to pull data for every column that is in the database. It will run a SELECT distinct query as soon as you type the operator after a WHERE clause. Selecting this option will take a long time on large databases.|
|Enable for columns that I choose||This is the best option for large database. Data Lookup only appears for fields that you decide.
Follow the steps below to specify the fields for which Data Lookup should occur.