Activity overview
Latest activity by atedw
Sorry it has taken me so long to reply to this...
I tried to enable logging with SQL Compare, but really didn't capture anything of use. However, I believe I may have discovered how this is triggered.
I think I have determined that this problem occurs as a result of a particular chain of events from the interaction of three (3) of the apps in the SQL Toolbelt. We use the latest version of all the apps in the suite of tools. In addition, I am using SQL Server 2008 R2 SP1 on the Windows 7 Enterprise PC at my office, and I have Windows 7 Ultimate on my home PC. We are using SVN at the office for our source control repository.
It all seems to start after I commit some code changes using SQL Source Control during a Windows 7 remote desktop session from my home PC to my office PC (over a VPN of course). This sometimes results in a "corrupted" entry in SVN which manifests after as an error during reading of the SVN entry when making a Migration Script: "Should have two revision for an edit - Expected 2 actual 1." Note: I can actually make a migration script at this point, using the SQL Source Control tool.
However, once there is a "corrupted" entry like that in the SVN tree, any SQL Compares between a DB under source control and one that is not, and that would reference that bad entry from the Source Tree, result in SQL Compare hanging during the generation of the migration script.
I really hope this helps resolve this issue, because as much as I love these tools, this problem has almost rendered SQL Compare unusable for me. / comments
Sorry it has taken me so long to reply to this...
I tried to enable logging with SQL Compare, but really didn't capture anything of use. However, I believe I may have discovered how this is trigger...
I will do this first thing Monday / comments
I will do this first thing Monday
SQL Compare 10 hangs after pressing Deployment Wizard button
I have tried a number of times to generate a deployment script with SQL Compare 10.1. The issue first occurred when I was using Remote Desktop, so I first thought it was related to that. However, a...