Re: optimal size for rollback

Karen Abgarian <abvk_at_ureach.com> wrote in message news:<3D8AB02F.422B5E88_at_ureach.com>...
> I would phrase it as: a properly written application should not let the users
> leave uncommitted transactions for undefined amount of time. Not only because
> of rollback segments.
>
> These systems should not exist but they do. And these problems do happen.
> Speaking of DBA's take on this, their involvement should be limited to spotting
> such things and preventing service loss that might be caused by them. Speaking
> of application support or development, they should redesign or fix these things
> if at all possible.

I absolutely agree with you. Just such applications are rare. They may exist in a training course but don't survive in production environment for long.

Also (as you can see from my prev posts) I agree with you on performance impact (negligible in real life) and optimal (should be used).

But what I like most is how you stay polite and patient. To me (not native speaker though) some Howard's remarks sound rude to the point to be insulting. His understanding of $Subject shows lack of real-life experience. It's ... OK, better not to bring horses in :)  

> Regs
> AK

Regards,
Igor Received on Sun Sep 22 2002 - 06:23:35 CDT