Subject | Re: Update is Slow |
---|---|
Author | sivram_mail |
Post date | 2003-06-05T14:40:52Z |
Hi SET,
if i do "update" operation after some huge deletion , what will
happen?Is there any difference in updation after huge delete?
Sivaraman
--- In ib-support@yahoogroups.com, Svein Erling Tysvaer
<svein.erling.tysvaer@k...> wrote:
if i do "update" operation after some huge deletion , what will
happen?Is there any difference in updation after huge delete?
Sivaraman
--- In ib-support@yahoogroups.com, Svein Erling Tysvaer
<svein.erling.tysvaer@k...> wrote:
>statement
> >I have thought trigger that cause the problem. However, the trigger
> >is nothing to do with this field. Moreover, the update performance
> >does not improve although I remove the trigger.
>
> Well, then we need a lot more information to help you, because this
>only a
> >When I issued the below sql query:
> > update HistCurr set IndiInitialized = 1
>
> by itself should execute within second(s) when the table contains
> few thousand records.difference
>
> Though there is one thing you haven't answered yet: What is the
> between next transaction and oldest active transaction (OAT)?Another
> question is if you run this statement by itself, or as part of alarger
> operation, e.g. following a huge delete.
>
> Set