Comments
Sort by recent activity
Hi all - confirming that we are starting to see releases of our Toolbelt products with SSMS21 preview functionality. It is noted that this is in preview and not officially supported until SSMS21 GA is available. There will be official notifications as our products officially support SSMS21 through our blogs, release notes & product requirement documentation. SQL History & SQL Prompt will install into SSMS21 (preview) for release V10.16.6 https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.16.6.15646.exe There are some one-time changes to make as SSMS21 is VS based. Thank you to @RightTurnsOnly for sharing the link: Refer section - Running SQL Prompt with SSMS 21 Preview https://documentation.red-gate.com/sp/getting-started/installing-and-running-sql-prompt We are looking forward to announcing other products joining SQL Prompt in SSMS21 / comments
Official comment
Hi all - confirming that we are starting to see releases of our Toolbelt products with SSMS21 preview functionality. It is noted that this is in preview and not officially supported until SSMS21 GA...
Hi NSRjecross Thank you for reaching out on the Redgate forums regarding your odd SQL Prompt behaviour. That initially sounds like SQL Prompt’s Find Invalid Objects feature is getting confused due to name caching or some kind of indexing issue, leading to incorrect object names in the script preview. Here are some possible suggestions to clear this variance:
Force Refresh SQL Prompt's Cache
In SSMS, go to SQL Prompt → Refresh Suggestions (or Ctrl + Shift + D ).
This should clear cached object names and reload them.
Manually Verify the Views
Run: SELECT name FROM sys.views WHERE name LIKE '%Vein%';
Check if any unexpected naming inconsistencies exist at the database level.
Check for Ghost Entries in sys.sql_modules
If the objects were renamed recently, stale metadata could be an issue.
Run: SELECT object_id, definition FROM sys.sql_modules WHERE object_id IN (SELECT object_id FROM sys.views);
See if any unexpected names appear.
Try SSMS’s Built-in Scripting InsteadIf SQL Prompt's Find Invalid Objects is unreliable, use SSMS:
Right-click the invalid view → Script as ALTER
Compare with what SQL Prompt generates.
Check SQL Prompt’s Log File for Errors
Logs are usually in %LOCALAPPDATA%\Red Gate\SQL Prompt\Log\ .
Look for errors or inconsistencies.
Test with a New SSMS Session
Restart SSMS and load Find Invalid Objects again.
If possible, test on another machine to rule out local corruption.
/ comments
Official comment
Hi NSRjecross Thank you for reaching out on the Redgate forums regarding your odd SQL Prompt behaviour.That initially sounds like SQL Prompt’s Find Invalid Objects feature is getting confused due ...