- or
3 results found
-
Outlining
Would be great to be able to add user specific outlining, so that you could add + & - where ever you choose in a sql script to collapse down certain parts. The CRM system that I support has a create contact table import with 200 columns which is regularly used and this functionality would be great when having to resort to using this import etc...
6 votes -
Outline for scripts
It would be very helpful if there was an outline for the script being edited. Say, a script has many "CREATE PROC"s. We could have a tree or a list or a drop-down, to view a list of CREATE PROCs and click to scroll to the section.
If a tree style is selected, this could be expanded into seconds inside each PROCs.
3 votes -
code folding
Enabled Intellisense conflicts with SQL Prompt and needs to be disabled. This also disables Code Folding feature (Outline Statements) of SSMS, which is very useful for large coding projects.
It would be helpful if SQL Prompt were to offer the similar feature.8 votes
674 results found
-
Add a warning for using a self-join in a delete or update statement
Add a checkbox to the warnings settings, for if a self-join is detected when doing an UPDATE or DELETE.
1 vote -
SQL Search endpoint for Fabric
Make SQL Search work with Fabric
1 vote -
fabric
Even if you don't add support for Fabric warehouses and lake houses soon, please detect that the current connection is to a Fabric object and quietly disable SQL Prompt's IntelliSense so it stops crashing when I connect to a Fabric lake house or warehouse.
Keeping the formatting working would still be nice though.
2 votes -
frequently use the ScriptObjectAsAlter shortcut in Visual Studio to modify views and procedures. However, when the script opens, it default
frequently use the ScriptObjectAsAlter shortcut in Visual Studio to modify views and procedures. However, when the script opens, it defaults to ALTER VIEW or ALTER PROC, while our source control requires everything to be saved as CREATE OR ALTER.
Would it be possible to introduce an option in SQL Prompt to default these scripts to CREATE OR ALTER instead of just ALTER? This would streamline the process and reduce manual edits before committing changes.
1 vote -
Aggregate Min/Max for Date/Time
Show aggregates Min and Max for Date/Time columns in result grids.
1 vote -
Allow typing from table then tab to convert it to Select | from dbo.table
Allow typing from table then tab to convert it to Select | from dbo.table and end up with the cursor after the from, to start typing. Now we have to write select * from table, then go back to the columns. A simple improvement.
1 vote -
Add support for PERCENTILE_CONT function.
The statement below is not formatting correctly. There is no space before or after the WITHIN GROUP clause.
PERCENTILECONT(0.5)WITHIN GROUP(ORDER BY Z.cntrresult) OVER (PARTITION BY Z.environment, Z.cntrfullname, DT.GRAIN_DT) AS [median]1 vote -
fabric
Add support basic intellisense support for Fabric SQL databases (it's eq. to all Microsoft SQL database and Azure SQL DB ect.!)
7 votes -
Automatic Log In after Update
After every update I have to Log On to get SQL Prompt working. Can´t the update do this or just do not log me off?
1 vote -
Generate script for Table Types
When hovering over a Table Type the pop-up window only shows tabs for Summary and Dependencies. Add a Script tab for consistent functionality when compared to other types of object such as Stored Procedures, Tables, Views, Functions etc.
2 votes -
Go to variable definition
I would like a feature that allows a user to right click on a variable name and allow for an option of
Go To Declarationso it would scroll up to the place where the variable is declared. The hover option shows how it is defined, but not where it is defined which is also extremely helpful when troubleshooting and researching a script.4 votes -
Modify Code Analysis to show able definition instead of blocking it
When I have Code Analysis enabled the mouse over shows the Code Analysis finding if there is something that isn't breaking a rule. However, this also makes it so that I can't see the normal mouseover behavior of an object. The only way I can see the object definition that would normally show up is if I disable Code Analysis. The only way I can do this by going in and temporarily disabling Code Analysis. Is there some way to make this more intuitive? Maybe if there is a Code Analysis finding you could show the code analysis finding and also show a link to the object definition? Or in the left-hand margin there is an icon that appears when a Code Analysis finding is flagged, maybe you could add a option there for
Show Object Definitionor something like that so it was easier?When I have Code Analysis enabled the mouse over shows the Code Analysis finding if there is something that isn't breaking a rule. However, this also makes it so that I can't see the normal mouseover behavior of an object. The only way I can see the object definition that would normally show up is if I disable Code Analysis. The only way I can do this by going in and temporarily disabling Code Analysis. Is there some way to make this more intuitive? Maybe if there is a Code Analysis finding you could show the code analysis finding and…
1 vote -
Align column aliases, but only up to a configurable MAX point
The alias alignment is a nice feature that improves the readability of the formatted SQL. Still, it sometimes gets lost too far to the right when the selected column values include things like SQL functions and column names. In those cases, the alignment of the column aliases can require scrolling to the right to see them with a great amount of whitespace between the column name and the aliases and they thus become a detriment to the readability of the SQL.
It would be great if we could configure a max number of spaces to align the aliases before which they just ignore any columns that are OVER that max and align as if those wide columns didn't exist.
I'd still like them to align in that case, just skip the really wide columns that otherwise make the alias alignments unhelpful. The wide columns would just not have their aliases aligned at all with the other ones when this max is set and those columns exceed that max.
The alias alignment is a nice feature that improves the readability of the formatted SQL. Still, it sometimes gets lost too far to the right when the selected column values include things like SQL functions and column names. In those cases, the alignment of the column aliases can require scrolling to the right to see them with a great amount of whitespace between the column name and the aliases and they thus become a detriment to the readability of the SQL.
It would be great if we could configure a max number of spaces to align the aliases before which…
3 votes -
Add or detect missing 'N' on inline string literals containing Unicode characters
This is an extension of:
https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/6779217-add-n-to-unicode-type-literal-stringsExcept I would like to improve this feature so that it is not limited to just variable declarations, but also for inline string literals.
For example, if an inline string literal contains a unicode character, it should have the N prefix. If anything it should probably be a Code Analysis rule rather than formatting because this change can absolutely impact code behavior. So I think it's better suited to be an analysis rule.
5 votes -
Intellisense for system stored procedure parameter values
For system stored procedures, some parameters have a predefined set of possible values, e.g.
msdb.dbo.sp_add_jobstephas the parameter@on_success_action.The MS documentation lists this predefined list of possible values:
1 (Default) Quit with success
2 Quit with failure
3 Go to next step
4 Go to step@on_success_step_idIt would be great if Intellisense could suggest values for these sorts of parameters, saving a trip to Microsoft's website.
3 votes -
sub
I would like to be able to check a box and always indent a sub-query.
currently formatting a query works like this:
SELECT *
FROM dbo.tbl1 AS a
INNER JOIN(SELECT ID FROM dbo.tbl2 WHERE value = 'y') AS b ON a.id = b.idwhen the paren is set to inline the open paren and indent the content with the indent parentheses contents checked. I would rather have a checkbox to force the sub-query to format like this:
SELECT *
FROM dbo.tbl1 AS a
INNER JOIN (
SELECT ID
FROM dbo.tbl2
WHERE value = 'y'
) AS b ON a.id = b.idI would like to be able to check a box and always indent a sub-query.
currently formatting a query works like this:
SELECT *
FROM dbo.tbl1 AS a
INNER JOIN(SELECT ID FROM dbo.tbl2 WHERE value = 'y') AS b ON a.id = b.idwhen the paren is set to inline the open paren and indent the content with the indent parentheses contents checked. I would rather have a checkbox to force the sub-query to format like this:
SELECT *
FROM dbo.tbl1 AS a
INNER JOIN (
SELECT ID
FROM dbo.tbl2
WHERE value = 'y'
) AS b ON a.id =…1 vote -
Option to display values within IN statements without spaces between them
Another white space removal feature to suggest.
The ability to format all IN statements as:
empType IN ('a','b','c','d')Rather than the default:
empType IN ('a', 'b', 'c', 'd')I have done some exploring in the formatting styles and scouring the forums here and this feature doesn't seem to be available.
2 votes -
Surround highlighted text with
Surround highlighted text with 'thing' instead of replacing it. Like in azure data studio or visual studio, pressing "(" will surround the highlighted text instead of replacing it. I have created surround snippets to surround the highlighted text with what I want; it's just not as good to use.
4 votes -
The automatic aliasing of tables and views could be improved
Say I typed the code below, just to look at the content of a table (don't slam me for the SELECT *, this is pseudo code).
SELECT * FROM dbo.Address AS A
dbo.Address was automatically aliased as "A", which is fine.
Now, let me double-click on "Address" and replace this table name with another one, just because I want to save time:
SELECT * FROM dbo.Affiliation AS A AS A
This time, the table was automatically aliased again, but your feature does not seem to care if the table was already aliases.
So now, the table is double aliased.
5 votes -
Allow indentation similar to nested JOIN when they are not written as nested
A nested join is indented additionally relative to the join that it is nested within:
SELECT *
FROM Person.Address
--INNER JOIN Person.StateProvince
----INNER JOIN Sales.SalesTerritory
------ON SalesTerritory.TerritoryID = StateProvince.TerritoryID
----ON StateProvince.StateProvinceID = Address.StateProvinceIDWhen joining the same tables but not writing them in a nested manner, there is no additional indentation:
SELECT *
FROM Person.Address
--INNER JOIN Person.StateProvince
----ON StateProvince.StateProvinceID = Address.StateProvinceID
--INNER JOIN Sales.SalesTerritory
----ON SalesTerritory.TerritoryID = StateProvince.TerritoryIDIt would be nice to allow the same amount of indentation that would be used if the join were nested to be used when it is not nested:
SELECT *
FROM Person.Address
--INNER JOIN Person.StateProvince
----ON StateProvince.StateProvinceID = Address.StateProvinceID
----INNER JOIN Sales.SalesTerritory
------ON SalesTerritory.TerritoryID = StateProvince.TerritoryIDA nested join is indented additionally relative to the join that it is nested within:
SELECT *
FROM Person.Address
--INNER JOIN Person.StateProvince
----INNER JOIN Sales.SalesTerritory
------ON SalesTerritory.TerritoryID = StateProvince.TerritoryID
----ON StateProvince.StateProvinceID = Address.StateProvinceIDWhen joining the same tables but not writing them in a nested manner, there is no additional indentation:
SELECT *
FROM Person.Address
--INNER JOIN Person.StateProvince
----ON StateProvince.StateProvinceID = Address.StateProvinceID
--INNER JOIN Sales.SalesTerritory
----ON SalesTerritory.TerritoryID = StateProvince.TerritoryIDIt would be nice to allow the same amount of indentation that would be used if the join were nested to be used when it is not nested:
SELECT *
FROM…1 vote
- Don't see your idea?