Activity overview
Latest activity by CLDS
It only seemed to work for a matter of hours. Once I left a new comment on a script, the issue came back. I am starting to wonder if it depends on which DB server I am connection to, as this issue didn't come about earlier when I was predominantly working on another DB server connection. It might have become a noticeable issue in recent weeks as I have started using this specific DB connection more. I will have to wait and see whether working on another connection ends up keeping the issue away. / comments
It only seemed to work for a matter of hours. Once I left a new comment on a script, the issue came back. I am starting to wonder if it depends on which DB server I am connection to, as this issue ...
Hello David, Thank you for getting back. I don't believe that there have been any changes to either. As I am between pieces of work, I have just tried re-installing SQL Prompt again, this time also deleting the main persistent folder I have seen: C:\Users\<user>\AppData\Local\Red
Gate I will see whether it stays working this time. Cheers, Scott / comments
Hello David,Thank you for getting back. I don't believe that there have been any changes to either.As I am between pieces of work, I have just tried re-installing SQL Prompt again, this time also d...
Hello @TomW This is happening for me now. I've tried updating SSMS (now v18.11.1) and re-installed SQL Prompt (now v10.11.9.27382). I think that @TheoL has narrowed in on the observations further than I have so far - I think their description matches what I am seeing. The non-alpha key that I've noticed triggering it has been '-' due to me regularly commenting since the time the issue began in the last week, rather than creating variables. I would love to know if there is a solution, otherwise I will have to stop using SQL Prompt after a trouble free first ~9 months personally. Perhaps a cache or something that can be cleared? Cheers, Scott / comments
Hello @TomW This is happening for me now. I've tried updating SSMS (now v18.11.1) and re-installed SQL Prompt (now v10.11.9.27382).I think that @TheoL has narrowed in on the observations further th...