Re: Chained Rows

From: Kenny Payton <k3nnyp_at_gmail.com>
Date: Thu, 24 Apr 2014 05:36:25 -0400
Message-ID: <CAEidWqMmAkpMYk1vrZWmMZ5Cu8E3N9hPS+B8pLK4RmUHt=goZQ_at_mail.gmail.com>



Yes. List partitioned.
On Apr 23, 2014 10:21 PM, "Karth Panchan" <keyantech_at_gmail.com> wrote:

> Is table partition possible here?
>
> Karth
>
>
> On Apr 23, 2014, at 6:29 PM, Kenny Payton <k3nnyp_at_gmail.com> wrote:
>
> 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 - 11:36:25 CEST

Original text of this message