Re: SQL Table Create

On Fri, Feb 3, 2017 at 6:45 AM, (WalzCraft) Jerry Forss <
JForss@xxxxxxxxxxxxx> wrote:

First question:
Is it a good standard practice to create the table with no keys and use
the Create Index?

​NO. Every table should have a primary key defined.​

Arguably, a table without a primary key doesn't meet the definition of a
relational table.

This is not new, your DDS PF's should have had a unique key defined.

Second question:
The table I want to replace is a comment file that has the comments broken
into 50 char chunks.
The user enters 50 char at a time, hits enter to add the record, tries to
remember where they left off and continues to add.
What a mess. It was created in 1989.

I created a new pgm that splices all the 50 char records together,
displays a single 2400 char field that they can add to and insert into the
middle of. I then re-parse the field into 50 char chunks again.

There are about 25 million records with the 50 char comment.

In the new table it will have a 2400 varchar field. I would guess that
90%+ of the records will not ever be displayed again.
For the Allocate clause should I still use the average length of the real
comment, say 150 or leave it at 0?

I'd probably go with non-zero. Disk is cheap, CPU not so much.
But I'd look at not just the average, but the distribution of lengths...

But since 90% aren't used again, if you want the most efficient use of
space, go with 0.

Charles