Re: Chained Rows

From: Kenny Payton <k3nnyp_at_gmail.com>
Date: Wed, 23 Apr 2014 18:29:43 -0400
Message-ID: <CAEidWqPe86S72Bw5Y=EsEfJm+ZJtajPNdpjsh8HTa_FiTg3_mA_at_mail.gmail.com>



Thanks.

Unfortunately the data and access patterns change pretty frequently. Another reason we find ourselves in this situation. On Apr 23, 2014 6:02 PM, "Sayan Malakshinov" <xt.and.r_at_gmail.com> wrote:

>
> On Thu, Apr 24, 2014 at 12:56 AM, Kenny Payton <k3nnyp_at_gmail.com> wrote:
>>
>> I know a lot of the tricks for avoiding chained rows and migrated rows
>> but the only trick I know of to element these intra or inter block chained
>> rows is to break the table into multiple tables or the row into multiple
>> rows.
>
>
> Sometimes might be helpful to redefine table with moving less-used columns
> to the ends of rows. It allows to reduce extra-work if most queries use
> only the first columns
>
> --
> Best regards,
> Sayan Malakshinov
> Senior performance tuning engineer
> PSBank
> http://orasql.org
>

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Apr 24 2014 - 00:29:43 CEST

Original text of this message