Re: IDS Next Version - features wanted.
How about a simple command to complete page version conversion. Most,
probably all, people use something like "UPDATE foo SET bar = bar WHERE
1 = 1". This simple query is used by many to get rid of IPA's and for
large chunk conversion. The issue that I have is that this is a logged
action and therefore is vulnerable to long transactions. Since it is a
dummy update I see no reason why it actually needs to be logged.
Options that come to mind for syntax are:
1) Optimizer is smart enough to recognize the pattern and avoid logging
for that type of statement, I'd imagine that is harder to do than it
sounds and probably opens the door for many bugs/issues.
2) An UPDATE STATISTICS statement that will force this update, i.e.
"UPDATE STATISTICS DUMMY UPDATE ON foo". This seems like the wrong
place for this functionality but sounds like it would work.
3) An onmode/onparams/onstat/onsomething command that will perform the
page conversion behind the scenes, unlogged.
4) An addition to the SQL library so that something like "UPDATE foo
FOR PAGE CONVERSION" or "UPDATE foo CONVERT PAGES" ... that will do the
action unlogged.
You probably get the idea by now. :)
david@smooth1.co.uk wrote:
> What features do you want for the next version of IDS?
>
> The Key Features in IDS Version 10.00 by Jerry Keesee
>
> mentions...
>
> - Smooth Upgrade of HDR
> - Online table re-org
> - Dynamic Reconfiguration
> - Auto Update Stats
> - Auto Disk Mgmt
> - RAS
> - Autonomics
>
>
> a) What does Smooth Upgrade of HDR mean?
>
> b) What else do people want as features?
>
> David.
How about 1 primary server to N secondary servers for HDR instead of just 1
primary to 1 secondary?
Carlton Doe brought this up at IDUG 2005, would anyone else be interested in
this feature?
Andrew
"Redden96" <Redden96@yahoo.com> wrote in message
news:1119364729.758706.65940@g43g2000cwa.googlegroups.com...
> How about a simple command to complete page version conversion. Most,
> probably all, people use something like "UPDATE foo SET bar = bar WHERE
> 1 = 1". This simple query is used by many to get rid of IPA's and for
> large chunk conversion. The issue that I have is that this is a logged
> action and therefore is vulnerable to long transactions. Since it is a
> dummy update I see no reason why it actually needs to be logged.
>
> Options that come to mind for syntax are:
>
> 1) Optimizer is smart enough to recognize the pattern and avoid logging
> for that type of statement, I'd imagine that is harder to do than it
> sounds and probably opens the door for many bugs/issues.
>
> 2) An UPDATE STATISTICS statement that will force this update, i.e.
> "UPDATE STATISTICS DUMMY UPDATE ON foo". This seems like the wrong
> place for this functionality but sounds like it would work.
>
> 3) An onmode/onparams/onstat/onsomething command that will perform the
> page conversion behind the scenes, unlogged.
>
> 4) An addition to the SQL library so that something like "UPDATE foo
> FOR PAGE CONVERSION" or "UPDATE foo CONVERT PAGES" ... that will do the
> action unlogged.
>
> You probably get the idea by now. :)
>
> david@smooth1.co.uk wrote:
> > What features do you want for the next version of IDS?
> >
> > The Key Features in IDS Version 10.00 by Jerry Keesee
> >
> > mentions...
> >
> > - Smooth Upgrade of HDR
> > - Online table re-org
> > - Dynamic Reconfiguration
> > - Auto Update Stats
> > - Auto Disk Mgmt
> > - RAS
> > - Autonomics
> >
> >
> > a) What does Smooth Upgrade of HDR mean?
> >
> > b) What else do people want as features?
> >
> > David.
>