Post reply

SQL 2005 DB Upgrade

  • November 13, 2007 at 10:23 am

    #122438

    We are upgrading our database Server from SQL 2000 to SQL 2005, When we restore one of our user databases from SQL2000 to SQL2005. We got the following error:

    When I run the following script:

    RESTORE DATABASE Oiddbdevl

    FROM DISK = 'k:\mssql\devL2kdatabackupfiles\Oiddbdevl_db_20071109.bak'

    WITH REPLACE

    I got the error:

    Processed 405808 pages for database 'Oiddbdevl', file 'OIDDBDevl_Data' on file 1.

    Processed 1 pages for database 'Oiddbdevl', file 'OIDDBDevl_Log' on file 1.

    Converting database 'Oiddbdevl' from version 539 to the current version 611.

    Database 'Oiddbdevl' running the upgrade step from version 539 to version 551.

    Location: cmeddb.cpp:1802

    Expression: 0

    SPID: 53

    Process ID: 1728

    Msg 3167, Level 16, State 1, Line 1

    RESTORE could not start database 'Oiddbdevl'.

    Msg 3013, Level 16, State 1, Line 1

    RESTORE DATABASE is terminating abnormally.

    Msg 3624, Level 20, State 1, Line 1

    A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

    When I run the DBCC CHECKDB, It's fine.

    Any idea? How to fix it.

    I really appreciate your help

    Thanks,

    Linda

  • November 13, 2007 at 10:40 am

    #750766

    tried a new backup yet?

  • November 13, 2007 at 11:02 am

    #750783

    Yes.

  • November 13, 2007 at 2:45 pm

    #750845

    You could try making a copy of your mdf, ldf files and then attaching them rather than doing the backup restore route.

    Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

  • November 13, 2007 at 2:49 pm

    #750847

    you should ensure that the destination path exists:

    restore filelistonly from disk='....'

    See if the destination exists. Normally 2005 introduce MSSQL.1 in the path so it may not match the 2000 one and if that is the case use the "MOVE" clause of the restore command.

    Good luck


    * Noel

  • November 13, 2007 at 11:07 pm

    #750941

    You can check the consistency of the backup using the restore verifyonly command to see if there is any backup file corruption.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • November 14, 2007 at 5:05 am

    #751043

    Yes. I already tried detach database and attach database files method to restore this database. But when I attach data files, I got almost the same error message.

  • November 14, 2007 at 5:42 am

    #751048

    Thanks for your response.

    Here is my case:

    We have 17 user databases in the SQL 2000 server, When I migrate those databases into SQL 2005 (other server), I have no problem to restor 16 of them. Only this one. I can't restore it. First I run restore script to restore this database, (destination path does exist). It failed. See my post error message, So I tried using SQL Server Management Studio interface to restore it. I got almost same error message. I tried detach and attach data files, It fail too. Then I tried using the same backup to restore into difference 2005 server. I got same error. When I using this same backup file to restore into SQL2000 server, It's fine.

    Rigth now, in order to restore this database, We have to objects by objects to move it, It's a time consuming. I like to know if there is other way we can try?

    Thanks for your help,

    Linda

  • November 14, 2007 at 7:11 am

    #751074

    A completely off the wall thought and I'm not even sure it would make a difference but have you checked the compatability level? Any chance it a 6.5 database? Again I'm not sure it would have any affect but it can't hurt to check.

    Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

  • November 14, 2007 at 8:30 am

    #751111

    This database compatability level is 80 which is right one.

    Thanks,

    Linda

  • November 17, 2007 at 2:58 pm

    #752078

    Hi Linda,

    first of all,i have a doubt..why yo are restoring the databse ith 'REPLACE' option...is there any datafiles in th same location...?...can you try to restore other than same location....you installed the latest service pack of sql server 2005 right?

    Thanks

    Joseph

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply