Asp.net / sql help: sql2000

Showing posts with label sql2000. Show all posts

Thursday, March 29, 2012

attach multiply databases

This summary is not available. Please click here to view the post.

attach multiply databases

This summary is not available. Please click here to view the post.

Attach db to sql 2005 express edition

My dog ate my sql2000 installation disk! After a recent xp installation I remembered that.

Now I'm in a hurry to get up and running with SQL again. I've installed SQL server 2005 express, but I can't attach any databases, or really do anything for that matter. I have a copy of SQL Server 2005 enterprise edition but that won't install on my development machine, Xp Sp2. Which way should I go, install SQL 2005 enterprise on a Win 2003 server or can I download something to administer the express version?

As always thanks for any and all replies!

/Eskil

You can download the SQL Server 2005 Management Studiohttps://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en)

attach db to .net2 project

Hi,

How do I attach an existing sql2000 database to a .net 2 project in the app_data folder?

thanks

Just detach the database from the SQL 2000 instance, then open your project-> right click the App_Data folder in Solution Explorer->choose Add Existing Items->find the database file and add it.sql

Attach DB problem

I'm running SQL2000 on my development machine. 2 of our clients use SQL2005.
I've read that it's not possible to attach DB detached from SQL2005 to
SQL2000. But by some reason I can do it with the database of one of the
client. When I try to do the same with the second client database I get an
Error 602.
What is correct - database from SQL2005 cannot be attached to SQL2000, or it
can be attached?
Why I can do it with one DB, but cannot with another one. Both DBs do not
give me any problem if I'm attaching them to SQL2005 running on my second
development machine.
Thank you
vovanMy guess is that the one that works was never attached to a SQL2005 instance
to begin with. Even if by chance it seemed to attach I would not trust it.
The system objects are no longer compatible with 2000 after it has been
attached or restored to a 2005 instance. Bottom line is that it is NOT
backward compatible.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"vovan" <v@.v.com> wrote in message
news:uzIknmq4HHA.5984@.TK2MSFTNGP04.phx.gbl...
> I'm running SQL2000 on my development machine. 2 of our clients use
> SQL2005. I've read that it's not possible to attach DB detached from
> SQL2005 to SQL2000. But by some reason I can do it with the database of
> one of the client. When I try to do the same with the second client
> database I get an Error 602.
> What is correct - database from SQL2005 cannot be attached to SQL2000, or
> it can be attached?
> Why I can do it with one DB, but cannot with another one. Both DBs do not
> give me any problem if I'm attaching them to SQL2005 running on my second
> development machine.
> Thank you
> vovan
>|||Thank you Andrew
I was mislead by the fact that the client uses SQL 2005 Management Studio to
manage their SQL Server. But the version of SQL is 2000.
vovan
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eDUnIYr4HHA.5316@.TK2MSFTNGP04.phx.gbl...
> My guess is that the one that works was never attached to a SQL2005
> instance to begin with. Even if by chance it seemed to attach I would not
> trust it. The system objects are no longer compatible with 2000 after it
> has been attached or restored to a 2005 instance. Bottom line is that it
> is NOT backward compatible.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "vovan" <v@.v.com> wrote in message
> news:uzIknmq4HHA.5984@.TK2MSFTNGP04.phx.gbl...
>> I'm running SQL2000 on my development machine. 2 of our clients use
>> SQL2005. I've read that it's not possible to attach DB detached from
>> SQL2005 to SQL2000. But by some reason I can do it with the database of
>> one of the client. When I try to do the same with the second client
>> database I get an Error 602.
>> What is correct - database from SQL2005 cannot be attached to SQL2000, or
>> it can be attached?
>> Why I can do it with one DB, but cannot with another one. Both DBs do not
>> give me any problem if I'm attaching them to SQL2005 running on my second
>> development machine.
>> Thank you
>> vovan
>

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 to SQL2005 from old MSDE database

I have a medical records system, SoapWare v4.90, that uses MSDE (SQL2000) databases. Due to the 2gb limitation, I am trying to migrate over to SQL 2005 (Standard or Express) which the company says works fine. The SoapWare has a datamanager that allows me to log in to the MSDE instance, detach the SoapWare databases from msde (as well as do backups, etc) which I can confirm are detached.

Then I log back into a SQL2005 database instance using the datamanager and try to attach the database. This is what their pictured instructions demonstrate. However, I get an error:

Database 'sw_charts' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.

Or... is there a way to attach the databases to SQLExpress manually?

Help pls?The instance of SQL Express needs to be run as "Local system" which is not the default. Once this is changed, the SQL Express database attaches to the old MSDE SQL 2000 database just fine, and the program appears to run without problems.

