How can we help you today? How can we help you today?

Cache settings

A couple of things about cache management.

1 - BUG: I think there is a problem with cache exclusion settings. We have tried avoiding caching the master db, and it works. But every time we close and reopen QA, cache settings are lost.

2 - Cache persistency: Every time we open QA and select a DB, SQL Prompt scans the objects, which don't change so often. So, is there any way to avoid cache refreshes? Or to reduce them, at least?

Thank you.
It has really improved since last version.

Redards,
Juan.
Juancis
0

Comments

1 comment

Sort by
  • Bart Read
    Hi Juan,


    Thanks for your post.

    (1) We know about this and it will be fixed for the final release: there's a problem with the shutdown hook we're using in that under .NET 2.0 it's now limited to 3 seconds of execution time so often SQL Prompt doesn't have time to save everything it needs to in this relatively short period.

    (2) Once a database has been cached SQL Prompt still has to pull the cached information from the disk and reprocess it to build up the code completion data structures. This generally takes a few seconds although is generally much quicker than going back to the database itself. Whilst this is happening the toast popup with the progress bar will appear, however this is just to let you know that SQL Prompt is working and does not mean it's re-retrieving the data from the database.

    Hope that helps.


    Thanks,
    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.