Hi, new feature with transparency on Ctrl in SQL Prompt 9.4.10 is extremely annoying, I'm using only Ctrl+Space to show intellisense. Please provide us option to disable this feature, or change key to Alt or Ctrl+something, this is really horrible, please fix it asap. I've to uninstall tool for now.

Options - Styles pane contains, for example, "Apply column alias style" and its drop-down. This does not belong as a universal style setting, among others.

Please move it to the "Formatting Styles" configuration dialog.

This is because many practitioners either do not know about the "alias = column" capability in T-SQL, or don't like it, or it's contrary to company standards. The ability to use this form, which IMO is more brain-friendly, ought to be on the Formatting page as it is, in fact, a significant style element.

Thanks.

I want to be able to keep my tab history open. I am rebuilding a lost development database and using search a LOT, but after I search, find a tab I want to look at more deeply or execute, the window disappears and my search predicate and place in the list of matching tabs is lost, so I have to enter search predicate and scroll back down each time. This is a VERY useful tool, but it would be so much more useful if I could just keep it open.

Current behaviour: let's say we're editing a multi-statement script. The cursor is in the middle of one of the statements. Some other statements in the script are broken (i.e. have invalid syntax) but the one under the cursor is perfectly valid. We hit Shift-F5, expecting the current statement to be executed. Instead, we get a syntax error on some other piece of the script half a mile down the screen.

Expected behavior: just run whatever is under the cursor and ignore all other parts of the script.

I would like to see the ability to copy a selected row or a number of cells in a grid, and add it to the clipboard as a transposed view of the record
with 2 columns (Column Name, Value) to allow results to be easily pasted into emails etc

example (simple result only the result values would need to be selected)
ID Name Activation Date
1234 John Smith 2018-01-14

output on clipboard

ID 1234
Name John Smith
Activation Date 2018-01-04

Some programming languages (we use FireDac in Delphi) use colon notation to declare variables. Eg

select * from table where id = :id;

Testing such queries in SQL Prompt forces you to change the query before and after testing and that is error prone.
It would be nice if SQL Prompt could handle this type of parameters by instead of raising an error show a "Enter parameter value" input box.

open source sql prompt's formatting module.

I'd like to vote for adding PE019 (Consider using EXISTS instead of IN) to the issues which can be auto-fixed.

It feels like the kind of re-write that would probably be simpler for a computer to do than a person.

Colors Option For Different Databases

I use two AD user accounts on a daily basis - a normal account and a "server admin" account (for server OS local admin and SQL instance sysadmin permissions). Hence, I run SSMS as either one or the other user. SQL Prompt settings (same goes for other Redgate tools) are saved per user, which makes it quite tedious, since after every setting change I have to export from that user and import to the other user.

Can you it an option for settings to be user independant (universal)?

It would be nice if we can turn off the auto update check for a new version on start-up. This check is happening in the Visual Studio database project and in SSMS. I'd like to disable it. Thanks!

Occasionally, developers working in SSMS accidentally leave transactions open. This causes big issues, of course. SSMS lets the user know if they try to close a tab with an uncommitted transaction, but only when the user tries to close the tab.

I would like a feature in SQL Prompt so that it lets the user know that they have an uncommitted transaction. SQL Prompt could prompt the user via a toast pop-up or coloring the connection tab or something

While using Shift-F5 to execute the current statement, any BEGIN TRANSACTIONS above your UPDATE are ignored, running it not in a transaction.
I shouldn't use Shift-F5 probably, but it's becoming a habit and could be very expensive when forgetting to highlight-execute.

Custom Warnings.
For example, we have juniors who are just starting out in the SQL server world, Id like to have warning for Select statements that do not have Nolock hints. As the juniors will never be running any updates and deletes, they only have read access, but currently sometimes people forget the nolock hints and start causing locks and so on.

It would be very useful to have the ability to define a color for certain database objects such as tables or columns. With that feature, objects could be marked individually and would be highlighted, for example columns with an index on them. Other users would be able to directly see this and take it into account in their query design for example. These settings should also be saved in the source control if desired.

I don't want to globally turn off warnings for UPDATE or DELETE without WHERE clause, but would like an authorization text that disables the warning in a given script:

-- Currently Warns:
DELETE FROM dbo.Person

-- Suggestion - comment would authorize the delete to not warn
/* Authorized */
DELETE FROM dbo.Person

Current formatting is:

CASE
WHEN 1 = 1 THEN
'Hello World'
END

I need the option to put the expression on the same line:

CASE
WHEN 1 = 1 THEN 'Hello World'
END

Is it possible to add a hard return after the /* comment */ block so code doesn't keep formatting after the comment

Currently:
/* comment */ UPDATE User
SET Modified = CAST('2018-12-20' AS datetime)
WHERE id = 255454

Suggestion
/* comment */
UPDATE USER
SET Modified = CAST('2018-12-20' AS datetime)
WHERE id = 255454