When you create a new query or open an existing query, SQLPrompt pops up and then locks down my editor until it gathers database information (refreshes). This is a huge annoyance because I am trying to move on with my work. With 2.0 you could do this and when it was done refreshing, SQL prompt kicked into play and started working. I think this is better than freezing the current application and waiting for it to update.
Comments
4 comments
-
Hi,
Sorry about the problems your having. It should of course work the way you want it to. Could you give me some more information. What's your editor, OS, Framework version, machine spec, editor version, anything else useful you can think of?
Regards,
Tilman -
Hi
SQL Prompt actually gathers the Schema information in a background thread just like the old version. The reason that it is locking up your UI is that it locks the UI while it indexes all the schema information. The reason it locks the UI while doing that is that we were expecting that to be a very quick operation which it clearly isn't on your machine. I have raised a bug that the indexing needs to be done on another thread so we should have this anoyance cleared up by the final release.
Lionel -
OS: Windows XP Pro SP2
Framework: ??? .NET?? 1.1 & 2.0
CPU: P4 3.6 GHz
RAM: 1 GB
Editors: SQL Server Management Studio (2005) and SQL Query Analyzer 2000.
I just tested both and right now I am just getting the pop-up with the "Messages". Previously I was getting several different items that it was cataloging that were taking the most time. The "Messages" takes about 5 - 10 seconds.
Also, we have a couple of fairly large databases on these server of 12GB + with thousands of objects (views, tables, procedures, functions, triggers, etc...)
John W. -
That sounds defaintly sounds like it taking a long time to index the schema information. Thanks for reporting this. We will try and get this fixed for the final version.
Lionel
Add comment
Please sign in to leave a comment.