Attach DB from SQL7 into SQL2000

Hello all,
We have one computer with MSDE 1.0 with one database. Now, we are moving to
another server with SQL2000. When we try to attach the DB into the new
server, an error message appears:
--
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:355872) with latch type EX. VerifyPageId
failed.
Server: Msg 8946, Level 16, State 1, Line 1
Table error: Allocation page (1:355872) has invalid PFS_PAGE page header
values. Type is 0. Check type, object ID and page ID on the page.
Server: Msg 1813, Level 16, State 1, Line 1
Could not open new database 'Aroma2004Gco'. CREATE DATABASE is aborted.
Converting database 'Aroma2004Gco' from version 515 to the current version
539.
Database 'Aroma2004Gco' running the upgrade step from version 515 to version
524.
Database 'Aroma2004Gco' running the upgrade step from version 524 to version
525.
Database 'Aroma2004Gco' running the upgrade step from version 525 to version
526.
--
This DB works fine in the old computer. We also tried a Backup/restore, but
the error message is the same.
I'm stuck. Any ideas of what can i do to overcome this situation?
Best regards
Hugo SousaHi
Looks like you have corruption in the DB on MSDE.
Run DBCC CHECKDB on the database to see how bad it is.
Regards
Mike
"HugoSousa" wrote:

> Hello all,
> We have one computer with MSDE 1.0 with one database. Now, we are moving t
o
> another server with SQL2000. When we try to attach the DB into the new
> server, an error message appears:
> --
> Server: Msg 8966, Level 16, State 4, Line 1
> Could not read and latch page (1:355872) with latch type EX. VerifyPageId
> failed.
> Server: Msg 8946, Level 16, State 1, Line 1
> Table error: Allocation page (1:355872) has invalid PFS_PAGE page header
> values. Type is 0. Check type, object ID and page ID on the page.
> Server: Msg 1813, Level 16, State 1, Line 1
> Could not open new database 'Aroma2004Gco'. CREATE DATABASE is aborted.
> Converting database 'Aroma2004Gco' from version 515 to the current version
> 539.
> Database 'Aroma2004Gco' running the upgrade step from version 515 to versi
on
> 524.
> Database 'Aroma2004Gco' running the upgrade step from version 524 to versi
on
> 525.
> Database 'Aroma2004Gco' running the upgrade step from version 525 to versi
on
> 526.
> --
> This DB works fine in the old computer. We also tried a Backup/restore, bu
t
> the error message is the same.
> I'm stuck. Any ideas of what can i do to overcome this situation?
> Best regards
> Hugo Sousa
>
>|||CHECKDB found 0 allocation errors and 0 consistency errors in database
'ServiM2004Gco'.
I didn't mention it before, but if i attach this DB to an SQLServer 7, all
goes well.
This is very odd to me...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:B6A99C34-781A-4437-A4F0-557D614DB803@.microsoft.com...[vbcol=seagreen]
> Hi
> Looks like you have corruption in the DB on MSDE.
> Run DBCC CHECKDB on the database to see how bad it is.
> Regards
> Mike
> "HugoSousa" wrote:
>|||This is all very strange, and something I've never heard of before. You shou
ld be able to attach and
restore 7.0 stuff into 2000. I also thought about database corruption. I sug
gest you open a case
with MS support and see if they can come up with anything.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"HugoSousa" <hugosousa@.removethis.gestexper.pt> wrote in message
news:uN0foHmwEHA.3416@.TK2MSFTNGP09.phx.gbl...
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'ServiM2004Gco'.
> I didn't mention it before, but if i attach this DB to an SQLServer 7, all
> goes well.
> This is very odd to me...
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:B6A99C34-781A-4437-A4F0-557D614DB803@.microsoft.com...
>|||Well... i've done this kind of operation many times before, without any
problems...
I guess i'll try MS.
If they cannot help, i'll make a little program to copy all data to an empty
DB on thee SQL2000 machine (this is a very small DB... sholdn't take too
long).
Thanks to everyone that tried to help me
Hugo Sousa
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OqckEVmwEHA.2908@.tk2msftngp13.phx.gbl...
> This is all very strange, and something I've never heard of before. You
> should be able to attach and
> restore 7.0 stuff into 2000. I also thought about database corruption. I
> suggest you open a case
> with MS support and see if they can come up with anything.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "HugoSousa" <hugosousa@.removethis.gestexper.pt> wrote in message
> news:uN0foHmwEHA.3416@.TK2MSFTNGP09.phx.gbl...
>|||Perhaps you should give backup / restore a try?
"HugoSousa" <hugosousa@.removethis.gestexper.pt> wrote in message
news:%23%23nfqrmwEHA.1204@.TK2MSFTNGP10.phx.gbl...
> Well... i've done this kind of operation many times before, without any
> problems...
> I guess i'll try MS.
> If they cannot help, i'll make a little program to copy all data to an
empty
> DB on thee SQL2000 machine (this is a very small DB... sholdn't take too
> long).
> Thanks to everyone that tried to help me
> Hugo Sousa
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:OqckEVmwEHA.2908@.tk2msftngp13.phx.gbl...
new[vbcol=seagreen]
>|||Already tried that. In fact, it was my first choice. But the error message
was the same...
"Scott Morris" <bogus@.bogus.com> wrote in message
news:uhCKpPnwEHA.1988@.TK2MSFTNGP12.phx.gbl...
> Perhaps you should give backup / restore a try?
> "HugoSousa" <hugosousa@.removethis.gestexper.pt> wrote in message
> news:%23%23nfqrmwEHA.1204@.TK2MSFTNGP10.phx.gbl...
> empty
> in
> new
>|||I would make sure that the SQL 7 MSDE had the latest service packs on it.
Also, what is the service pack level on the SQL 2K installation? Have any
QFE's been applied to either.
After awhile, if the 7.0 hasn't been serviced, but the 2K has been, the
versions get too far seperated for the inline upgrade to complete
successfully... Backwards compatibility only works for so long.
Sincerely,
Anthony Thomas
"HugoSousa" wrote:

