Skip to content

How can we improve SQL Prompt?

SQL Prompt: Tab history

CATEGORIES
All ideas
My feedback
Code Analysis 48 ideas
Encapsulate as new stored procedure 1 idea
Expand wildcards 7 ideas
Find invalid objects 7 ideas
Find unused variables 3 ideas
Format SQL 186 ideas
Intellisense 77 ideas
Platform Support 16 ideas
Qualify object names 6 ideas
Script object as alter 14 ideas
Smart rename 10 ideas
Summarize script 5 ideas
Tab coloring 5 ideas
Tab history 42 ideas
User interface 89 ideas

Searching…

No results.
Clear search results

- Flyway 16 ideas
- MySQL tools 24 ideas
- Oracle 129 ideas
- Redgate 0 ideas
- SQL Change Automation 49 ideas
- SQL Compare 250 ideas
- SQL Data Compare 110 ideas
- SQL Prompt 662 ideas
- SQL Search 133 ideas
- SQL Source Control 588 ideas
- SQL Toolbelt Essentials 15 ideas
Redgate

SQL History keyboard shortcut

Just like Tab History has, SQL History should have a keyboard shortcut to open the window.

2 votes

Adam Jeppson shared this idea · Jan 27, 2023 · Report… · Admin →

completed ·

Adminjames.hemson (Admin, Redgate) responded · Jan 31, 2023

Hi there,

Thanks so much for the message.

You can also use CTRL+SHIFT+X to access SQL History.

I hope this helps!

Show previous admin responses (1)

An error occurred while saving the comment

Adam Jeppson commented · January 31, 2023 1:58 PM · Report

Thank you! Also, for anyone still reading this, once in the sql history window, you can do a Ctrl-F to go to the search input box.

Submitting...
Rob commented · January 27, 2023 9:15 AM · Report

Thanks for the quick response.
That is easier than a button but is still a bit slow and cumbersome.
I currently map Tab History to Alt-Q since that is very quick to type with one hand.

I still have other usability issues with SQL History but am hopeful that it will soon get some needed features so I can finally upgrade and use it instead.

Submitting...
Rob commented · January 27, 2023 7:53 AM · Report

redgate, its crazy to have to ask for this as a feature...
Requiring mouse clicks for a feature related exclusively to text input makes no sense.
SQL History should be an optional beta/preview until it's features are better flushed out and polished.

Submitting...