Comments
3 comments
-
Hi Dave,
I'm not sure why this is not working for you with SQL Prompt 4. I have tried it out myself by writing a select statement, changing the database dropdown, and typing a second SELECT query, which will then suggest table candidates from the newly-selected database.
Maybe it would help if you let us know the version of Prompt you use, and the exact steps to reproduce the problem.
Thanks! -
Version is 4.0.2.53
The steps are documented in my first post. -
Thanks, Dave, but I did type and execute some SQL without the problem happening to me.
SELECT * from ...
then, after changing the context, select * from...
In each case I got the list of candidates from the correct database.
Add comment
Please sign in to leave a comment.
1. Open Query Window in msdb.
2. Type and execute some SQL, prompting works as expected.
3. Change database context using the toolbar (not a USE statement).
4, Type some SQL, no database-specific prompting appears for the new database context; system variables, functions, and syntax still work as expected.
I have to close the Query Window and reopen to get database-specific prompting to work. Refresh Suggestions has no effect.