11.5.4.27450 - Released on 10 September 2026 (Standalone installer)

Features

• Changed the Get Query Execution Plan MCP tool in Redgate Assistant to allow it to accept T-SQL snippets (including query editor window selections), rather than limiting it to the entire T-SQL in the open editor window.
• The default delay before AI code completion requests a suggestion after you stop typing is now 2 seconds (previously 500 milliseconds). This applies to new installations; existing users keep their current delay and can adjust it as they prefer from 500 milliseconds upwards in SQL Prompt > Options > Prompt AI.

• Added a Fix Code Analysis Issues MCP tool to Redgate Assistant, which runs your code analysis rules over the T-SQL in the open editor window and returns an auto-fixed version.

Fixes

• Expanded SQL Prompt options locking fix from previous release to cover all disk I/O options operations and not only save.
• Fixed enablement and disablement of code suggestions in main menu (SQL Prompt > Enable suggestions) and SQL Prompt options (SQL Prompt > Options... > Suggestions > Behavior > Show code suggestions) to prevent stale data that could cause faulty behavior in schema-dependent features (e.g. database refactorings, code analysis, Prompt AI, Redgate Assistant, etc.) until the next IDE restart.
• Fixed an issue where SSMS process lingered after application shutdown.
• Fixed race condition that could cause a An attempt was made to transition a task to a final state when it had already completed when loading the schema for a newly connected database.
• Fixed bug that could cause timeouts and empty results for non-empty databases when calling schema dependent tools in Redgate Assistant and Prompt AI.
• Fixed bug that caused all DB object names to be returned instead of only those of the type being searched for when querying Redgate Assistant MCP tools without a specific search term (e.g. list all tables or list all views).
• Fixed an issue where List Code Analysis Issues menu option displayed an empty window in Visual Studio 2026.

• Fixed an issue where SQL Prompt repeatedly displayed the Azure authentication dialog and consent screen after the user cancelled authentication.

11.5.3.27255 - Released on 01 September 2026 (Standalone installer)

Features

• Added Support for Select in Object Explorer feature for Tables, Stored Procedures, Functions and Views in Microsoft Fabric databases.

• The Check AI Availability button is now available at all times (previously required an open query editor window). An associated popup, where you can launch Prompt AI and Redgate Assistant, is added to improve usability.

Fixes

• Fixed an issue where SQL Prompt options could fail to save if the options file was temporarily locked.
• Fixed an issue where aggregate functions like Max and Min showed the return type as Numeric instead of generic.
• Fixed an issue where the SQL Prompt was crashing when using Table Design in SSMS.
• All Redgate Assistant tools now provide richer detail if something goes wrong -- similarly to what was done for the query execution plan in version 11.5.2.27061 -- which can save time and lead to better diagnosis.
• Fixed an issue where SQL Prompt did not add square brackets to identifiers in the WINDOW clause.
• Fixed an issue where SQL query tab retained its text color after being disconnected from the server.
• Fixed an issue where open new query in SSMS 20 would prompt for repeated authentication when connected to Azure database using MFA.

• Fixed an issue in SQL Prompt bulk actions where the text color was not applied correctly in dark mode.

11.5.2.27061 - Released on 21 August 2026 (Standalone installer)

Fixes

• Unsupported query execution plan T-SQL statements (e.g. CREATE TABLE) or scripts with multiple GO batches will now issue an explicit error when being processed in Redgate Assistant.
• Fixed an issue where background coloring was not applied correctly for SQL History 'DeleteConfirmation' and 'Rename Query' window.
• Redgate Assistant UI will now provide several suggestions if Redgate licensing authentication failed or if the backend could not connect within the allowed time window (e.g. confirm all prerequisites are met).
• Fixed a bug where talking to Prompt AI might cause SSMS to freeze.

11.5.1.26824 - Released on 14 August 2026 (Standalone installer)

Fixes

• Fixed an issue where the Open In Excel option from the result grid was throwing an error.

11.5.0.26718 - Released on 11 August 2026 (Standalone installer)

Features

• Added a button to open the Redgate Assistant window in SSMS toolbar.
• Added an option to open the Redgate Assistant window in SSMS query editor window context menu.
• Changed the model for AI autocompletion from Alibaba Cloud's Qwen3-Coder to Mistral AI's Devstral 2.
• The Redgate Assistant chat window will now automatically detect state changes without requiring to be closed and reopened.
• Turning on Prompt AI now also turns on Redgate Assistant if it is not already enabled.

• Added information on all the new AI features in SQL Prompt. Check it out in SQL Prompt > Help > What's new in SQL Prompt? menu option.

  Fixes

• Fixed an issue where SELECT statements in views containing Common Table Expressions (CTEs) were formatted incorrectly.
• Fixed an issue where users authenticated with Microsoft Entra MFA were repeatedly prompted for re-authentication on Visual Studio 2026
• Fixed an issue where Redgate Assistant chat shows up as a blank window if the user is logged out when opening SSMS.
• Fixed an issue that could incorrectly throw an ObjectDisposedException when Redgate Assistant's MCP server was stopped.
• Fixed an issue that caused an execution timeout when viewing the script of a database object in Azure Synapse.
• Fixed an issue where function call formatting was not getting applied to JSON_OBJECT and JSON_OBJECTAGG.
• Fixed an issue where JSON_OBJECT did not suggest the ABSENT ON NULL or NULL ON NULL clauses.
• Fixed an issue where renaming an alias in a CTE could result in mismatched references and invalid SQL.

• Redgate Assistant will now provide better and faster guidance if there are any issues retrieving the query execution plan (e.g. malformed T-SQL, database mismatches, etc.) for the current active query.