if somebody could throw some light, if creating indexes are better
than enabling indexes. Also does update stats work better with
creating
indexes or when indexes are enabled.

I was trying to avoid a lengthy discussion, but I guess nobody else is
jumping in.

I think what you are asking is whether it is better to disable an index,
load a bunch of data, and then enable the index. The answer is, of course,
that it depends. If you are going to push a lot of data into the table,
then it will be quicker to re-create the index. If we are talking one or
two rows, then what is the point of disabling the index?

Your update statistics question is unclear. Having an index will not
improve the performance of update statistics. The guidelines call for
updating statistics high on columns which are indexed. I would check out
ak_util from the iiug site for a guide from the master on this topic.

Cheetah has a feature where statistics are gathered while the index is being
created, thus obviating the need to update stats after the index creation.

j.

-----Original Message-----
From: informix-list-bounces (AT) iiug (DOT) org
[mailto:informix-list-bounces (AT) iiug (DOT) org]On Behalf Of
mohitanchlia (AT) gmail (DOT) com
Sent: Monday, June 18, 2007 8:27 PM
To: informix-list (AT) iiug (DOT) org
Subject: create indexes vs enable indexes


if somebody could throw some light, if creating indexes are better
than enabling indexes. Also does update stats work better with
creating
indexes or when indexes are enabled.

_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list

Jack Parker wrote:

Some statistics are gathered. Not all that a column with an index should have...

--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...

On 19 Jun, 23:05, Fernando Nunes <s... (AT) domus (DOT) online.pt> wrote:
So this feature that was ported from DB2 is crap then? Typically half-
baked implmentation from another product.

Why does it not built everything if it has read and sorted the columns
already?

david (AT) smooth1 (DOT) co.uk wrote:
Err... this is hardly a "feature that can be ported". The way statistics are
gathered and represented is completely different. You may say the idea was
ported... I don't know... But in this case it was not necessarily from DB2. I
imagine most databases do this... or should do...

As for your specific question, the definition of what are the statistics that a
column "should" have is not absolute... It really depends on the column, the
data and the queries.. It collects medium distributions for the column heading
and index... And LOW for the index itself...
It does not collect distributions for other columns in the index... And you may
like distributions in high mode for the heading column...

For more information about the modes and best practices please check the
performance guide.

This area will hopefully see more autonomic stuff in the future...

--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...