HP3000-L Archives

March 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Denys Beauchemin <[log in to unmask]>
Reply To:
[log in to unmask][log in to unmask]]
Sent: 11 March 1999 12:57
To: [log in to unmask]
Subject: 947 replacement [...]36_11Mar199911:49:[log in to unmask]
Date:
Wed, 10 Mar 1999 10:24:00 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
X-no-Archive:yes
Nick has a good point.  I usually recommend that all datasets be at the
same size and that this size be 2048 words or 4096 bytes.  If this is too
large, you might try 512 words or 1024 words.

Kind regards,

Denys. . .

Denys Beauchemin
HICOMP America, Inc.
(800) 323-8863  (281) 288-7438         Fax: (281) 355-6879
denys at hicomp.com                             www.hicomp.com



-----Original Message-----
From:   Nick Demos [SMTP:[log in to unmask]]
Sent:   Wednesday, 10 March, 1999 10:20 AM
To:     [log in to unmask]
Subject:        Re: Howmessy Help

Curt Narvesen wrote:
>
> I have a client with performance problems on their database. I have run a
how
> messy report and identified several datasets that could use repacking
based upon
> the elongation values. Besides adding or deleting paths, is there
anything else
> that I can look at to help improve their database efficiency?
>
Curt, look at the block sizes, which could be important depending
on
how the data base is accessed.

Nick D.

ATOM RSS1 RSS2