Asp.net / sql help: moving

Showing posts with label moving. 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 db

I'm moving a db from serverA to serverB. I detached the db on serverA and
copied the files to serverB. I want to change the file names when I attach
it on serverB. How can I do this? If I try to change the name and attach
the db, it doesn't like the renamed files; it will only let me attach as the
original name of the files.
If it's not available in attach, can I rename the file once I attach them
somehow?
Thanks, AndreI figured this out, thanks.
"Andre" <no@.spam.com> wrote in message
news:uvackOWzGHA.1536@.TK2MSFTNGP02.phx.gbl...
> I'm moving a db from serverA to serverB. I detached the db on serverA and
> copied the files to serverB. I want to change the file names when I
attach
> it on serverB. How can I do this? If I try to change the name and attach
> the db, it doesn't like the renamed files; it will only let me attach as
the
> original name of the files.
> If it's not available in attach, can I rename the file once I attach them
> somehow?
>
> Thanks, Andre
>

attach db

Sunday, March 25, 2012

attach / detach newbie question

I've looked at all the microsoft articles relating to moving a database from
one location to another using the attach/detach commands and I have one
question. Are those commands typed from a command prompt or do I need to run
these from SQL manager?
Hi,
You can execute those commands from
1. Selecting Query Analyzer from SQL Program groups. (issue the user name
and password to login)
Once you go inside the Query analyzer you could execute all TSQL
commands which includes the detach and attach db commands.
2. FROM command prompt execute OSQL
OSQL -Usa -Ppassword -S <SQL Servername> (enter)
This will go to a SQL prompt; there execute those sp_detach_db and
sp_attach_db commands.
Thanks
Hari
SQL Server MVP
"JL Adamson" <JLAdamson@.discussions.microsoft.com> wrote in message
news:8886FE74-93B2-4FD9-997F-25884FA0F953@.microsoft.com...
> I've looked at all the microsoft articles relating to moving a database
> from
> one location to another using the attach/detach commands and I have one
> question. Are those commands typed from a command prompt or do I need to
> run
> these from SQL manager?

attach / detach newbie question

I've looked at all the microsoft articles relating to moving a database from
one location to another using the attach/detach commands and I have one
question. Are those commands typed from a command prompt or do I need to run
these from SQL manager?Hi,
You can execute those commands from
1. Selecting Query Analyzer from SQL Program groups. (issue the user name
and password to login)
Once you go inside the Query analyzer you could execute all TSQL
commands which includes the detach and attach db commands.
2. FROM command prompt execute OSQL
OSQL -Usa -Ppassword -S <SQL Servername> (enter)
This will go to a SQL prompt; there execute those sp_detach_db and
sp_attach_db commands.
Thanks
Hari
SQL Server MVP
"JL Adamson" <JLAdamson@.discussions.microsoft.com> wrote in message
news:8886FE74-93B2-4FD9-997F-25884FA0F953@.microsoft.com...
> I've looked at all the microsoft articles relating to moving a database
> from
> one location to another using the attach/detach commands and I have one
> question. Are those commands typed from a command prompt or do I need to
> run
> these from SQL manager?

attach / detach newbie question

I've looked at all the microsoft articles relating to moving a database from
one location to another using the attach/detach commands and I have one
question. Are those commands typed from a command prompt or do I need to run
these from SQL manager?Hi,
You can execute those commands from
1. Selecting Query Analyzer from SQL Program groups. (issue the user name
and password to login)
Once you go inside the Query analyzer you could execute all TSQL
commands which includes the detach and attach db commands.
2. FROM command prompt execute OSQL
OSQL -Usa -Ppassword -S <SQL Servername> (enter)
This will go to a SQL prompt; there execute those sp_detach_db and
sp_attach_db commands.
Thanks
Hari
SQL Server MVP
"JL Adamson" <JLAdamson@.discussions.microsoft.com> wrote in message
news:8886FE74-93B2-4FD9-997F-25884FA0F953@.microsoft.com...
> I've looked at all the microsoft articles relating to moving a database
> from
> one location to another using the attach/detach commands and I have one
> question. Are those commands typed from a command prompt or do I need to
> run
> these from SQL manager?

Thursday, March 22, 2012

Atlernative to SQL Server Management Studio (i.e. garbage) . Any suggestions?

Folks I have recently had the misfortune of moving to SQL Server Managment Studio as per our upgrade to SQL 2005. There is no doubt that SQL Server Management is a major disappoinment compared to Enterprise manager.

The UI is the biggest disaster I have ever seen. Getting rid of the SQL Query analyzer tool was aTERRIBLE idea. The UI is buggy and unfriendly. It is a major POS. I hope someone in the SQL Dev team is listening / reading this post (hellooooo anybody homeee.....)