Thanks to anyone looking at my post, and hopefully, this will help others.

David|||1> use master
2> go

** close the database johandb

1>exec sp_dboption N'johandb',N'autoclose',N'false'
2>go

1>checkpoint
2>go

** detach database johan
1> exec sp_detach_db johandb, true
2> go

** attach with files

1> exec sp_attach_db @.dbname = 'johandb',
2> @.filename1='d:\mssql7\data\johandb_data.mdf',
3> @.filename2='d:\mssql7\data\johandb_log.ldf'
4> go

Regards,
Johan|||Does anyone use Lytec and SOAPware together?

MD in Texassql

Attach database between different sort orders

Hi,

Just wanted to check. I've got a SQL 7.0 box on NT4 with about 40 databases (each about 500Mb-1Gb) which I want to move to SQL2000.

The main problem is, the 7.0 box was built with a sort order not officially supported by the finance software that uses the databases, so I want to build the SQL2000 box with the default sort orders and character sets.

I've done this in a test environment by copying the .mdf files accross and attaching them to the SQL2000 box, and this all seems to work. But is this advisable, and will there be any problems?

Thanks for the help!!It does?

How are you doing the migration?

Dump and Restore...I didn't think it would work...Never did for me...

I know there are reasons, but WHY (for the love of god) do people install with other than the default collation..|||Yeah, it works, basically just by taking the current database offline, copying the .mdf and .ldf files to the new server, and attaching the database.

Backup / restore won't work, as it gives sort order errors...

As for why not have a defaul sort order, I don't know - just ask whoever built the original server!!

So given that I've got it to work, is this a good idea, or should I DTS the data accross (which would take a lot longer!)?|||If there are different sort orders, you can setup the new server with old server's configuration and use BACKUP/RESTORE method.

If not DTS is only way to get the data out from source database.|||Yeah, but I actually WANT to change the sort order to the default.

If DTS is the best way of doing this rather than the way I've desribed above, is there any way of setting the DTS package not to get logged, as this is a pain when migrating a large database...

Cheers!

Sunday, March 25, 2012

Attach an aspnet or sql2005 database on a sql2000 server

Hello

I want to attach an ASPNETDB database (generated by the asp.net login wizard system), which is a sql2005 .mdf database I think, to our SQL2000 server.

I tried to attach the file directly ; then to attach it to a sql2005 express server, "turning it" into a sql2000 database via the properties, then make a backup, then restore the backup on the 2000 server ; nothing worked out !
One of the method I tried (I don't remember which one) told me it could'nt read the sysindexes table ; of course, because there isn't such table on sql2005 databases.

So, is there a way to attach a SQL2005 database (so with no or few system tables) to a SQL2000 server (which requires those tables), or to re-generate the ASPNETDB in the SQL2000 format ?
If I re-create the syssomething tables on the SQL2005 database, will it work that simply ?

At the very last, I may have to install SQL express on the server. If there is already a SQL2000 server on the machine, will it cohabit with no problem ? Is the SQL express server ready for a production server with light or medium load ?

Thanks a lot, and sorry for so many questions ! :)

Hi,

"I want to attach an ASPNETDB database (generated by the asp.net login wizard system), which is a sql2005 .mdf database I think, to our SQL2000 server."

-That′s not working, the format is different to SQL Server 2k5, there is no backward compatibility.

""turning it" into a sql2000 database"

-Making the compatibility level to 2000 doesn't mean that the database is 2000 ready, it just behaves on a SQL2k5 machine like a SQL 2k database.

You will either have to script the object and the data out or bcp the data out or use any wizard to transfer the objects to the other SQL 2000 Server machine.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Ok, and if I export the database structure as a SQL script, will it just work ?

And for the SQL2005 Express server, is it usable along with the SQL2000 server, and does it fits for a ligt-load production server ?

thanks !
|||

Hi,

sure as long as you don′t use any new features of SQL Server 2005 and you take care of the difference of schema and owner you should be fine.

SQL 2k and SQL2k5X is working together. It can be also used as a light load production server (whatever that means in your case :-) ), it is only limited by the limitations of SQL Server Express, no query governor or anything else.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

Thursday, March 29, 2012

attach multiply databases

attach multiply databases

Attach db to sql 2005 express edition

attach db to .net2 project

Attach DB problem

Attach DB from SQL7 into SQL2000

Attach DB from SQL7 into SQL2000

Tuesday, March 27, 2012

Attach DB from SQL7 into SQL2000

Attach database to SQL2005 from old MSDE database

Attach database between different sort orders

Sunday, March 25, 2012

Attach an aspnet or sql2005 database on a sql2000 server

Asp.net / sql help

Blog Archive

About Me