Hi Bernie

No, I don't think the engine has a problem. I think it's just wise to:

Backup at LEAST daily - how much work can you afford to lose?

While you're at it backing up, why not PACK keys - since AUTOCHK doesn't
check indexes, the safest way to be sure your indexes are OK is to rebuild
them daily.

And rebuilding indexes improves speed because it means R:Base has up to date
info in SYS_INDEXES to help the query optimizer build fastest retrieval
possible.

BTW, while mentioning speed, just though I'd pass on that I'm working on a
new application with very complex structure, where the daily basic query
needed is a five SELECT union, each of which uses from 8 to 11 tables!  I
tried all the tricks I could to get speed to where I and the client would
accept it, and then said, "What the heck, let's try on R:Base 7.0!"  And it
was TWICE the speed!!

David Blocker

----- Original Message -----
From: "Bernard Lis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 21, 2002 9:06 AM
Subject: Re: Corrupt Indexes


> David,
> Why do you feel that it is necessary to pack keys every day.  Is this a
> signal that you suspect the "Industrial Strength" engine has a problem?
> I have one customer that has corruption repeatedly and I can't get to the
> bottom of it.  I tried Pack Keys once and it didn't help.  They are
running
> dos and win 6.5++ 1.851
> We've tried rotating the unuse (if there is such a word) of workstations
to
> see if one of them is causing the problem.
> No positive results so far.
>
> Bernie Lis
> Megabytes, Inc.
>
> ----- Original Message -----
> From: "David M. Blocker" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, August 21, 2002 9:07 AM
> Subject: Re: Corrupt Indexes
>
>
> > Because of the importance of indexes, the DAILY backup routine that I
have
> > all my clients do does the following:
> >
> > SET MULTI OFF
> > CONNECT  dbname
> >   -  abort if you can't connect
> > AUTOCHK dbname
> >   - abort if problem
> > PACK KEYS (rebuilds all indexes)
> > COPY .... (backup)
> >
> > David Blocker
>
>
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
>


================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to