Now that I have vented my frustration ...

I wanted to know any atlernatives to the SQL Server Management Studio. There are plenty of 3rd Party tools out there I wanted to find out from this forum which popular 3rd Party tools are most developers using

Thanks for bearing with me.

If all you're after is query analyzer type functionality the free SQL Scripter fromhttp://www.sqlscripter.com/ is worth a look.

|||

There's a bunch of them. Some of them free, some paid. Do a google search and you will find them - SQL Edit, Toad etc.

|||

A colleague found this reference on line yesterday. None of us have tried it out, but it looks reasonable.

http://www.albahari.com/queryexpress.html

|||

That's quite odd actually, I use it every day, and have yet to really stumble across a major issue with it. It's nice having one single app to be able to do all the functionality of the old enterprise manager (Yuck!), query analyzer, and (insert some database project tool that wasn't shipped with 2000). It is however pretty memory hungry, so I feel sorry for those trying to develop on really low end machines.

Really, the only complaint I have with it, is that I wish it's "script to..." functionality for insert/update/delete would default to placing parameters in the placeholders, or even better generate a VB.NET/C# SqlCommand for it (including creating the parameters, with datatypes). Obviously a minor complaint considering that it isn't part of the VB.NET/C# programming tools.

Or perhaps you've overlooked that you can right click any database, choose "New query", and it opens a new tab that acts very similiar to the old query analyzer?

|||

Motley:
That's quite odd actually, I use it every day, and have yet to really stumble across a major issue with it. It's nice having one single app to be able to do all the functionality of the old enterprise manager (Yuck!), query analyzer, and (insert some database project tool that wasn't shipped with 2000). It is however pretty memory hungry, so I feel sorry for those trying to develop on really low end machines.
Really, the only complaint I have with it, is that I wish it's "script to..." functionality for insert/update/delete would default to placing parameters in the placeholders, or even better generate a VB.NET/C# SqlCommand for it (including creating the parameters, with datatypes). Obviously a minor complaint considering that it isn't part of the VB.NET/C# programming tools.

Or perhaps you've overlooked that you can right click any database, choose "New query", and it opens a new tab that acts very similiar to the old query analyzer?

Well after using enterprise manager for a very long time I liked the fact that Query Analyzer open by itself. I realize now that it simply is intergated into the application via tabbed windows. Some how I just do not like that structure of UI design. But that this the least of my issues. In addition to the issue you mentioned there are several other issues.

When I try to open 2 or more db connection in my object explorer items not appear in my summary window. For example if i click on stored procs under programmability it shows me there are x number of items on the top right by the main screen is blank.

Frequently I get invalid errors when trying to browse items in the object explorer (error says invalid index)

When I ask it to remember my password for object explorer or for a new query it does not remember the password the next time

Additionally the UI is poorly designed and does not flow very well from a usability standpoint. (I wish the SQL team would pay more attention to this and not take UI so lightly. UI it is an after thought for developers BUT it is the first impression you make on the user, and that IMO is crucial)

I thought that I was the only person on my team not liking SQL Mgmt studio but 4/5 develpers including our DBA are not at all happy with the product...

|||

Well it seems to me that you are using portions of the studio, that I don't think I've ever used. I don't think I've had the Object Explorer Details window open for more than 2 seconds ever.

As for the UI design, it's probably a matter of taste. The paned view (Objects on left, middle as a work area, right is properties, etc) is used by a number of differing products (Visual Studio, Dreamweaver, Photoshop, etc etc). I'd hardly call it a poorly designed UI, but it's a matter of opinion and what you are trying to accomplish with the tool.

|||

Motley:
Well it seems to me that you are using portions of the studio, that I don't think I've ever used. I don't think I've had the Object Explorer Details window open for more than 2 seconds ever.
As for the UI design, it's probably a matter of taste. The paned view (Objects on left, middle as a work area, right is properties, etc) is used by a number of differing products (Visual Studio, Dreamweaver, Photoshop, etc etc). I'd hardly call it a poorly designed UI, but it's a matter of opinion and what you are trying to accomplish with the tool.

Most of my problems are with SQL Mgmt Studio UI whose is very different from the Visual Studio's UI (I find VS2005 to be quite good actually). I did intially think it was a matter of personal taste but what can I can when 4/5 folks on my team have the same complains.

Believe you me I did not give up on this after a day of working with it. I have been using it for the last 2 months.

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 db

attach db

Sunday, March 25, 2012

attach / detach newbie question

attach / detach newbie question

attach / detach newbie question

Thursday, March 22, 2012

Atlernative to SQL Server Management Studio (i.e. garbage) . Any suggestions?

Asp.net / sql help

Blog Archive

About Me