If the COLUMNS that comprise the CLUSTERED index are monotonically increasing (that is, new row key values are greater than those previously inserted) the following System 11 dbcc tune will not split the page when it’s half way full. Rather it’ll LET the page fill and then allocate another page: 
dbcc tune(ascinserts, 1, “my_table”) 
By the way, SyBooks is wrong when it states that the above needs to be reset when ASE is rebooted. This is a permanent setting.
 To undo it:
dbcc tune(ascinserts, 0, “my_table”)

If the columns that comprise the clustered index are monotonically increasing (that is, new row key values are greater than those previously inserted) the following System 11 dbcc tune will not split the page when it’s half way full. Rather it’ll let the page fill and then allocate another page: 
dbcc tune(ascinserts, 1, “my_table”) 
By the way, SyBooks is wrong when it states that the above needs to be reset when ASE is rebooted. This is a permanent setting.
 To undo it:
dbcc tune(ascinserts, 0, “my_table”)