What are the challenges you face when working across database platforms? Take the survey

SQL Compare error message too vague

xpilxpil Posts: 7
edited October 8, 2015 7:06PM in SQL Compare 11
When running the mapping step, it may happen that SQL Schema Compare detects a severe error and stops further processing. It displays the details of the error but without indicating whether it applies to the source or the target server.

The error is:

"SQL Server detected a logical constency-based I/O error: incorrect pageid (expected: xxxxxxx; actual: yyyyyy). It occured during a read of page (a:bbbbbbb) in database ID zz at offset 0x123471289304781290374 in file 'E:path omdffile.mdf'. Additional messages in the SQL Server error log or system event may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately."

As can be clearly seen, there is no mention of which server this error applies to. It would be desirable to see this fixed in some future release.


Sign In or Register to comment.