Comments
6 comments
-
Could you take a look at the beta version of Compare 7 (you can find it on the beta forum, lower down the forum list)? We think we've fixed this problem for v7. -
I downloaded SQL Compare 7 beta, and ran the diff.
It seems to be fixed - worked fine.
Thanks!
Scott R. -
So - for those of us not wanting to use a Beta product in our production or critical development projects, when can we expect a fix for this bug in the 6.2 release(s)???
-
This applies to me as well...
The 7.0 beta application is notifying me with a dialogue window: "Thank you for evaluating SQL Compare. Your trial will end in 51 days.".... -
We purchased Sql Compare (6.2) several months ago.
It no longer works for us because of this bug.
The 7.0 beta trial version has now expired.
Please advise. -
We are currently install testing the release candidate for 7.0 and will hopefully have it out sometime in the next few weeks. If you have a current support contract, contact Support (support@red-gate.com) and they may be able to sort something out for you.
Add comment
Please sign in to leave a comment.
Until recently, I was able to run SQL Compare with no problems. But recently, I started getting an error when trying to compare two DBs (both containing the deployed assembly).
When I run the comparison, it does the following:
- Registering databases (completes successfully)
- Creating mappings (completes successfully)
- Comparing...
- "SQL Compare - Aborting" appears at the header.
- "Index was outside the bounds of the array." (bottom of screen)
If I delete the .NET stored proc assemblies from both databases, I can run the tool with no errors.