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

Feature Request to accomidate frequent detach/attach scenari

I would like to request a feature in SQL Prompt 3.0. I just downloaded the final beta, and activated it (we have a license). However it has one limitation that I hope you can resolve.

Currently we work with an accounting package and switch to different configurations of that accounting package on a frequent basis. When this happens what we do is detach a database, lets call it "TEST", and attach the other version of "TEST" that has a bunch more stored procedures and tables (and tables that previously existed, not longer exist), because the accounting package has been setup with different functionality that the previous instance did not.

SQL Prompt doesn't go through a full reindex at this point, and the cache is out of date.

I would like an option in the SQL Prompt setup to say, that if you attach a database go through a full reindex/recache of the database when the database is the same name as one already in the cache (though even if it wasn't the same name and you attach a database it should go through a full reindex, which sql prompt may do, i haven't tested this).

All I know is that SQL Prompt looked like it was going to index, but quickly finished when I reattached this other "TEST" database with many added stored procedures and tables.

Thus, I got a cache in SQL Prompt that was very out of date. Additionally, when adding tables in management studio, it did not seem to pick up that new table after it was created, is there some lag time before this table will appear or do I have to manually refresh the cache? (If manually, this would be another addition I would add, the same goes for any other object type, not just stored procedures).

Regards,

Matt Olson
MattO
0

Comments

1 comment

Sort by
  • Bart Read
    Hello Matt,


    For now I'm afraid you'll need to manually refresh the database via the cache management dialog which you can access through the SQL Prompt > Cache Management menu item. However for the final release we'll be added an option to automatically refresh the cache on startup. It'll be switched off by default, but you'll be able to get the functionality you want by switching it on.

    I should point out that when it appears to be doing a full re-index what it's actually doing is pulling the cached version of the meta-data from disk and rebuilding the code completion data structures: if your database is large enough you should notice that this is significantly quicker than actually refreshing the meta-data from the database itself.

    Hope that helps.


    Thanks,
    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.