You more than likely encountered a logged error, but if the database upgrade did not inform you of an error I would still check the log. I have seen this kind of stuff many times, usually when the database or test system hasn't been prepared properly, you use an unsupported version of SQL, you have custom modifications or in at least 1 case, the system ran out of storage space. Preparation has to include not only resource allocation to SQL (especially tempdb) but proper consistency checks performed on the database, index maintenance, space allocation and typically a schema comparison. Sometimes these are only the beginning steps.

You more than likely encountered a logged error, but if the database upgrade did not inform you of an error I would still check the log. I have seen this kind of stuff many times, usually when the database or test system hasn't been prepared properly, you use an unsupported version of SQL, you have custom modifications or in at least 1 case, the system ran out of storage space. Preparation has to include not only resource allocation to SQL (especially tempdb) but proper consistency checks performed on the database, index maintenance, space allocation and typically a schema comparison. Sometimes these are only the beginning steps.