Hello,

Can Sybase do the following?

Used to benefit selects that perform table scans or index scans not DML
statements. There are not multiple last pages using this approach. Only 1
last page.

Example)
CREATE DATABASE JUNKDB
ON dev001 = 500
,dev002 = 500
,dev003 = 500
,dev004 = 500
,dev005 = 500
LOG
ON dev010 = 250
go

SEGMENT(S):
seg001 on dev001, dev002, dev003, dev004, dev005

TWO OPTIONS FOR STRIPING
===============================================================================================================
I) CIRCULAR STRIPING
extent allocation from low to high device number

FROM LOW DEV NUM TO HIGH DEV NUM USING ROUND ROBIN APPROACH FOR EXTENT
PLACEMENT.
sysgrowthallocations( id int not null, -- Object ID
num_allocations int not null, -- Number Allocated On
Current Device SINCE LAST SWITCH
cur_dev_num int not null, -- Current Device
Receiving Extent Allocations
allocations int not null, -- Number Of Extents
To Allocate Before Switch
segid int not null, -- ID Of Segment
Object Is Located On
PK(id)

II) BALANCED STRIPING
===============================================================================================================
extent allocated on device with lowest number of extent allocations
then extent allocation from low to high device number

A Control Page For Each Fragment Contains The Extent IDS For All Extents
Allocated On That Fragment.
Extents Linked Via Pointers Based On Allocation Order And/Or Cluster Order
And/Or Index Order.

Control Page is used for queries that perform table scans or index scans as
a parallel thread can be used to process the extents and pages for each
device for the object.

Thanks,
Ryan Putnam