Source Control Crashing SSMS
micadee_87
Posts: 1 New member
Hi,
I am linking Redgate Source Control 7 to 6 databases across 2 environments (QA and Dev). Source control works fine on all databases bar one. Each time source control refreshes the list of items to be committed, it crashes on this one database.
I have compared comparison options and filters on all databases in Source Control and all are the same. I have also tidied up working folders such as working bases and transients. I have also unlinked and relinked the database several times. I have repaired Source Control 7 and have even gone as far as uninstalling and reinstalling.
Would anyone have any ideas why Source Control would crash on just one database out of 6? I would also note that source control works fine on the same database in a different environment, i.e. it crashes on database XYZ in QA but works fine on database XYZ in Dec).
Redgate Source Control 7.7.0.18212
SSMS 19.1.56.0
Thanks in advance
I am linking Redgate Source Control 7 to 6 databases across 2 environments (QA and Dev). Source control works fine on all databases bar one. Each time source control refreshes the list of items to be committed, it crashes on this one database.
I have compared comparison options and filters on all databases in Source Control and all are the same. I have also tidied up working folders such as working bases and transients. I have also unlinked and relinked the database several times. I have repaired Source Control 7 and have even gone as far as uninstalling and reinstalling.
Would anyone have any ideas why Source Control would crash on just one database out of 6? I would also note that source control works fine on the same database in a different environment, i.e. it crashes on database XYZ in QA but works fine on database XYZ in Dec).
Redgate Source Control 7.7.0.18212
SSMS 19.1.56.0
Thanks in advance
Answers
Thank you for reaching out.
This appears to be related to the support ticket that you had opened. As mentioned in the ticket, it is difficult to diagnose the issue without copies of the Working Base, Transients, and, SQL Compare snapshots of the database. As a reminder, the scripts folder does not contain any transactional data; at most, it might hold static data if that feature is being utilized.
If you're able to provide those, I'll be happy to re-open the ticket to continue troubleshooting. Otherwise, there's not much else we can do.