663 results found
-
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.
3 votes -
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…
1 vote -
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.
1 vote -
Add support for Fabric warehouses and lake houses
Add support basic intellisense support for Fabric warehouses and lake houses.
14 votes -
open excel with different account
Configure a different account than the one opening SSMS to open Excel for results. We use an Admin account for DBA work separate from our Windows account.
3 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.
2 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.
1 vote -
VSCode integration.
I've used SQL Prompt for 20 years. I would LOVE VSCode integration.
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 =…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.
1 vote -
Formatting style for CASE statement: on a new line
Add a feature for the formatting styles for CASE expression.
Currently the formatting is so strange, it adds indents that don't make sense.
It should have the possibility to add CASE on a completely new line.Please add :Start expression on a new line or something…
2 votes -
Sql prompt support for Dedicated SQL pool
Add support for Dedicated SQL pool on Azure Synapse.
3 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…1 vote -
Separate VALUES style by first/subsequent
It would be nice to have an option to specify different styles when there is one set of VALUES compared to multiple. For example, I would like to use "Compact, indented) when there are multiple sets of VALUES:
INSERT INTO Employees
( id
, FirstName
, LastName
, BirthDate )
VALUES
( 2
, 'Jane'
, 'Doe'
, GETDATE())
, ( 3
, 'Frederico'
, 'James'
, GETDATE());But compact when there is only one set of VALUES:
INSERT INTO Employees
( id
, FirstName
, LastName
, BirthDate )
VALUES
( 2
, 'Jane'
, 'Doe'
, GETDATE())1 vote -
CTE on new line with commas before items is adding an extra line
When using the Lists > "Place commas before items" combined with the CTE >" Place CTE name on a new line" options, the subsequent CTEs are getting placed on new lines after the comma is already on a new line, resulting in:
WITH
myCte
AS ( SELECT 1 a )
,
mySecondCte
( Col1, Col2 )
AS ( SELECT
'Test' AS ThisIsAColumn
, 'Test2' AS ThisIsAnotherColumn
FROM Person.BusinessEntityContact )
SELECT *
FROM myCteI believe this combination of settings should be resulting in:
WITH
myCte
AS ( SELECT 1 a )
, mySecondCte
( Col1, Col2 )
AS ( SELECT…1 vote -
Place empty lines between BEGIN/END and their contents
The Whitespace > "Empty lines between statements" option doesn't appear to consider BEGIN/END as separate statements from the code between them, resulting in formatting like:
WHILE @@ROWCOUNT > 20
BEGIN
IF @BusinessEntityID > 0
DELETE FROM HumanResources.Employee_Temporal
WHERE BusinessEntityID = @BusinessEntityID;
ELSE
BREAK;IF @OldId < 2000
RETURN @OldId;
END;Please modify the behavior or provide another option such that the following result can be achieved:
WHILE @@ROWCOUNT > 20
BEGINIF @BusinessEntityID > 0
DELETE FROM HumanResources.Employee_Temporal
WHERE BusinessEntityID = @BusinessEntityID;
ELSE
BREAK;IF @OldId < 2000
RETURN @OldId;END;
1 vote -
Add system versioned table scripting
Add system versioned table scripting
2 votes -
SQL Prompt - More Granular Suggestion. WHERE AND / CASE AND
SQL Prompt - More Granular Suggestion. WHERE AND / CASE AND
Would you add a couple of settings that give users more granular control in formatting SQL Prompt, please?
In the CASE section, please add a section on how to handle Case AND statements, if we want the AND on a new line or the same line, and where to Align the AND.
Also, please add a checkbox to align any '=' signs, like CASE WHEN colA = 1 then 1 else. I'd like all = signs to line up when there are multiple WHEN statements.
Also, Please add a…
2 votes -
Align tables within FROM clause
Currently, I can get SQL Prompt to format my SQL like this.
SELECT
tbl.name AS TableName,
col.name AS ColumnName
FROM
sys.tables AS tbl
INNER JOIN
sys.columns AS col
ON
tbl.objectid = col.objectidThis annoys me because the tables in the FROM statement are not aligned. I would like to be able to achieve something like below where the tables are aligned and the join and ON are indented from the table. So the tables are indented from the FROM and the INNER JOIN is indented from the table. Then, the ON can either be indented from table or…
1 vote -
Option to Change != to <>
Although used quite often, != is not ANSI compliant for NOT EQUAL. Have an option in SQL PROMPT Code Formatting to automatically replace != with the ANSI compliant <>.
2 votes
- Don't see your idea?