> Already tried that. In fact, it was my first choice. But the error message
> was the same...
> "Scott Morris" <bogus@.bogus.com> wrote in message
> news:uhCKpPnwEHA.1988@.TK2MSFTNGP12.phx.gbl...
>
>|||Well, i've found it.
When running DBCC CHECKCATALOG , i've found lots of errors, like the one
below:
Table Corrupt: Object ID 37067368 (object 'OrcCb') does not match between
'SYSREFERENCES' and 'SYSCOLUMNS.'.
The question now is: What to do to correct this?
Best regards
Hugo Sousa
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message
news:4E652B8D-C482-4626-8B93-5C4087A53DAD@.microsoft.com...[vbcol=seagreen]
>I would make sure that the SQL 7 MSDE had the latest service packs on it.
> Also, what is the service pack level on the SQL 2K installation? Have any
> QFE's been applied to either.
> After awhile, if the 7.0 hasn't been serviced, but the 2K has been, the
> versions get too far seperated for the inline upgrade to complete
> successfully... Backwards compatibility only works for so long.
> Sincerely,
>
> Anthony Thomas
>
> "HugoSousa" wrote:
>|||Well, i've deleted all Foreign Keys, and the errors just went away. But when
i recreate them, the errors come back.
Anyone as any idea to solvee this?
"HugoSousa" <hugosousa@.removethis.gestexper.pt> wrote in message
news:erbHSAowEHA.3144@.TK2MSFTNGP15.phx.gbl...
> Well, i've found it.
> When running DBCC CHECKCATALOG , i've found lots of errors, like the one
> below:
> Table Corrupt: Object ID 37067368 (object 'OrcCb') does not match between
> 'SYSREFERENCES' and 'SYSCOLUMNS.'.
> The question now is: What to do to correct this?
> Best regards
> Hugo Sousa
> "AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message
> news:4E652B8D-C482-4626-8B93-5C4087A53DAD@.microsoft.com...
>