Comments
15 comments
-
We've had one or two instances of this being reported recently.
Do you have some tables that only exist in one of the databases? If so, it sounds like a known issue that we currently have a bug logged for. -
Yes. I'm only comparing a few tables out of many. Any idea when this may be resolved?
-
I just ran it through the comand line using version 8, which is still installed on the server. I started with 8 just before 9 came out, and it runs fine.
I don't know if this is relevant, but 9 also gave me an error about licensing. -
I'm not sure precisely when it will be fixed; but we've had a few reports now so hopefully it should be fairly soon
-
I'm getting this same error, but I can't use version 8 because that gives me an error about "Only x86 assemblies are currently supported." I have some tables that only exist on the second server, and I tried excluding them but I still get the error. Is there a workaround for this issue or do I have to wait until the next version is released?
-
I'm afraid the only workaround is to completely sync the schemas using SQL Compare. If there are more tables in one database than the other, you'll encounter this error from the command line.
-
Registering databases
Mapping
Comparing databases
Error: Object reference not set to an instance of an object.[/quote]
I have the same problem. -
Could users experiencing this issue please try the following patch: ftp://support.red-gate.com/patches/SQL_Data_Compare/SQL Data Compare_9.0.1.2.exe - and let us know if it helps?
Thanks! -
Is this patch officialy released? Or is it still in development i couldn't find any information on it.
-
It's still a private build specifically for addressing the issue discussed here; however the same fix should be in the next "proper" release of SQL Data Compare.
-
The patch worked. no problems.
-
The patch worked for me as well, thank you!
-
Oh, one thing to note about this version. It seems to be leaving a folder behind inside the Data folder. If I run it twice, the second run fails with a bunch of errors like the following:Error: Ignored statement found in file
d:\build\Database\trunk\Data\634429737738099016\dbo.tablename_Data.sql
at line 1
If I delete that weird folder (634429737738099016) then it works fine. -
Patch made it work for me.
-
After upgrading from v7 to v9 my scheduled tasks started crashing with this exact same error. The patch solved the issue.
The problem was only occurring when using the command line utility with a project file as parameter.
Add comment
Please sign in to leave a comment.
Registering databases
Mapping
Comparing databases
Error: Object reference not set to an instance of an object.