Comments
Sort by recent activity
Found the setting [image] SQL Prompt > Options > Connections > Load referenced databases option selected / comments
Found the setting SQL Prompt > Options > Connections > Load referenced databases option selected
reverting last commit removes error - recommitting same objects brings error back / comments
reverting last commit removes error - recommitting same objects brings error back
seems i logged a similar issue in 2018 but i cannot open the link in my discussion history anymore to see how it was resolved. but i'm guessing i have to go into git and delete the object as if it never existed and then init it. will lose history but at least the rest of the repo will work / comments
seems i logged a similar issue in 2018 but i cannot open the link in my discussion history anymore to see how it was resolved.but i'm guessing i have to go into git and delete the object as if it n...
JoshH said:
Hello, Have you tried unlinking and relinking the database? I've seen this same error in other tickets and this has resolved their issues.
Thanks for the advice Josh. I did try this but still the same issue. Seems to ring a bell this, so I will trawl through my previous posts. / comments
JoshH said:
Hello, Have you tried unlinking and relinking the database? I've seen this same error in other tickets and this has resolved their issues.
Thanks for the advice Josh. I did try ...
Hi Peter, Thanks for your response, I was on 18.12.1 (SSMS). Two colleagues both on this version also, one experiencing the same issue and one not. However, I have now upgraded my SSMS to version 19.3 to be able to work and avoid the crashing. I have not as yet found a window to setup Source Control against this version. James / comments
Hi Peter,Thanks for your response,I was on 18.12.1 (SSMS). Two colleagues both on this version also, one experiencing the same issue and one not.However, I have now upgraded my SSMS to version 19.3...
So having moved off SSMS 18.12 to 19.3 prompted by this issue, I've updated SQL Prompt today and now introduced this issue into 19.3 Ironically, because i'm now on 19.3 and having to uninstall and re-install redgate products to get them to show in the new version, I am prompted to close SSMS to allow the update, but after you close SSMS you actually see the second SSMS instance in the 'Quit applications' screen. And have to go and close that as well before being able to install. [image] Is there a fix in the works for this issue raised at the start of this year? / comments
So having moved off SSMS 18.12 to 19.3 prompted by this issue, I've updated SQL Prompt today and now introduced this issue into 19.3Ironically, because i'm now on 19.3 and having to uninstall and r...
I have this issue as well. I'm in the habit of closing down my SSMS periodically and reopening to start afresh on a separate piece of work. Wondering why i've got 2 SSMS instances open. And it appears that the closure is prompting a delayed restart of SSMS. / comments
I have this issue as well. I'm in the habit of closing down my SSMS periodically and reopening to start afresh on a separate piece of work. Wondering why i've got 2 SSMS instances open. And it appe...