Activity overview
Latest activity by GaryH
@ATurner
Here are a few pain points. 1. Ouch. That melon-sized Search throbber. Why flash half the screen while the app does its work? We all know that a throbber is just an animated gif that doesn't really show any work is being done. This one is a real eye-stabber. Just drop it.
2. Do some QA on using keyboard-only to navigate. Behavior is really inconsistent. Sometimes focus will completely disappear, forcing me to use the mouse to get on a focused item. This happens if you up-arrow beyond the top item, but also for what seems like no reason at all. When you first open SQL History, nothing is focused, and you can't use the keyboard to gain focus. It should initially set focus on the Recent Queries list. Search result should do the same after results are returned.
3. Don't steal the ctrl-tab key! Stepping through tabs gets stuck on SQL History and I can't ctrl-tab out of it, having to remember that, oh yeah, use Esc to get out. Once in SQL History, ctrl-tab does the same thing as tab, so I think this is probably a bug. 4 Still wish it was as snappy as Tab History. That thing was FAST. Thanks, and I hope someone reads this!
/ comments
@ATurner
Here are a few pain points.1. Ouch. That melon-sized Search throbber. Why flash half the screen while the app does its work? We all know that a throbber is just an animated gif that d...
Hi @Dan_J
Interesting timing on your post. I had just now finished updating all my other Red Gate products, thinking it might help the SQL Search crash problems. It worked. SQLSearch_3.6.13.4316 is newer than the one in the Toolbelt Essentials package so SQL Search wasn't updated. There must have been some interaction between an earlier version of a Red Gate product. Maybe SQL Prompt? I was still using the last version with Tab History since the debut of SQL History was so awful. SQL Prompt is current now, and SQL Search isn't causing any crashes.
Thanks for attempting to reproduce the problem.
/ comments
Hi @Dan_J
Interesting timing on your post. I had just now finished updating all my other Red Gate products, thinking it might help the SQL Search crash problems. It worked. SQLSearch_3.6.13.431...
Dan_J Thanks for letting us know about the update. It does retain the database selections, but there is a real problem.
SSMS version 18.10 will crash if SQL Search is open and you either select the Connect dropdown [image] in the Object Explorer [image] After the crash, SSMS is unable to recover the documents that were open. It also crashes if you right click on a server name in the Object Explorer.
It also crashes if you close the SQL Search tab. Let me know if I can provide any diags
/ comments
Dan_JThanks for letting us know about the update. It does retain the database selections, but there is a real problem.
SSMS version 18.10 will crash if SQL Search is open and you either select t...
Hi Dan, Thanks so much for your attention. I sent you a DM with the log file and link for a screen recording. My Help menu doesn't show an option to set log level, but the log looks pretty verbose. That's probably what it's set to.
Gary
/ comments
Hi Dan,Thanks so much for your attention. I sent you a DM with the log file and link for a screen recording. My Help menu doesn't show an option to set log level, but the log looks pretty verbose...
Now there's an inverse problem in version 3.6.7: If you click in the Object Explorer on a database name or expand it, it becomes the database that SQL Search will always revert to until you do the same with another database or restart SSMS. The selection reverts to this database if you click the SQL Search button or the server drop down list. There is now no way to make more that one database or "All Databases" persistent. Can't Red Gate just persist whatever is selected in the drop-down list? If not, give us a "Lock" checkbox to do that? / comments
Now there's an inverse problem in version 3.6.7:If you click in the Object Explorer on a database name or expand it, it becomes the database that SQL Search will always revert to until you do the s...
I downgraded to 10.12 to get Tab History back. SQL History is just an awful half-baked mess. It's slow, it hijacks ctrl-Tab so you have to use the mouse to get out of it, tons of useless iterations to scroll through (again, so slooooow), search just plain doesn't work. Who on earth thought that gigantic throbber was a good idea?
Red Gate, please offer Tab History as an option in future versions, and for your own good, reassign everyone involved in the design of SQL History to someplace where they can't hurt anything.
/ comments
I downgraded to 10.12 to get Tab History back. SQL History is just an awful half-baked mess. It's slow, it hijacks ctrl-Tab so you have to use the mouse to get out of it, tons of useless iteratio...