Comments
1 comment
-
Official comment
Hi Bryan,
Thanks for reaching out to Redgate Support regarding your Source Control issues. I was able to discuss this a bit further with the developers and they have concluded that this does appear to be the newly expected behavior from Source Control in SSMS 21. While the behavior you were seeing was indeed not nominal when comparing to older versions of Source Control, with SSMS 21, the initial loading behavior has changed. As a result, the SOC page does not auto load when SSMS 21 starts. This affects the initialization of certain events responsible for updating icons. Now (SSMSv21 onwards), these events get triggered whenever the SOC page is opened manually or the SOC button is clicked.
Workaround options for you include the following. (Either of these steps will trigger the event and then the connected database will be identified as expected)
- In SSMS 21, connect to DB server then open(Click on) SOC tab and Refresh the DB server.
- In SSMS 21, connect to DB server then open(Click on) SOC tab, Disconnect, and Reconnect the DB server.
- Cancel the connection dialog when SSMS 21 opens, open the SOC page first, and then connect to the desired DB server.
Let me know if you have any follow up questions or concerns.
Add comment
Please sign in to leave a comment.
SSMS 21.2.5 and SQL Source Control 8