Comments
Sort by recent activity
To prevent this SSMS stuck loop, remove file SqlHistory.db from user "\AppData\Local\Red Gate\SQL Prompt {version}" folder. SQL Prompt will generate a new empty one, and you can continue with SSMS. As that is SQLLite database, you could also use DB Browser for SQLite to find the problem in the history and try to remove it. / comments
To prevent this SSMS stuck loop, remove file SqlHistory.db from user "\AppData\Local\Red Gate\SQL Prompt {version}" folder. SQL Prompt will generate a new empty one, and you can continue with SSMS....
Seems to be a problem still, as I did run to this today. SSMS goes totally unresponsive, and only end task will work. As next time this happens again, SSMS is totally out of reach. How to bypass history opening? / comments
Seems to be a problem still, as I did run to this today. SSMS goes totally unresponsive, and only end task will work. As next time this happens again, SSMS is totally out of reach. How to bypass hi...