I am restoring a SQL 2000 user database on a SQL 2008 R2 box, but occasionally I get the following error This is the SQL log.
22/11/2010 09:32:00 | SPID61 | Starting database 'DB_OPP_P_2'
22/11/2010 09:32:00 | SPID61 | The database 'DB_OPP_P_2' has been reinstated and is in a position that does not allow retrieval to run.
22/11/2010 09:32:33 | SPID61 | Starting database 'DB_OPP_P_2'
22/11/2010 09:32:33 | SPID61 | Recovery is writing a checkpoint in the database 'DB_OPP_P_2' (51). This is an informational message only. No user action is required.
22/11/2010 09:32:36 | SPID61 | Error: 9 28, Seriousness: 20, State: 1.
22/11/2010 09:32:36 | SPID61 | During the upgrade, database exception 156, severity 25, state 1, address 0000000002225 raised A 9F. Use the exception number to determine the reason.
Since this exception appears during the upgrade phase, I believe that after 100% of hits per cent it happened.
A script retrying it has been applied again, and it was tried all 5 times. However, if I try again with the same restore script manually, the restore is complete. I have run the DBCC checkbox on the source and there is no error.
The database compatibility level is 80 (sql 2000) and the version is 539.
Upgrade consultant on the problematic database of time, 27 view external objects as well as view older objects. * =, = *
Unfortunately I will not be able to check whether it is a criminal or not. Another possibility is that there are so many PROCs that are not able to demarcate their extensions to BEGIN and END, and if I create them in batch, it confuses SQL.
Update:
- I have successfully restored the database on the SQL 2000 box.
- I have also applied a retraining approach to my work, which failed all the time 5 times.
Failed to retry But the strange thing is that if I try again with the same restart script, then the work has been tried to restore it.
UPDATE 2: I have manually restored the database on my migration to SQL 2008 R2, so I have not fixed this issue, and it will not be corrected, As does not happen on SQL 2008 R2. Thanks for your help.
Check the compatibility of the database in SQL Server 2000: Are they 65?
Error 156 is wrong syntax, basically, and this is usually due to compatibility mismatch. "65" is not supported in SQL Server 2008
Did you try before backup / restore?
Edit:
External join hmm
Just for the sake of but looked for it. My guess is that the syntax is breaking things, even if the upgrade consultant and MSDN say what I personally have not used it, er, I migrated from 6.5 to SQL Server 7 ...
Comments
Post a Comment