I work on the same databases on a regular basis. Many do not have foreign keys and do not used identically named column names in tables that I'm joining.

I repeatedly have to specify the same several columns in the join condition.

I'd love a way for SQLPrompt to either remember join clauses I've previously used, or allow me to specify default join conditions for pairs of tables (or both).

When I right click in a Stored procedure SSMS hangs, and it takes too long for the menu to show up. Please review Red Gate Source Control for the added entries in the menu to improve performace

We have code littered with IIFs that we would like to convert to CASE. Logically this is straightforward, but achieving it swiftly is proving more difficult. A regex takes care of the simple ones, but the ugly ones with nested functions across multiple lines and all sorts are proving far more difficult.

Would it be possible to add a feature to SQL Prompt to refactor IIFs into CASE statements? Thanks

When I use SSMS to query the data and use "open in Excel", the exported “. Xlsx” is too old, which will cause the digital content to become 0 after WPS or other form software is opened. This problem has lasted for a long time. I hope your company can upgrade and handle it accordingly. Thank you Very Much

This is essentially the same as a forgotten SSMS request over here: https://feedback.azure.com/forums/908035/suggestions/32896039

It would be incredibly useful to be able right-click on a server-node in the Registered Servers list and change/set the connection for the current document window to that. You already have a custom context menu item in there ("Tab Color (Server)", so that hurdle is gone.

This idea is related to these, but not quite the same. In both cases, it seems they don't know about the Registered Server functionality, so they're basically asking for this idea, plus for you to re-implement that entire feature.
https://redgate.uservoice.com/forums/94413/suggestions/40385740
https://redgate.uservoice.com/forums/94413/suggestions/13425135

No CREATE SQL is displayed in the suggestions window when hovering over any CLR objects, or scripting the object as alter. The code returned is just a comment saying:

-- No creation SQL available for this object type

The CREATE/ALTER statement can easily be built by querying the relevant system tables. SSMS does it when you script the object and other Redgate products such as SQL Compare and SQL Source Control do it just fine, not sure why SQL Prompt would have been left out.

I often use the Ctrl-F12 feature to jump to an object in the object Explorer, however this doesn't work if the object has been renamed, or was just recently created. In those cases I need to manually refresh the object Explorer before I can use F12. Perhaps the F12 feature could do that for me? (or prompt if it can't find the object)

Many time SQL Prompt doesn't work for me because it thinks I use the database mentioned in the last USE statement in the SSMS query window. This is incorrect and confusing since I change the database in the SSMS dropdown without explicit running any USE statement. SQL Prompt should know what database is selected in the dropdown and offer objects from the selected database,

When scripting an object from the Object Explorer, for example with right-click -> Modify or Script as... CREATE To, the tab created has a default name determined by SSMS, for example "SQLQuery45 - database01.sql". It would be great if this naming was the same as when you click F12 on an object name in a script, where the new tab is named the same as the object, for example "dbo.SomeStoredProcedure - database01.sql".

PERSIST_SAMPLE_PERCENT is a new feature in SQL Server 2016 SP1 CU4.

SQL Prompt does not think this is a valid UPDATE STATISTICS statement:

UPDATE STATISTICS dbo.MyTable(MyStat)
WITH FULLSCAN, PERSIST_SAMPLE_PERCENT = ON;

It is valid and the correct syntax. SQL Prompt should be updated to format this correctly.

Pressing control+A will select an entire document.
I'd like a control+k, control+A to select the current statement based on cursor position.

This would enable me to do a few things:
01. Format the current statement with a hotkey
02. Copy or cut my current statement so I can paste it somewhere else

Thanks.

Would LOVE SQL Prompt to do a silent upgrade, without the need to "promote" admin privledges, nor close Visual Studio / SSMS. Love the upgrades, but they are frequent, and the installation process is disruptive.

Please add support for Visual Studio Preview versions. We frequently work in those and SQL Prompt Pro specifically is not available.

Add an option to have the DISTINCT keyword appear at the top of the suggestions list when the first few characters (DIS, DIST) are typed, ahead of any column name suggestions. Nearly every time I type DIS or DIST, I want the DISTINCT keyword and not a column name that begins with the same letters.

I would like to request a one-click option (or at least an out-of-the-box Format Style) that would minify either the selected line(s) or entire code in the current session.

This would be really helpful when writing a non-dynamic TSQL that will need to be turned into dynamic to save on (VAR)CHAR limit (4000/8000).

Thank you

We have a database that has Foreign keys, but doesn't have them set up as such via it's schema. It's a legacy system and there are technical reasons we aren't going to go back in after the fact and define them. I can't imagine we're the only place to ever run into this, it would be nice to have some sort of config file where you could manually set up things like that.

When collapsing CASE expressions shorter then XXX, the END has no space if there is a preceding parenthesis.

Example1 = CASE t1.Col004 WHEN 1 THEN t1.Col006 END,
Example1 = CASE t1.Col004 WHEN 1 THEN TRY_CONVERT(int, t1.Col006)END

When collapsing CASE expressions shorter then XXX, the END has no space if there is a preceding parenthesis.

Example1 = CASE t1.Col004 WHEN 1 THEN t1.Col006 END,
Example1 = CASE t1.Col004 WHEN 1 THEN TRY_CONVERT(int, t1.Col006)END,

Merge Command Formatting

For MERGE commands there is no way to make the conditional requirements with 'ON' follow the same style as JOIN's ON. I noticed back on 5/17/2017 there was a closed 'Merge command formatting options' through the User Voice, stating that an experimental feature was available for SQL Prompt 7.4. What happened? In my 10.1.7.15015, within the formatting styles, there is no area for MERGE like there is for JOIN.