Thank you for your suggestion! Unfortunately, when I do this, it places the partition dtrange2015q3 into the iseg15 segment, and it no longer lives in the dseg15 segment. This happens to all table partitions. They move from the specified segment in the create table statement, to the segment specified in the create index statement. The segments you have in your example belong to the same database and device. The segments in my example, belong to the database database, but different devices. Perhaps that is what is causing this to occur. I did adjust my scripts to specify the table partition and segment. This seems to be keeping my table partition in the segment that is specified in the create table statement, and create the index partition in the same segment as the table partition. I guess I'm okay with that design. I was hoping to separate the index partitions out into a separate segment/device.
The create index syntax from Sybase documentation for the index partitions is the following:
index_partition_clause::=
[local index [partition_name [on segment_name]
[,partition_name [on segment_name]...]]]
So, then I created the my index this way:
CREATE clustered index idx1_audit_event
ON audit_event(audit_event_timestamp, audit_sequence, audit_object, audit_column_name, audit_object_id) ON index_infraseg local index event_M62015 on infraaudit2015seg, event_M72015 on infraaudit2015seg, event_M82015 on infraaudit2015seg, event_M92015 on infraaudit2015seg, event_M102015 on infraaudit2015seg, event_M112015 on infraaudit2015seg, event_M122105 on infraaudit2015seg, event_M12016 on infraaudit2016seg, event_M22016 on infraaudit2016seg, event_M32016 on infraaudit2016seg, event_M42016 on infraaudit2016seg, event_M52016 on infraaudit2016seg, event_M62016 on infraaudit2016seg, event_M72016 on infraaudit2016seg, event_M82016 on infraaudit2016seg, event_M92016 on infraaudit2016seg, event_M102016 on infraaudit2016seg, event_M112016 on infraaudit2016seg, event_M122016 on infraaudit2016seg, event_M12017 on infraaudit2017seg, event_M22017 on infraaudit2017seg
GO
This syntax is keeping the table partitions in the infraauditYYYYseg segments, and placing the index partitions into the infraauditYYYYseg as well. Not what I was going for, but it may be the best I can do. At least the data and indexes are now into the different segments/devices. I'm just trying to reduce the amount of I/O on the physical devices by keeping monthly data partitions for 1 year into 1 device. Maybe that is moot point with Sybase. I know with Oracle, DBA's like to have the data and indexes partitioned across many tablespaces for backup, maintenance and high availability (RAID) solutions.
Thanks again for your help.