Asp.net / sql help: computer

Showing posts with label computer. Show all posts

Thursday, March 29, 2012

Attach DB from SQL7 into SQL2000

Tuesday, March 27, 2012

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 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 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...
> 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:
>> 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 Sousa
>>|||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...
> 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...
> > 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:
> >
> >> 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 Sousa
> >>
> >>
> >>
>|||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...
>> 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...
>> > 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:
>> >
>> >> 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 Sousa
>> >>
>> >>
>> >>
>>
>|||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...
> > 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...
> >> 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...
> >> > 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:
> >> >
> >> >> 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 Sousa
> >> >>
> >> >>
> >> >>
> >>
> >>
> >
> >
>|||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...
>> 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...
>> >> 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...
>> >> > 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:
>> >> >
>> >> >> 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 Sousa
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >
>> >
>>
>|||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...
> > 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...
> >> > 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...
> >> >> 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...
> >> >> > 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:
> >> >> >
> >> >> >> 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 Sousa
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>|||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...
>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...
>> > 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...
>> >> > 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...
>> >> >> 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...
>> >> >> > 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:
>> >> >> >
>> >> >> >> 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 Sousa
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>|||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...
>>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...
>> > 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...
>> >> > 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...
>> >> >> 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...
>> >> >> > 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:
>> >> >> >
>> >> >> >> 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 Sousa
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>|||Do the errors come back when you add each FK back or only after you've added
them and rerun DBCC CHECKCATALOGUE?
When you recreate the FK, do you use the WITH CHECK or the WITH NOCHECK
clause? I would recommend that you use the WITH CHECK. It sounds like the
FKs were there, someone issued a ALTER TABLE DISABLE FK command and loaded
some data the violated the constraints and/or the original creation, and
subsequent, used and/or keep using the WITH NOCHECK clause. I'm rather upset
with Microsoft that they even allowed that clause in the syntax. The fix
would be to repair the data that is violating the constraints.
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...
> >>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...
> >> > 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...
> >> >> > 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...
> >> >> >> 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...
> >> >> >> > 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:
> >> >> >> >
> >> >> >> >> 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 Sousa
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
> >
> >
>
>|||The erros only come after i run CHECKCATALOG, but i'm creating them with
NOCHEK. I'll try it with CHECK clause, to see if that's the problem, and
i'll post here the results.
"AnthonyThomas" <AnthonyThomas@.discussions.microsoft.com> wrote in message
news:40B1DAA7-2E15-41E4-BC85-D7A5CC9D4214@.microsoft.com...
> Do the errors come back when you add each FK back or only after you've
> added
> them and rerun DBCC CHECKCATALOGUE?
> When you recreate the FK, do you use the WITH CHECK or the WITH NOCHECK
> clause? I would recommend that you use the WITH CHECK. It sounds like
> the
> FKs were there, someone issued a ALTER TABLE DISABLE FK command and loaded
> some data the violated the constraints and/or the original creation, and
> subsequent, used and/or keep using the WITH NOCHECK clause. I'm rather
> upset
> with Microsoft that they even allowed that clause in the syntax. The fix
> would be to repair the data that is violating the constraints.
> 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...
>> >>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...
>> >> > 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...
>> >> >> > 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...
>> >> >> >> 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...
>> >> >> >> > 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:
>> >> >> >> >
>> >> >> >> >> 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 Sousa
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >
>> >
>>

Attach database over the network.

Hello,
I have Sql Express installed in one computer and I want to attach a database
that is stored in another computer.
How can I do that?
ThanksSQL Server doesn't support having database files over the network. Copy the
files locally then
attach to the files. Or have an SQL Server on the other machine and connect
to that SQL Server from
your client apps.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Joao Novo" <jotanovo@.gmail.com> wrote in message news:uQPr1M$gHHA.4064@.TK2MSFTNGP02.phx.gbl
..
> Hello,
> I have Sql Express installed in one computer and I want to attach a databa
se that is stored in
> another computer.
> How can I do that?
> Thanks
>sql

Attach database over the network.

