After removing of SQL Code debugging features beginning with Management Studio 18, it would be quite welcome to have this feature in SQLPrompt.
Other competitors are already providing debugging.

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.

Allow more filtering options for populate tables with data tool.

My idea is for the SQL Compare tool: when the warnings are displayed, it would be helpful to be able to copy text of these warnings to deal with them

All setup-options, except "Manage Code Analysis Rules..." seems to also be available from the "Options..." menu, which is nice ...

At the moment a user is warned before executing a potentially dangerous operation.
However, junior devs might accidentally just press enter without thinking twice.
Please add functionality to PROHIBIT execution besides WARNING (like SSMS Boost has) so that junior devs can't make mistakes at all.
It would be fantastic if this would be possible.

Make the column picker the default tab when suggesting columns when the ursor is inside a select statement.

Consider a table
CREATE TABLE [dbo].[ItemGroups](
[Group] [VARCHAR](25) NOT NULL,
[Description] [VARCHAR](25) NOT NULL)

SELECT Group from dbo.ItemGroups ->

Incorrect syntax near the keyword 'Group'.

Would be nice to get a warning when a column name is a reserved word. Square brackets make the syntax valid but unnecessary if a column is named more accurately, e.g. ItemGroupCode

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.

In SQL Prompt, in the pop-up display for an object, allow drill down from an object reference in the popped-up display.

In the new feature showing dependencies, implement drill down (from the "uses" section) and drill up (from the "used by" section)

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.

Surround with, add to the list Select, Pivot, and I am sure there are more items like CTE

The way I work when creating complicated scripts is creating all the SELECT statements and then convert them to CTEs of my final query.
It would be nice if you could convert SELECT into CTE

Sometimes my SSMS crashes. The Crash recovery of the program is not good enough. Would love to see "auto save" option that will save the open queries to history each time I'm idle for few moments. It would be much easier to recover than reproduce

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 ...

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.

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)

It would be nice to search for multiple keywords in the Tab History. For example, I know I had a script to insert data from TableA to TableB, but I searching for TableA or TableB yields to much result (both are frequently use tables). Searching for "TableA, TableB" or "TableA*TableB" would be a good quality of life feature.

Using a shortcut to swap commented / uncommented lines in the sql script. This could be very helpful when we need to test (select / update) for the same source query.

Please check the screenshots

Thanks