156 results found
-
Refactoring an INSERT statement into an UPDATE statement with SELECT
Be able to refactor INSERT statement into UPDATE statement that has SELECT rather than VALUES i.e. "insert into xxx select from".
2 votes -
DDL Parentheses Formatting should apply to VALUES clause of INSERT Statements - Bug?
The current parenthesis options I have set for an INSERT INTO (DML) statement, only appear to work for the list of columns, but NOT for the list of values in the VALUE clause. I'm unsure why this behaviour is different, but this inconsistency seems like a bug.
I have provided a screenshot where you can clearly see the parentheses are not aligned correct in comparison with the INSERT statement.
Ultimately I would like for the formatting to be overall consistent.
2 votes -
Unformat Query
Add a menu Item option to unformat a query. In other words take the query that is highlighted or every query in the script and convert them to be on a single line with only a single space between keywords, words, and operators.
This would be very useful for having to copy SQL into a table or other some object that shouldn't have normal formatting in it.
An option would be to double up all single quotes, so that the query can be placed between single quotes.5 votes -
Properly format the start of a CTAS in Azure Synapse Analytics
SQL Prompt does not start a new line for the SELECT portion of a CTAS statement within Azure Synapse Analytics when there is a defined distribution or index using a WITH clause. Instead the SELECT statement is tabbed way over to the right.
4 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 ...2 votes -
Use formatter to create table of contents
It would be great to be able to use the formatter to create an automated table of contents based on some recognized commented pattern. For example, I could begin each section of code with:
--******
-- Title of section
--******Then after using the formatter it would see the commented section and add the line number for each section in the beginning of the script. I imagine something similar to MS Word's auto generated table of contents.
1 vote -
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)
2 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 -
Stop OPENJSON after CROSS APPLY from showing up on new line
I have included a Sample SQL script. This script shows the desired formatting. I can't find any way to prevent the OPENJSON from being sent to a new line. For example:
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY OPENJSON(OJ.Value)
WITH (ID int) AS CAOJbecomes
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY
OPENJSON(OJ.Value)
WITH ( ID INT ) AS CAOJ2 votes -
Allow block comments /* SQL Prompt formatting off */ to disable T-SQL formatting
SQL Prompt should allow block comments /* SQL Prompt formatting off */ to disable T-SQL formatting.
Single line comments are a pain when tuning queries. I would always use block comments in my code except when I don't want SQL Prompt to not mess with certain T-SQL it does not format to my standards.
Blocking formatting should support both type of comments.
/* SQL Prompt formatting off */
-- SQL Prompt formatting off5 votes -
SQL Prompt Support for Azure Synapse (Azure SQL Data Warehouse)
Please add support for
SQL Prompt Support for Azure Synapse (Azure SQL Data Warehouse)26 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 -
Separate ALIAS Alignment - table vs. column
Aligning based on column-alias makes for much better readability. When turned OFF, because some long-named table's alias pushes the TABLE-alias way to the right, all other table aliases follow it...into the NON-VISIBLE area (when using multiple vertical tabs).
Please SEPARATE these into TWO options:
. Align Column Aliases - on/off
. Align Table Aliases - on/offTHERE IS A BUG TO FIX HERE TOO: If a UDF is bounded by "--SQL Prompt formatting off/on" the TABLE ALIAS position REMAINS as if the UDF's alias was in it's SQL Prompt position, NOT where the excluded code has it! NASTY.
You could…
3 votes -
Separate UDF Formating from Built-in in "Function Calls"
We cannot treat UDF parameter listing/indentation in similar vein to Stored Procedure call formatting. All "Functions", be they UDF or built-in, are lumped into the same four RESTRICTIVE options on the "Function calls" page, and we have no "parentheses style" options for them.
We need:
1. Separation by type (UDF vs. Built-in).
2. Global ==> Parentheses, to apply to UDFs, by our choice.Thanks.
1 vote -
Have Formal SQL Actions be included in the formatting style file.
Have Formal SQL Actions be included in the formatting style file. This way when a team shared a standard we do not have to share the file and screen shots of the Options menu to manually sync to maintain team consistency on code checkin.
2 votes -
Add quotes and commas function with commas before
Please can the "Add quotes and commas" action conform to the current active style's Commas setting?
So if the setting is "Place commas before items", then the action should also place the commas before.
At the moment, I have to run a Format SQL action after using Add quotes and commas, which is cumbersome.
1 vote -
Make the "Enclose identifiers within square brackets [ ]" option persist
Currently in Visual Studio the option to "Enclose identifiers within square brackets []" option will be set to true on startup requiring a user to turn it off every time they load Visual Studio.
This option when set to false should remain that way even after a restart of Visual Studio the same way it does in SSMS.
2 votes -
Aliases Postfixes to ignore
Similar to the "Prefixes to ignore" option in Options > Inserted code > Aliases, could we have a "Postfixes to ignore" option to allow use to set words at the end of a tablename to ignore when generating aliases.
Currently I have to keep the custom aliases list up to date, whereas this would do that automatically.
1 vote -
Multi Line Comment shortcut
Add /* / multi line comment shortcut for highlighted code in text editor. See SSMSBoost pro for example CTRL+.
1 vote -
Fix closing quote for 'N' strings
When typing a string preceded with 'N' (like N'string value'), when you type the closing quote it gets doubled. Hard to explain, but easy to reproduce. Just type these two statements into SSMS to see the difference:
SELECT 'Bill' As FirstName
SELECT N'Bill' As FirstName1 vote
- Don't see your idea?