|
|
Posted by time management on 11/20/07 01:10
On Nov 19, 5:32 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> time management (tatata9...@gmail.com) writes:
> > Here's the scoop, I got a generic-purpose database (in the form of
> > *.mdb and *.ldf) from a 'reputable' source on the net. But when I
> > attempted to attach it to my sql server 2000 with SP3 with EM, it
> > failed complaining "Could not find row in sysindexes for database ID
> > 10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes."
>
> That message appears familiar. I seem to recall that is what happens
> if you try to attach an SQL 2005 database on SQL 2000. As far as
> SQL 2000 that is a database that is alien, and for which it cannot
> really have any graceful handling off.
>
> > Then, I attempted to command line attach (thought it may have some
> > option...), same outcome. Then, ran a search on this NG, and found
> > the following thread,
>
> Which is from 1998, and applies to really old versions of SQL Server.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Thanks for the follow-up, Erland. I tried to attach it with sql
server 2005 as well, the restored db seemed weired with "D:\aName
\blakdsm\blad..", empty, not workable. Now, suppose I can get a
clean/good copy for server 2005, what are the chances of success of
using DUMB database then BACKUP or LOAD back into server 2000? These
two boxes are not connected and they can't.
Don
Navigation:
[Reply to this message]
|