DBCC Checkdb runs 12 hours

We have a really ancient Sql Server db -- version 6.5 --
with a 7.6 GB database on it. The DBCC Checkdb runs 12
hours, and now it fails every time it runs, without giving
any meaningful error messages. Is there some way to speed
up DBCC Checkdb? Or should we be running some other
utility?The best way to speed it up is to migrate to SQL 7.0 or better yet 2000. I
don't know of any way in 6.5.
Andrew J. Kelly
SQL Server MVP
"khabita" <anonymous@.discussions.microsoft.com> wrote in message
news:fc0901c3f24c$16443170$a001280a@.phx.gbl...
> We have a really ancient Sql Server db -- version 6.5 --
> with a 7.6 GB database on it. The DBCC Checkdb runs 12
> hours, and now it fails every time it runs, without giving
> any meaningful error messages. Is there some way to speed
> up DBCC Checkdb? Or should we be running some other
> utility?|||Thanks. But we are moving away from Sql Server, so I doubt
we'll upgrade. I guess we'll just have to live with the
slow performance until we move the db to Oracle.

>--Original Message--
>The best way to speed it up is to migrate to SQL 7.0 or
better yet 2000. I
>don't know of any way in 6.5.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"khabita" <anonymous@.discussions.microsoft.com> wrote in
message
>news:fc0901c3f24c$16443170$a001280a@.phx.gbl...
giving
speed
>
>.
>|||Too bad. It would cost you tons less just to upgrade to SQL Server 2000. I
did an upgrade in place (i.e. on the same box) from 6.5 to 7.0 and tripled
the speed of an app.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
<anonymous@.discussions.microsoft.com> wrote in message
news:f71201c3f25a$37fc35c0$a301280a@.phx.gbl...
Thanks. But we are moving away from Sql Server, so I doubt
we'll upgrade. I guess we'll just have to live with the
slow performance until we move the db to Oracle.

>--Original Message--
>The best way to speed it up is to migrate to SQL 7.0 or
better yet 2000. I
>don't know of any way in 6.5.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"khabita" <anonymous@.discussions.microsoft.com> wrote in
message
>news:fc0901c3f24c$16443170$a001280a@.phx.gbl...
giving
speed
>
>.
>

DBCC Checkdb runs 12 hours

We have a really ancient Sql Server db -- version 6.5 --
with a 7.6 GB database on it. The DBCC Checkdb runs 12
hours, and now it fails every time it runs, without giving
any meaningful error messages. Is there some way to speed
up DBCC Checkdb? Or should we be running some other
utility?The best way to speed it up is to migrate to SQL 7.0 or better yet 2000. I
don't know of any way in 6.5.
--
Andrew J. Kelly
SQL Server MVP
"khabita" <anonymous@.discussions.microsoft.com> wrote in message
news:fc0901c3f24c$16443170$a001280a@.phx.gbl...
> We have a really ancient Sql Server db -- version 6.5 --
> with a 7.6 GB database on it. The DBCC Checkdb runs 12
> hours, and now it fails every time it runs, without giving
> any meaningful error messages. Is there some way to speed
> up DBCC Checkdb? Or should we be running some other
> utility?|||Thanks. But we are moving away from Sql Server, so I doubt
we'll upgrade. I guess we'll just have to live with the
slow performance until we move the db to Oracle.
>--Original Message--
>The best way to speed it up is to migrate to SQL 7.0 or
better yet 2000. I
>don't know of any way in 6.5.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"khabita" <anonymous@.discussions.microsoft.com> wrote in
message
>news:fc0901c3f24c$16443170$a001280a@.phx.gbl...
>> We have a really ancient Sql Server db -- version 6.5 --
>> with a 7.6 GB database on it. The DBCC Checkdb runs 12
>> hours, and now it fails every time it runs, without
giving
>> any meaningful error messages. Is there some way to
speed
>> up DBCC Checkdb? Or should we be running some other
>> utility?
>
>.
>|||This is a multi-part message in MIME format.
--=_NextPart_000_023E_01C3F232.508BED60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Too bad. It would cost you tons less just to upgrade to SQL Server 2000. I
did an upgrade in place (i.e. on the same box) from 6.5 to 7.0 and tripled
the speed of an app.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
<anonymous@.discussions.microsoft.com> wrote in message
news:f71201c3f25a$37fc35c0$a301280a@.phx.gbl...
Thanks. But we are moving away from Sql Server, so I doubt
we'll upgrade. I guess we'll just have to live with the
slow performance until we move the db to Oracle.
>--Original Message--
>The best way to speed it up is to migrate to SQL 7.0 or
better yet 2000. I
>don't know of any way in 6.5.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"khabita" <anonymous@.discussions.microsoft.com> wrote in
message
>news:fc0901c3f24c$16443170$a001280a@.phx.gbl...
>> We have a really ancient Sql Server db -- version 6.5 --
>> with a 7.6 GB database on it. The DBCC Checkdb runs 12
>> hours, and now it fails every time it runs, without
giving
>> any meaningful error messages. Is there some way to
speed
>> up DBCC Checkdb? Or should we be running some other
>> utility?
>
>.
>
--=_NextPart_000_023E_01C3F232.508BED60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Too bad. It would cost you tons =less just to upgrade to SQL Server 2000. I did an upgrade in place (i.e. on the =same box) from 6.5 to 7.0 and tripled the speed of an app.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
wrote in message news:f71201c3f25a$37=fc35c0$a301280a@.phx.gbl...Thanks. But we are moving away from Sql Server, so I doubt we'll upgrade. I =guess we'll just have to live with the slow performance until we move the =db to Oracle.>--Original Message-->The best way to =speed it up is to migrate to SQL 7.0 or better yet 2000. I>don't =know of any way in 6.5.>>-- >>Andrew J. =Kelly>SQL Server MVP>>>"khabita" wrote in message>news:fc0901c3f24c$16443170$a001280a@.phx.gbl...>=> We have a really ancient Sql Server db -- version 6.5 =-- > with a 7.6 GB database on it. The DBCC Checkdb runs 12> hours, and =now it fails every time it runs, without giving> any meaningful =error messages. Is there some way to speed> up DBCC Checkdb? Or =should we be running some other> utility?>>>.>

