At the moment to purge old tabs you need to open the tab history window and scroll to a certain point and right click and choose "Remove tabs older than this"
This can be a bit tricky so instead could we have a button (perhaps in options?) that will prompt you for a date and purge items last closed before that date.3 votes
Thanks for the suggestion!
We’re actively reviewing this suggestion alongside some others for Tab History. We’ll update again here when we progress.
Add the ability to define groups of tabs that are used regularly for different jobs. For instance--there is a group of scripts I use for month end processing and a completely different set of scripts I typically have open for daily processing. Monthly statement preparation and troubleshooting comprise another set of scripts. I'd like to be able to name groups of tabs and retrieve them based on that named grouping, while still being able to go back to what I was doing before the "interruption" that caused me to need a different set of tabs open.32 votes
We’re looking at improvements to tab history later during 2019 so will review this suggestion.
Interested in demand, so do vote on the suggestion if you would find it useful.
If I am running an "ALTER" or "CREATE" or "DROP", etc. Have SQL Prompt automatically refresh suggestions after my call.14 votes
The team are currently reprioritising this suggestion with a view to picking it up during 2019.
Enhance Smart Rename to accept a list of name changes.
Even if it runs the existing smart rename and concatenates the scripts it would save a lot of data entry time versus doing each change one at a time.
You should require fully qualified names in the import data to avoid ambiguity errors.56 votes
We’re going to be reviewing this over the next couple of months, which would be released via the SQL Prompt for Teams EAP (get in touch if you want to know more).
In the meantime please add any other information that you think would be useful.
I think having an API to format generated SQL scripts, whether it be from the SQL Compare API or another process like SMO objects, to able to apply the formats saved in SQL Prompt.32 votes
It would be great if you could let us know more about how you’d use a Prompt API / command line version of Prompt.
What problems are you having without it?
How are you getting around those?
How would this make your work better?
- Don't see your idea?