Having an odd SQL problem attempting to get a database moved from one machine to another. Both machines are running SQL 2005 Standard 32 bit and are both Windows 2003 servers. When I attempt to back the database up using the SQL tools and restore the .BAK file to the new SQL server, I get the following error:
Restore failed for Server “servername” (Microsoft.SqlServer.Smo)
System.Data.SqlClient.SqlError: RESTORE detected an error on page (44:2097184) in database “RestoreDBName” as read from the backup set.
Likewise when I attempt to simply copy the .MDF and .LDF files to the new server and attach them, I get the following error:
Attach database failed for Server “servername”
An exception occurred while executing a Transact-SQL statement or batch.
A system assertion check has failed. 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 a vailable from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Could not open new database ‘NewDatabaseName” Create DATABASE is aborted.
Process ID: 292876 (Microsoft SQL Server, Error: 3624)
From everything I’ve read, these errors generally indicate some sort of database corruption. However when I run DBCC CHECKDB on the database on the source server, it comes up perfectly clean... no corruption detected. In fact, this server hosts 8 different databases. All DB’s check out okay on the source server, however none of them will restore to a new server using either of the above methods. I’m having a hard time believing all of them could be corrupt when they show absolutely no indication of a problem.
Anyone have any ideas?