---

--=_NextPart_000_023E_01C3F232.508BED60--

dbcc checkdb not needed?

"With SQL Server 2000, you're no longer required to run DBCC CHECKDB or DBCC
CHECKALLOC statements. The latest version of SQL Server automatically detects
damaged pages and fixes them. Ninety-nine percent of database corruption with
SQL Server 2000 happens due to hardware failures."
I read that on http://www.informit.com/articles/printerfriendly.asp?p=27784 and
I'm looking for confirmation if it's true or not?
I've searched in BOI for confirmation without success.
Thanks in advance,
Craig.That's not quite true. If you have torn pgedetection turned on (the
default) it can detect torn pages. But there are things DBCC CHECKDB can
detect other than that and should be run on a regular basis for reassurance.
You don't need to run CheckAlloc as it is already included in checkdb but
you should run CheckCatalog.
--
Andrew J. Kelly SQL MVP
"Craig" <spam@.[at]thehurley.[dot]com> wrote in message
news:ecTMYtxAEHA.2480@.TK2MSFTNGP11.phx.gbl...
> "With SQL Server 2000, you're no longer required to run DBCC CHECKDB or
DBCC
> CHECKALLOC statements. The latest version of SQL Server automatically
detects
> damaged pages and fixes them. Ninety-nine percent of database corruption
with
> SQL Server 2000 happens due to hardware failures."
> I read that on
http://www.informit.com/articles/printerfriendly.asp?p=27784 and
> I'm looking for confirmation if it's true or not?
> I've searched in BOI for confirmation without success.
> Thanks in advance,
> Craig.

dbcc checkdb not needed?

"With SQL Server 2000, you're no longer required to run DBCC CHECKDB or DBCC
CHECKALLOC statements. The latest version of SQL Server automatically detect
s
damaged pages and fixes them. Ninety-nine percent of database corruption wit
h
SQL Server 2000 happens due to hardware failures."
I read that on http://www.informit.com/articles/pr...dly.asp?p=27784
and
I'm looking for confirmation if it's true or not?
I've searched in BOI for confirmation without success.
Thanks in advance,
Craig.That's not quite true. If you have torn pgedetection turned on (the
default) it can detect torn pages. But there are things DBCC CHECKDB can
detect other than that and should be run on a regular basis for reassurance.
You don't need to run CheckAlloc as it is already included in checkdb but
you should run CheckCatalog.
Andrew J. Kelly SQL MVP
"Craig" <spam@.[at]thehurley.[dot]com> wrote in message
news:ecTMYtxAEHA.2480@.TK2MSFTNGP11.phx.gbl...
> "With SQL Server 2000, you're no longer required to run DBCC CHECKDB or
DBCC
> CHECKALLOC statements. The latest version of SQL Server automatically
detects
> damaged pages and fixes them. Ninety-nine percent of database corruption
with
> SQL Server 2000 happens due to hardware failures."
> I read that on
http://www.informit.com/articles/pr...dly.asp?p=27784 and
> I'm looking for confirmation if it's true or not?
> I've searched in BOI for confirmation without success.
> Thanks in advance,
> Craig.