Comments
3 comments
-
If you could run SQL Server Profiler against your database, and send me (michelle.taylor@red-gate.com) the last query that SQL Compare executes before returning that error message, along with the results of that query, we should be able to find out what's wrong.
The most likely cause is that there is some object in your database with very strange properties, possibly inherited from pre-7 versions of SQL Server or introduced by an application. If you could run dbcc checkdb and tell us if it reports any problems with the database, that may also be useful. -
Info is on the way via email -- Thank!
-
Resolution -- found 1 table and 1 stored proc that had null as the owner. Modified sysobjects to change uid to 1. Compare worked after that.
Add comment
Please sign in to leave a comment.
Any other help available?