fragmentation question

Running IDS10.0.uc5 on aix5.3. We have a table that has some bad queries written against it that are having poor performance now. It is also a pretty wide table, lots of varchars. We aren't going to re-write the queries at this minute, but instead I am going to fragment the table. Investigating fragmenting it on the date_notified field. My question is, that even though I know the queries that filter on date_notified will work much quicker because they can do fragment elimination, I'm sure other queries will suffer, especially if I leave the indexes alone which will cause them to go into the data fragments. Is it best in this circumstance to just put the indexes in a separate unfragmented dbspace ? They have one composite index with date_notified. It is some other column and date_notified. I am thinking to drop that index, make one that is just date_notified and have that one follow the fragmentation scheme of the table. Then create a new index for the other column of the index I just dropped. That, and the rest of the indexes to go in a separate dbspace all together. Is this how it's done or are there any suggestions ? Thanks, Floyd