- I have a SELECT with some comments after the column aliases (e.g. in column 80)
- I comment a line out
- I let SQL Prompt format the statement
-> the outcommented line will be moved to column 80 too, which makes it hard to find / read etc.

Solution:
- only align it when there is some regular SQL code before the comment (e.g. a column, table, condition ...)
- or there are only whitespaces before the comment and it starts (roughly) equal as the comment one line above (multiline comments)
- and / or do not align it, when after the comment comes regular SQL code (temporary uncomment the line and check the code after it; when regular SQL then align it, as when it would not be commented out and place the -- or /* just before the regular position)

I would like an option that can disable the tab key from popping up the suggestions menu/popup. When I am formatting my code in SSMS using the tab key to line up various items, each time I hit tab, the suggestions menu pops up.

MOST of the time this isn't an issue other than ignoring the pop-up. Occasionally, based on what is in the code I am formatting, when I hit tab it will auto select an item in the suggestions, and the second tab will insert the suggestion. This slows me down quite a bit.

In the mean time, I have fixed this by disabling the tab key from inserting a suggestion...however, I don't like this because I prefer to use the tab key for that. I just don't want the tab key popping up the suggestions in the first place.

I've uploaded a sample query to Pastebin that demonstrates the issue: https://pastebin.com/0nJPWrvx

My settings file is here: https://pastebin.com/iwb4QMYN

I'd love it if you could fix two things about this.

1) The indentation of the "NOT IN" clause on lines 17-18 is atrocious. The issue appears to be that it's aligning to the wrong SELECT statement.

2) I want to wrap my subqueries with more whitespace. I think adding an option to indent the subquery on dedicated lines would work, and the result would look like they're nested in curly braces like you might see in scripting languages or C#. The upside to this is that it's very easy to pick out the subquery's alias.

Thanks!

Hi RG - using the latest sql prompt. its really good but could I request two enhancements please.

1. on the casing can we separate the 'as' keyword from the others. i.e. "SELECT", "FROM" etc have one rule applied but "AS" can be set separately (i like to have all my 'as' statements in lower case)

2. could there be an option to add a column as 'alias' to every column in a SELECT statement (defaulting to the column name). This would do the donkey work and then the sql developer could go and add in friendly names afterwards using the nicely aligned structure that sql prompt has added.

if i'm adding friendly names to a few columns in a query i end up adding "as 'alias' " to all of them so everything is aligned.

cheers
ben

I will often use a block comment /* */ around code in the current script that I don't want to execute by default when I press F5. To execute the code in the block comment, I must select the content of the block comment and press F5.

This is inefficient with the keyboard for comment blocks that are many lines of code: Locate the top of block comment, hold SHIFT, DOWN-DOWN-DOWN-etc..., F5)

My suggestion is to allow CTRL-A (or similar) to select the content of the block content that the cursor is currently in. Followed by F5, this would execute the commented code.

separate options for formatting different types of lists, which are currently all formatted with the same settings:
* parameters when defining a function
* parameters when calling a function
* select
* insert column list

Option to always put a newline after a multi-line case statement. e.g.
select o.name, o.object_id, o.principal_id, o.schema_id, o.parent_object_id, o.type, o.type_desc
, friendly_object_type = case o.type
when 'S' then 'system table'
when 'D' then 'default'
when 'V' then 'view'
end
, o.create_date, o.modify_date, o.is_ms_shipped, o.is_published, o.is_schema_published
from sys.objects o
order by friendly_object_type

instead of

select o.name, o.object_id, o.principal_id, o.schema_id, o.parent_object_id, o.type, o.type_desc
, friendly_object_type = case o.type
when 'S' then 'system table'
when 'D' then 'default'
when 'V' then 'view'
end, o.create_date, o.modify_date, o.is_ms_shipped, o.is_published, o.is_schema_published
from sys.objects o
order by friendly_object_type

Option for multi-line insert statements: option to wrap lines after corresponding items rather than after exceeding the length threshold, e.g.
create table #foo (one int, two int, three int, four int, five int, six int, seven int, eight int, nine int, ten int, eleven int, twelve int, thirteen int, fourteen int, fifteen int, sixteen int)

insert #foo (
one, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve
, thirteen, fourteen, fifteen, sixteen
)
values (
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
, 13, 14, 15, 16)

instead of

insert #foo (
one, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve
, thirteen, fourteen, fifteen, sixteen
)
values (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)

Option for insert statements: vertically-align corresponding items in insert column list and values/select column list, e.g.
insert #foo (
one, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve
, thirteen, fourteen, fifteen, sixteen
)
values (
1, 2, 3, @four, 5, 6, 7, 8, 9, 10, 11, 12
, 13, 14, @fifteen_something, 16)

We really like the ability to collapse if statements to a single line when short but we'd prefer the addition of a general option to suppress empty lines between one line statements. For example today we get:

-- check parameters
if @FormRecordSID is null set @blankParm = '@FormRecordSID';

if @FormSchemaName is null set @blankParm = '@FormSchemaName';

if @FormTableName is null set @blankParm = '@FormTableName';

if @FormDefinition is null set @blankParm = '@FormDefinition';

if @Response is null set @blankParm = '@Response';

and we would prefer:

-- check parameters
if @FormRecordSID is null set @blankParm = '@FormRecordSID';
if @FormSchemaName is null set @blankParm = '@FormSchemaName';
if @FormTableName is null set @blankParm = '@FormTableName';
if @FormDefinition is null set @blankParm = '@FormDefinition';
if @Response is null set @blankParm = '@Response';