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

SQL Prompt v3 Final Beta caused my QA to lock up and close

Gents. Just downloaded v3 and tried it out...

Looked cool UNTIL it locked up my QA while it was trying to save a snapshot of one of our largest databases. Glad I did not have any work I really needed in that QA instance. Then it errored out when I clicked in the bottom text box in the OPTIONS-->Snippets. I realize it is a Beta, but these kind of errors should not be happening at this stage.

Are these known bugs? If not, is there anything I can do to assist with capturing information to help you fix these bugs?
bconlon
0

Comments

1 comment

Sort by
  • Bart Read
    Hi there,


    Thanks for posting. I think it's likely that the "hang" may actually just be because it can take quite a long time to cache very large databases - we have one Peoplesoft database that we use for testing here that takes 15 - 20 minutes. Even when it's been cached this monster takes a couple of minutes to pull back off disk as well, because of course we compress and encrypt the data and the decompression/decryption adds some overhead to the process.

    There is a chance though that if your machine doesn't have enough physical memory that it might hang whilst loading. Much of the information, such as e.g. stored procedure, view, function text etc is cached on disk, however the completion data structures, which are in themselves sizeable, are necessarily stored in memory because they have to be able to respond and filter instantaneously on every keypress.

    To give you an idea, with our Peopesoft database my copy of SQL Prompt chews up 800 - 900MB on a machine with 2GB of physical memory. Unfortunately due to limitations in the meta-data model we're using it's not possible to limit the information that SQL Prompt pulls back from the database to particular schemas or object types. This is something we might consider adding in the future though in order to support very large databases. Part of the issue here is that our meta-data model is used in a number of our tools so making what would be a fairly radical set of changes to support this could cause significant problems, hence we have not done so for this release.

    The error you found in the snippets pane of the Options dialog is a bit of an embarrassing blooper: I can't quite believe nobody here spotted it before it went out, and it took all of 1 minute to fix once we were aware of it. I can imagine that it might crash Query Analyzer, however in SQL Server Management Studio you should be able to carry on working fine after it's occurred. In QA, once you've dismissed the error dialog, if QA itself doesn't close then again, you should be OK to carry on working.


    Many thanks,
    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.