Hello,
I have Sql Express installed in one computer and I want to attach a database
that is stored in another computer.
How can I do that?
ThanksSQL Server doesn't support having database files over the network. Copy the files locally then
attach to the files. Or have an SQL Server on the other machine and connect to that SQL Server from
your client apps.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Joao Novo" <jotanovo@.gmail.com> wrote in message news:uQPr1M$gHHA.4064@.TK2MSFTNGP02.phx.gbl...
> Hello,
> I have Sql Express installed in one computer and I want to attach a database that is stored in
> another computer.
> How can I do that?
> Thanks
>

Friday, February 24, 2012

ASPNETDB.mdf "...already in use..." Error and Broader Questions

When you create and host an ASP.Net 2.0 site on your local computer and then configure .Net 2.0's drop-in user registration and management system it creates a SQL file named ASPNETDB.mdf with a whole bunch of tables and stored procedures (…as most of you know). If you add your own custom tables to that database file and then try to call those tables you get an error that says that ASPNETDB.mdf is already in use. One way to get around this is to create a separate database in the form of another ".mdf" file and then put all of your own custom tables in it. You avoid the "...already in use..." errors that way but all your user accounts and the primary key structure that identifies them are in the original ASPNETDB.mdf file. This makes it impossible to do primary/foreign key relationships between those tables and those in the new separate database you created. It's kind of a catch-22 situation...unless I'm missing something that relates to releasing the ASPNETDB.mdf file from use whenever it is called so that additional tables and queries against that database file can be made without the "…already in use…" error cropping up. I am wondering if this problem is because the ASPNETDB.mdf file is not a "real" SQL database and as such imposes multiple-connectivity limitations such as those I am seeing. If this is true, migrating to a real SQL database would alleviate this? Finally, from a broader security and scalability standpoint…what are the best practices relating to use of the ASPNETDB.mdf database for all your custom tables? Should an additional database be created for all my application's custom tables (leading to the primary/foreign key problems) or should the additional tables be put into the ASPNETDB.mdf file (with some way of working around the "…already in use…" error)? A long-winded and broad question…thanks in advance for any responses.

MDCragg

The default membership provider already has an open connection to the file, which seems like the reason why you can't make your own connection. Perhaps you could extend this provider to keep its current functionality, but add your own requirements to access the other tables, as well. The default provider is the System.Web.Security.SqlMembershipProvider class. After you create this, set it as the default provider in your web.config.

Sample on how to configure a membership provider in web.config:http://msdn2.microsoft.com/en-us/library/44w5aswa.aspx

|||

That article tells how to merge the membership provider tables and stored procedures into my own database. I will try this to see if it solves the problem. I am at least a little bit doubtful if it will though because it seems like it will just shift the same persistent and exclusive connectivity problem I am having from the current user account database to my own database.

|||

This seems to have worked. I installed SQL Server Management Studio Express. I wasn't able to navigate to the existing custom database that I had created so I copied it to the default directory that SQL Server MSE utilizes. I was able to connect to it there and thus "attach" it to my PC's SQL host. Once that was done I was able to use the aspnet_regsql.exe utility to populate that database with all of .Net's Membership tables, views, stored procedures, etc. I copied the database back to the App_Data folder. I adjusted all the Membership entries in the web.config folder to "point to" the custom database instead of the ASPNETDB.mdf file (which I removed). I did some additional tweaking with things such as connection strings. Then I launched the site and everything seemed to work. I am able to connect to the .Net Membership tables as well as all my own tables...all of which exist in the one custom database file.

So, this is fixed although I don't know what the difference was between the ASPNETDB.mdf file and the custom ".mdf" file that I created. I'm sure there is a setting or two somewhere in the database instance, the connection, or something or other that led to the difficulty.

Thursday, March 29, 2012

Attach DB from SQL7 into SQL2000

Attach DB from SQL7 into SQL2000

Tuesday, March 27, 2012

Attach DB from SQL7 into SQL2000

Attach database over the network.

Attach database over the network.

Friday, February 24, 2012

ASPNETDB.mdf "...already in use..." Error and Broader Questions

Asp.net / sql help

Blog Archive

About Me