Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Table Partitioningq

4 posts in Product Futures Discussion Last posting was on 2002-02-07 18:39:34.0Z
kevbo Posted on 2002-01-25 17:50:20.0Z
From: kevbo
Date: Fri, 25 Jan 2002 12:50:20 -0500
Newsgroups: sybase.public.ase.product_futures_discussion
Subject: Table Partitioningq
Message-ID: <FE5EB5DCC3EE23910061FE0585256B4C.0061FE1A85256B4C@webforums>
Lines: 16
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:853
Article PK: 94381

Real, ddl-defined table partitioning where I can specify my own
partitioning algorithm. Eg.:

create table foo ( f1 int, year int, ...,
partition by year (2000 on tablespace1,
2001 on tablespace2,
default on tablespace3 )

In conjunction w/ this, the query optimizer, locking mechanisms, etc. know
how to completely ignore partitions that don't apply to submitted queries.
In this way, you can treat your table as if it were separate physical
tables: truncate/rebuild 1 partition while users are using the others.

Don't confuse this w/ current Sybase "partitioning" term where you get
multiple last pages for "heap" inserts. That's helpful for bulk loads, but
that's about it.


Tricia Posted on 2002-02-07 13:32:35.0Z
From: "Tricia" <tricia.crighton@travelex.com>
References: <FE5EB5DCC3EE23910061FE0585256B4C.0061FE1A85256B4C@webforums>
Subject: Re: Table Partitioningq
Date: Thu, 7 Feb 2002 13:32:35 -0000
Lines: 30
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <lpVmwy9rBHA.304@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: 195.99.138.2
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:797
Article PK: 94326

Hi,

I believe this will be a feature of ASE v14, if I remember correctly.
If not it certainly needs to be.

Regards,
Tricia.

<kevbo> wrote in message
news:FE5EB5DCC3EE23910061FE0585256B4C.0061FE1A85256B4C@webforums...
>
> Real, ddl-defined table partitioning where I can specify my own
> partitioning algorithm. Eg.:
>
> create table foo ( f1 int, year int, ...,
> partition by year (2000 on tablespace1,
> 2001 on tablespace2,
> default on tablespace3 )
>
> In conjunction w/ this, the query optimizer, locking mechanisms, etc. know
> how to completely ignore partitions that don't apply to submitted queries.
> In this way, you can treat your table as if it were separate physical
> tables: truncate/rebuild 1 partition while users are using the others.
>
> Don't confuse this w/ current Sybase "partitioning" term where you get
> multiple last pages for "heap" inserts. That's helpful for bulk loads, but
> that's about it.


Rob Verschoor Posted on 2002-02-07 18:39:34.0Z
Reply-To: "Rob Verschoor" <rob@DO.NOT.SPAM.sypron.nl>
From: "Rob Verschoor" <rob@DO.NOT.SPAM.sypron.nl>
References: <FE5EB5DCC3EE23910061FE0585256B4C.0061FE1A85256B4C@webforums> <lpVmwy9rBHA.304@forums.sybase.com>
Subject: Re: Table Partitioningq
Date: Thu, 7 Feb 2002 19:39:34 +0100
Lines: 46
Organization: Sypron B.V.
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <GeJ32nAsBHA.204@forums.sybase.com>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: p0329.spl.euronet.nl 194.134.112.73
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:796
Article PK: 94322

I believe the next major release would indeed have value-based
partitioning.
ASE "14" has been renamed "15", BTW.

Rob V.

"Tricia" <tricia.crighton@travelex.com> wrote in message
news:lpVmwy9rBHA.304@forums.sybase.com...
> Hi,
>
> I believe this will be a feature of ASE v14, if I remember
correctly.
> If not it certainly needs to be.
>
> Regards,
> Tricia.
>
>
> <kevbo> wrote in message
> news:FE5EB5DCC3EE23910061FE0585256B4C.0061FE1A85256B4C@webforums...
> >
> > Real, ddl-defined table partitioning where I can specify my own
> > partitioning algorithm. Eg.:
> >
> > create table foo ( f1 int, year int, ...,
> > partition by year (2000 on tablespace1,
> > 2001 on tablespace2,
> > default on tablespace3 )
> >
> > In conjunction w/ this, the query optimizer, locking mechanisms,
etc. know
> > how to completely ignore partitions that don't apply to submitted
queries.
> > In this way, you can treat your table as if it were separate
physical
> > tables: truncate/rebuild 1 partition while users are using the
others.
> >
> > Don't confuse this w/ current Sybase "partitioning" term where you
get
> > multiple last pages for "heap" inserts. That's helpful for bulk
loads, but
> > that's about it.
>
>


Johan Posted on 2002-01-28 08:32:41.0Z
From: Johan
Date: Mon, 28 Jan 2002 03:32:41 -0500
Newsgroups: sybase.public.ase.product_futures_discussion
Subject: Re: Table Partitioningq
Message-ID: <460378A51E5F3C52002EF03985256B4F.006AF7AA85256B4C@webforums>
References: <FE5EB5DCC3EE23910061FE0585256B4C.0061FE1A85256B4C@webforums>
Lines: 26
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:843
Article PK: 94371

I think this is a VERY good idea.

Allowing inserts/updates on views with unions on such tables will also be a
usefull feature,
and it should then cater for row-migration if updating the partition key.

Johan



Real, ddl-defined table partitioning where I can specify my own
partitioning algorithm. Eg.:

create table foo ( f1 int, year int, ...,
partition by year (2000 on tablespace1,
2001 on tablespace2,
default on tablespace3 )

In conjunction w/ this, the query optimizer, locking mechanisms, etc. know
how to completely ignore partitions that don't apply to submitted queries.
In this way, you can treat your table as if it were separate physical
tables: truncate/rebuild 1 partition while users are using the others.

Don't confuse this w/ current Sybase "partitioning" term where you get
multiple last pages for "heap" inserts. That's helpful for bulk loads, but
that's about it.