674 results found
-
Stop Overwriting Existing Features With new Alternatives that Aren't Merely Updates
The recent roll-out of SQL History was handled very poorly. SQL History isn't simply an update to Tab history else there would not have been the need for a name change. SQL History is an alternative feature meant to do what Tab History does (I hope) and more but on roll-out it made many of your paying customers not only angry because you replaced Tab history with it but because it wasn't ready for roll-out.
In the future when you feel the need to replace an existing beloved feature with something different and not just an update, DON'T! Instead roll…
3 votes -
snippet refresh
Snippet adds or updates are not refreshed until SSMS is restarted.
Can you add a feature to auto refresh the cache of snippets or make part of the "refresh suggestions"
3 votes -
Operators configuration depending on where they are placed
There is a general configuration for operators AND/OR. However, for us it is important to distinguish between the different places they are used:
- JOIN
- WHERE
- CASE ...
Would it be possible to configure the AND/OR options inside each block?
3 votes -
Exclude standard column names from join suggestions
We add certain standard columns to all tables (LastUpdatedDate for example). Would be great to be able to set a list of these columns in the Options so they can be excluded from list of suggested JOINS
3 votes -
Create shortcut to filter setting
Hello Redgate and the community,
During my day to day work, it would be greatly helpful to get a shortcut to enter the filter setting menu, not only on databases, but also tables, views and stored procedures and what not, just a global shortcut, to enter the filter setting on the selected folder (if that is available for the folder)3 votes -
New Code Analysis Rule: Flag system named constraints
It is generally bad practice to use system named constraints and there should be a rule for flagging them when there is DDL code creating one.
3 votes -
Script as Insert #tempTable to snippet/placeholder text
When using the Script as Insert, it generates the Create Table with the table name as
#temptable. If you want to change that name, you have to then change it in the Create, Insert, and Drop locations.
Would be nice if this defaulted as a snippet placeholder so that editing one would edit the other two as well.3 votes -
Open in Excel / Export to Excel - Choose file location for file creation
Currently the files write out to a temporary file location. Add pane in settings window to change the location (e.g. a folder in my one drive that is not read only)
3 votes -
Add AI assistance
As AI powered tools like codepilot, kite or tabnine are on the rise, It would be so great to add an AI assistant to SQL Prompt to support developers on their way to write t-sql code effortless.
3 votes -
foreign key follower
There is a feature that was in WinSQL where each field in a column would have a little plus sign if it had a foreign key. If you click the plus sign it would look up that value in the table with the foreign key in a new tab (it would give a choice of tables if there are more than one, then do the lookup).
It was very useful and a great learning tool; it would be a great addition to SQL Prompt. Pictures attached.3 votes -
Indent FROM clause
Allow the FROM, WHERE, GROUP BY, etc. clauses to indent from the select.
Change
SELECT Col1,
Col2
FROM Tab1
WHERE a = bTo
SELECT Col1, Col2 FROM Tab1 WHERE a = b3 votes -
export to excel bug(?) -- Acts odd if multiple result sets
Before I upgraded to latest version of SQL Prompt, if I had two queries in the same "New Query" window and ran them, I could select either of the two result sets and choose "Open in Excel" to open up the selected result set in Excel. Now it always seems to auto-select the first result set.
What I'm usually doing here is two related queries. I pick the larger result set, open that in Excel, and then add a new tab to Excel and copy-and-paste the smaller result set to the 2nd tab. Or sometimes I'm doing multiple queries to…
3 votes -
Generate C#/VB.NET class
It would be nice to have the ability to right-click on a table or stored procedure and generate a C# or VB.NET class from the table structure or stored procedure results that could be used in a development solution.
3 votes -
Have formatting features for cross join match those of left/right/inner join
I have set up rules to format as such:
Select *
From Employees e Join
People p On e.PersonID = p.PersonID;Each table/view object aligned on a new line. However, when I convert to a "cross join", they don't generate a new line, they concatenate on the same line, like such:
Select *
From Employees e Cross Join People p;3 votes -
Additional options for formatting the ON constraints of a JOIN
It would be appreciated if you could enhance the SqlPrompt Formatting Styles functionality for the Clauses >>> JOIN section. I'd like the ON keyword to stay on the same line as the table-name, but when constraints are line-wrapped, I'd just like them to be "normally" indented.
Presently, the only way to get close to this behavior is to check the "Place ON keyword on new line" checkbox and set "ON keyword alignment" to "Indented". But I don't want that box checked.
3 votes -
Table Column Format Correction
In cases where there is SELECT DISTINCT or SELECT TOP(n) .. I would l like the option to format my table's columns to appear on the next line and indented 1 tab or set of spaces in from the SELECT and not necessarily aligned with DISTINCT or TOP in the line above.
SELECT DISTINCT
COLUMN1,
COLUMN2
FROM ...instead of
SELECT DISTINCT
Column1,
Column2
FROM ...3 votes -
Ability to choose schema when there are multiple objects with the same name exists
Currently when SQL code is formatted, it will pick the first schema, if there are multiple objects with same name but having different schemas. It would be good if the choice is given to the user to choose which schema.objectname to use in this case.
Also it's better if we can exclude certain schema's to be considered during code format. (But want to see the intellisense. Only to exclude them during the code format)
3 votes -
Find invalid objects in script
Highlighting invalid objects is a nice feature, but it would also be nice to "find" invalid objects in a script.
Running SQL Format on a script with an invalid object in it runs fine and gives no error, it just doesn't prefix the object (like a table) with the schema.
It would be nice to have a quick and easy way to "go to next invalid object" or even for when you run SQL Format to have it bring up a warning saying "this/these object/s appear to be invalid".3 votes -
"Insert Semicolons" feature should add Semicolon after "BEGIN"
When using a BEGIN/END block, the "Insert Semicolons" feature adds a semicolon after "END" command, but not after the "BEGIN" command.
One reason why this should be done, is the use of the THROW statement, which requires the previous statement to be terminated with a semicolon.
Technically it is still runnable code, but, SSMS (as of version 18.8) sees it as a syntax error (see screenshot).
I don't know which is the appropriate fix...waiting for SSMS to fix the syntax error it shows (but I doubt they will since the non-use of semicolons is deprecated), or if it's appropriate for…
3 votes -
Do not auto complete literal strings
Currently SQL Prompt displays suggestions for auto-completing literal strings. These are never valid suggestions so can this be turned off (or at least have an option to turn this off)?
3 votes
- Don't see your idea?