Comments
6 comments
-
Btw, I am using SQL Prompt EAR 5.0.0.591.
-
Hi Kondrich,
I'm glad you are finding the Find Invalid Objects feature useful. Unfortunately we were unable to get support for temporary tables in this release but we will look at including it in the future.
Quick question regarding your hanging SSMS: how large is the database that was presenting problems?
Thanks for your comments and feel free to email me directly with any further feedback, suggestions or ideas.
All the best,
Luke Jefferson
Product Manager
Red Gate Software -
Hi Luke,
what size measure do you need? Data files size in GB, count of objects in the database?
I just run various tests on smaller databases and bigger ones (considering database size in GB and objects count), but I do not have a clear sight what the problem might by. I guess it's not the size in GB but the object count. Perhaps it depends on how many procedures, functions, views (= objects with a source code) exist within the database.
Please let me know if there is any measure that I may count and report (e.g. from sys.objects). -
Finding invalid objects is working much better in 5.0.638 RC1. However, I get timeouts on certain databases (I think they occur on databases that contain much (stored procedure, function,...) code.
-
Hi Kondrich,
Thanks for downloading and trying the SQL Prompt 5 RC.
Could you please confirm what sort of connection you have between SSMS and your database--is internet or VPN involved?
Luke -
Hi Luke,
the connection to all monitored servers is within our LAN, no internet, no VPN.
Add comment
Please sign in to leave a comment.
though this feature is very useful - in fact, I am wondering why it is not generically implemented in SSMS - I found two issues:
* Temporary tables referenced e.g. in procedures are shown as a reference to an invalid object. Since it will be created at run time during procedure execution this information is trivial in general and considered to be a false positive.
* "Sometimes" a refresh or even closing search window and re-searching for invalid objects within the same database seems to stall and invalid objects are not shown. After minutes of searching, I canceled it, but it did not recover on subsequent runs. Restarting SSMS always helps (I m using SSMS 2008 R2 10.50.1746.0).
Unforunately, I am not able to reproduce this issue every time. Sometimes it is working as expected...