Error on Attaching Database

When attaching a database that was detached from another SQL Server instance.

I got the error message below:

Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.

i am using SQL Server 2000

Thanks and Regards

Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.

I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||

I just hope somebody would help solve this prob coz i do have the same prob.

I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!

I got loads of work to do and this prob is eating my time.

Help!

|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.

Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.

This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||

I think upward compatibility doesn't work.

|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||

JonM wrote:

Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.

Jon,

With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.

Now, you asked for a reason, so here's my scenerio.

I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.

Do you have any comments or resolution that may be of assistance to me / us?

Thank you.

Chris

|||

reason 1

because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003

|||

It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:

1. Download the SQL Server 2005 Express Edition with Advanced Tools.

It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.

2. Buy a copy of SQL Server 2005 Developer Edition

This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.

3. Ask your webdesigner to migrate it to SQL Server 2000

If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.

|||

I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....

I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.