Another technique to speed large delete jobs when a maintenance window
may not be available would be to use the parallel query option, PQO,
against the table. This again would require lots of rollback but you
should be able to cut the clock time.
Finally if a lack of rollback space is the main issue then why not run
the delete as a series of delete steps where each step limits itself to
N number of rows? This may not be a slick as a single delete
step/statment but this method can often eliminate a large quantity of
data without taxing the capacity of the system too heavily.
HTH -- Mark D Powell --