Final beta feedback and suggestions

• 
  Would it be possible to set an interval on cache refresh checks? Currently it appears as though every time I connect to a db, SQLPrompt checks the schema.
  
  Would be nice to be able to manage the interval per database. Every connection, once a day, once a week, etc
  
  I love the auto insert functionality for alter and exec. Way cool!

  GilaMonster2 December 13, 2006 05:29

  - 0 +
• 
  Hi Gail,
  

  I loaded several files into management studio at once (multiselect in the open file dialog) and SQL Prompt went and indexed the database once for each file. It hadn't cached that database before.

  Every query window has its own candidate list in memory, so each query window needs to load the schema new. However, we do save the schema on disk the first time round and then read it from there, which should make things much quicker.

  When typing out a select, the candidate list appears at strange times, eg after I've entered a table name in the FROM clause or a column in the where. Neither place is appropriate. In the first case the next this typed would be a table alias or a SQL keyword and in the second it would be an expression (=, like, in, etc)

  We do actually have keywords on the list, so you could argue that it should pop up. I do agree, though that the pop up behaviour can be improved and it is on our list of things to do. If it is annoying you a lot, you can turn off automatic pop up and only use Ctrl + Space.

  Is it possible to give us options as to what we see in the candidate list? While I like the tables, columns, functions and built-in constants, I don't want the database roles, users or logins there and it would be nice to be able to deselect those.

  I've added it to the list.

  Would it be possible to set an interval on cache refresh checks? Currently it appears as though every time I connect to a db, SQLPrompt checks the schema.

  See above.
  
  Regards,
  
  Tilman

  Tilman December 13, 2006 07:29

  - 0 +
• 

  Tilman wrote:

  Hi Gail,
  
  Every query window has its own candidate list in memory, so each query window needs to load the schema new. However, we do save the schema on disk the first time round and then read it from there, which should make things much quicker.

  I noticed that behaviour later. It seemed like that time, it loaded from the database multiple times. Possibly because several connections were made to the database at once and no cache was stored for that db when the multiple connections were made.

  Tilman wrote:

  We do actually have keywords on the list, so you could argue that it should pop up. I do agree, though that the pop up behaviour can be improved and it is on our list of things to do. If it is annoying you a lot, you can turn off automatic pop up and only use Ctrl + Space.

  True, but the keywords are at the bottom of the list. It would be nice if the popup in those places contained only the valid keywords for that point, but I guess that's a lot of work. Good to hear that it's getting looked at.

  Tilman wrote:

  Would it be possible to set an interval on cache refresh checks? Currently it appears as though every time I connect to a db, SQLPrompt checks the schema.

  See above.

  
  So it will only check the database once and load from disk after that? How often does it check the db for schema changes?

  GilaMonster2 December 14, 2006 03:27

  - 0 +
• 
  About the candidate list in memory...
  
  Could it be possible that opening two or three windows cause QA to use 200+ MB of RAM. We are currently experiencing this behaviour which forces us to close and reopen QA to save system resources... QA needs to coexist with VS 2005, which is our develpoment tool, and by itself it drains our resources.
  
  Regards,
  Juan.

  Juancis December 27, 2006 16:44

  - 0 +
• 
  Hi,
  

  So it will only check the database once and load from disk after that? How often does it check the db for schema changes?

  
  It doesn't check for changes at all, atm. If you change your schema you need to update Prompt manually by going to SQL Prompt > Cache Management > Refresh. We are planning to do some automatic refresh thing in a future version.
  

  Could it be possible that opening two or three windows cause QA to use 200+ MB of RAM. We are currently experiencing this behaviour which forces us to close and reopen QA to save system resources... QA needs to coexist with VS 2005, which is our develpoment tool, and by itself it drains our resources.

  
  I'm afraid that is very well possible, and there is not much we can do about it for the moment.
  
  Regards,
  
  Tilman

  Tilman January 08, 2007 07:02

  - 0 +

Add comment

Please sign in to leave a comment.