February 19, 2009 at 2:42 pm
Our SQL Server 2008 (64-bit) is installed on a Windows 2003 Server (64-bit).
We copied the backup of a database from a SQL2000 server to SQL Server 2008 (64-bit). After the copy, we try to restore but it failed with a bunch of stack dump then the error "During upgrade, database raised exception 2905, severity 25, state 1, address 0000000002B93DCD. Use the exception number to determine the cause."
Then we copied the same backup to a SQL 2005 Server (64-bit) and we did not have problem to restore.
Anybody has any clue about this error ?
Thanks.
February 19, 2009 at 2:59 pm
I don't know the cause, but have you run SQL Server Upgrade Advisor on the SQL 2000 databases to see if there are any upgrade issues?
Greg
February 19, 2009 at 7:42 pm
Does anybody had this error before ?
February 20, 2009 at 7:10 am
I haven't run into it either. Have you run the Upgrade Advisor? There are things that you must change prior to upgrading the database. If you haven't run the Advisor, you might be hitting one of them.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 23, 2009 at 12:22 pm
I ran Upgrade Adviser but I didn't get any errors. There are two warnings but they are related to full-text search which we don't even use.
One thing I didn't mention is that our database is configured for replication. According to "Version and Edition Upgrades" from MSDN or SQL 2008 BOL, the upgrade notes says that: "You can also back up or detach database from a 32-bit instance of SQL Server, and then restore or attach them to an instance of SQL Server (64-bit) if the databases are not published in replication.". Well, my database is being published, does that means I cannot upgrade directly ? Microsoft did not said how to, have any of you were able to upgrade a published database (in 32-bit) to a 64-bit SQL 2008 database ?
Thanks.
February 23, 2009 at 12:36 pm
You need to remove the publication prior to upgrade. Then perform the upgrade and then reestablish the publication.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 23, 2009 at 12:56 pm
Is this applies only to SQL 2008 ? because I din't have problem restoring this same database to SQL 2005.
February 23, 2009 at 1:00 pm
I'm extremely weak on replication, so I couldn't begin to tell you why, but I'm pretty sure that's required.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 23, 2009 at 1:36 pm
Thank you anyway. Does anybody else have any clue ?
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply