Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Colin Bull — — source: Usenet: comp.databases.informix
I thought the best way to do this was try and fragment you data on a function of the deletion, ie, if you purge your data every
month, fragment over 12 dbspaces.
Then just drop the one to be purged.
I have promised myself I am going to test this real soon.
Colin Bull
c.bull@videonetworks.com
> -----Original Message-----
> From: owner-informix-list@iiug.org
> [mailto:owner-informix-list@iiug.org]On Behalf Of B.Johnson
> Sent: 28 January 2004 15:07
> To: informix-list@iiug.org
> Subject: Update Statistics versus Recreate table after large purge
>
>
> Quick question as to what is the most effective and expediant way to
> handle a large table purge. Should we ...
>
> A) run the purge and then run Update Stats with Drop Distributions.
>
> or
>
> B) make a copy of the table ... run sql to get records you want to
> keep ... verify data ... rename old table ... rename new table ...
>
> Time is of essence here ... as far as execution.
>
sending to informix-list
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.