Restrictions on Partition Keys and Bound Values for Range-Partitioned Tables

Partition bounds must be in ascending order according to the order in which the partitions were created. That is, the upper bound for the second partition must be higher than for the first partition, and so on.

In addition, partition bound values must be compatible with the corresponding partition-key column datatype. For example, varchar is compatible with char. If a bound value has a different datatype than that of its corresponding partition-key column, SAP ASE converts the bound value to the datatype of the partition-key column, with these exceptions: