Issue: SQL Prompt Queries > History > Restore open queries
jsreynolds1
Posts: 96 Silver 2
This has been happening the last couple of hotfix releases, but each time SSMS is closed with open queries, and re-opens, I get copies (sometimes two or three) of each previous tab. So If I closed with 3 tabs open, I might re-open SSMS and get 6 or 9 - 2 or 3 copies.
SQL Prompt 10.15.1.1422 & SSMS 20.2
SQL Prompt 10.15.1.1422 & SSMS 20.2
Tagged:
Best Answer
-
cperez Posts: 56 Bronze 2@Jaragoth , @AdamGojdas , @jsreynolds1
Thanks all for your patience on this issue.
Please upgrade Prompt to the latest version of 10.15.3 as this issue has been remediated in that version.
https://download.red-gate.com/checkforupdates/SQLPrompt/
Cheers,
Christian Perez
Answers
Thanks for reaching out to Redgate Support. Fortunately, the behavior you are describing is a known behavior already under investigation by the development team. As soon as they release some remediation steps or a patch fix for this issue I will circle back here and update you further.
You can also keep an eye on the https://download.red-gate.com/checkforupdates/SQLPrompt/ for any subsequent releases.
One additional odd behavior. For the SQL code I work on we have all our sql objects, procs, views, functions, etc in source code files and work from them. We keep them in version control and apply the code from the source file to the DB for changes. When opening a source code file while having several others in tabs in SSMS open I have twice had the data overwritten in the newly open file from another file I had open. This behavior I have only seen in the last day but I was thinking it was related to the SQL Prompt re-opening feature. I have never experienced this before this week which was when I updated SQL Prompt. Not sure of what the details are to have caused it but I at least know it has occurred to make sure I don't save code from one file into another. Luckily our code is in version control so it is easy for me to identify the whole file changed but not something I am thrilled with occurring.
How can I disable the behavior in the meantime?
Deleting SqlHistory.db removed all my history but restored functionaltity.