Unanswered: Msg 601 AND Msg 1813 on Attach Database...
I'm trying to use OSQL to attach an MDF and LDF file to my MSDE database. The files were originally detached from an SQL Server 7.0 (also MSDE) service and I'm trying to attach them to a computer running MSDE (SQL Server 2k). When I run sp_attach_db I get the following errors:
msg 601, Level 12, State 3, server IQCRAFT04, Line 1
could not continue scan with NOLOCK due to data movement
msg 1813, Level 16, State 3, server IQCRAFT04, Line 1
could not open new database 'M3SQL'. CREATE DATABASE is aborted.
converting database 'M3SQL' from version 534 to the current version 539.
database 'M3SQL' running the upgrade step fropm version 534 to version 535.
Any idea what this means?
I cannot attach these database files to the SQL Server 7.0 database either.
When I try to attach the database to the original SQL 7 computer, I get the following error messge:
Msg 906, Level 22, State 2, Server NIMITZ, Line 1
Could not locate row in sysobjects for system catalog 'Sysobjects' in database 'M3SQL'. This system catalog should exist in all databases. Run DBCC CHECKTABLE on sysobjects in this database.
You can attach a SQL 7.0 DB to a SQL 2K instance. I don't think that is the problem here. As a rule of thumb, whenever SQL Server asks for DBCC CHECKTABLE to be run on sysobjects, it is too late. I am afraid you will have to go back to the last good backup of this database. There are ways of getting a DB attached with no log, but sysobjects is firmly in the data portion of the database.
I was reaching that conclusion myself. Thankfully this is a dev environment which means no crucial data was lost. What I am upset about losing is my data structure. Any way I can extract that from the files?
The Command Tools only come with SQL Server. We don't own SQL Server, instead we're using MSDE.
MSDE is a free version of the SQL Server engine that comes with MS Office and Visual Studio. Access can be used as a front-end command tool, but I'm just learning how to use it as such. In the meantime, when I search for directions on the internet they describe how to do it in either EM or command-line. Not too many examples of how to accomplish these things in Access. It seems that many of these things can't be accomplished in access.