Comments
10 comments
-
@configio
For the same comparison, how long did it usually take prior to the upgrade? Did you use the same comparison's options? https://documentation.red-gate.com/sc13/troubleshooting/common-issues/comparison-seems-slow -
For the same comparison before the upgrading to the new version would take seconds
-
As for the link you posted, I already had the option unchecked.
-
I seem to have it working now.
I previously uninstalled/reinstalled the same version and they didn't fix it so I uninstalled again went back to version 12 and verified that it was working again. Then I upgraded to the latest version and it seems to be working again. -
Thanks for the updates and glad to know it's working fine now.
-
I am having the same problem with version: 13.7.11.10438. "Calculating work to do" step takes 15min to finish (it was <1min before upgrade).
-
We are seeing a similar performance hit as configio in 13.7.7.10021 - no errors in log, though
-
I am also having the same issue, "Calculating work to do" keeps spinning. Any solution?
-
Me too, glad I found this forum post. When I uninstalled and reinstalled it brought me back to 13.3.2.5875, which is running much quicker with the "Calculating work to do" screen
-
Problem persists even after Red Gate Support claim that new version will fix performance. Unable to use Compare for more than a month
Add comment
Please sign in to leave a comment.
I've done following:
1. reboot
2. uninstall/reinstall
3. I turned on verbose logging and get a bunch of errors about "Failed to resolve item"
e.g., Failed to resolve item RedGate.SQLSourceControl.Engine.Interfaces, Version=7.0.18.9209, Culture=neutral, PublicKeyToken=7f465a1c156d4d57. Requesting assembly = RedGate.SQLSourceControl.CommonUI, Version=7.0.18.9209, Culture=neutral, PublicKeyToken=7f465a1c156d4d57. File C:\Program Files (x86)\Red Gate\SQL Compare 13\RedGate.SQLSourceControl.Engine.Interfaces.dll not found.
Update:
I did a compare where there was a single change between 2 databases and let it sit there at the "calculating..." step and after about 4 minutes it did finish.
Perhaps this is just a performance issue? On my first attempt with several differences, I eventually killed it after about 20 minutes.