When setting a line wrap at a number of cheracters, I would like to get the line at that long, and then wrapped. Not at the first comma. For example currently I get:

select first_name
, last_name
, email
, phone_number
, country
, country_alias
, region
, gender

... but I want to get:

select first_name, last_name, email, phone_number, country
, country_alias, region, gender

When hovering over an object name to view its contents...the tab size used in the code is much larger than what is being used in SSMS. So the formatting of the preview is completely messed up.

Maybe a setting to configure the tab size? Or maybe it can look up what SSMS is using?

It would be nice if SQL Prompt had a way to add in the code DROP TABLE IF EXISTS #table for temp tables. Ideally it would add the statement immediately before the table is created from a CREATE TABLE or SELECT INTO statement.

Sometimes I set a variable equal to many strings concatenated together using the "+" syntax. When I format with Regdate, there is no option to wrap lines in this case. Everything ends up on the same line as the SET, so the lines often get very wide and go off screen.
It would be great if there was an option to wrap text if things got too wide horizontally.
One solution would be a setting to format concatenated strings like this:
SET @Variable = N'String1'
+ N'String2'
+ N'String3'

Allows you to define (on a per tab/session basis) a list of variables you would like to be declared before running the highlighted piece of SQL.

Reason: I like to put all of my "magic numbers" in variables at the top of the proc. This works great for code readability, but it's a pain to troubleshoot because now everywhere the variable is used, you need to copy that variable declaration above whatever code you are testing in order for it to work.

when stored procedures have variables with defaults, your auto complete intellisense does not set the default. for example, if the parameter @a is an int = 5 in the creation of the proc, your auto complete says @a = 0 --int

So i specifically excluded our "temp" schema from my suggestions and it works brilliantly, however, when specifically want that schema, after completing the schema name it should show me the suggestion within that schema? -
Currently my options are to remove the "don't show suggestions" for the temp schema and then add it again after this session.

I often need to work with data sets from Excel. Instead of doing a whole "Import Data" process I would like to copy from Excel & paste into SQL Management as a temp or persisted table.

I like to get clever with snippets, and it would be great to be able to create dynamic snippets for different circumstances by being able to nest one snippet within the creation script of another. That way I can parse individual functionality in different snippets, but build them together to create more complex dynamic snippets without having to maintain the same basic code in multiple individual scripts.

I could see this working simply like:

snippet1:
DoThing;

snippet2:
$snippet1$
DoMoreThing;

At the moment to purge old tabs you need to open the tab history window and scroll to a certain point and right click and choose "Remove tabs older than this"

This can be a bit tricky so instead could we have a button (perhaps in options?) that will prompt you for a date and purge items last closed before that date.

Support request #137199: Provide an option to indent AND/OR entries in a WHERE clause to line up indented, but leave AND/OR entries directly underneath ON clauses:

SELECT
        t1.col5
        , t2.col6
FROM
        table1 t1
        INNER JOIN table2 t2
                ON t1.col1 = t2.col1
                AND t1.col2 = t2.col2 -- AND is directly below ON clause
WHERE
        t1.col3 = 'Test'
        AND t2.col4 = 5 -- AND is indented underneath WHERE

Highlight of today was when I ran

DROP USER MyUser

In the wrong (production) database.

Please add a warning to SQL Prompt, like your
"You're about to execute a DELETE statement without a WHERE clause"

When you run a DROP USER or a DROP LOGIN statement on a production server. Not only does the user or login disappear, but also all rights granted to the user.

Maybe add the question “are you in the correct database?”

If a View looks like
SELECT TOP(n) FROM x ORDER BY x.clumn
SQL Prompt shows issue EI030 although the ORDER BY is vital for the TOP (n) clause

SQL Prompt fails badly in formatting window functions. As these are present at least since SQL 2014, SQL Prompt should be able to interpret them and format them accordingly.

Example:

I would format the LAG() function as follows:

SELECT
myColumn AS realColumn
,LAG(myColumn, 1, 0)
OVER (
PARTITION BY someColumn
ORDER BY anotherColumn) AS calculatedColumn

Try this with SQL Prompt - it's result is not very nice...

Would it be possible to treat the 'LIKE' operator the same as '=' in the Expressions\Operators settings so they are all aligned?

select AddressID
from Person.Address
where ModifiedDate
between dateadd(month, -6, getdate())
and getdate()
and City = 'Bothell'
or left(PostalCode, 2) like 'CB%'
or PostalCode = @prefix + @suffix