There are certain operational tables in Banner that, over time, grow to a point where they begin to affect system performance. Whether it is student accounts, registration, data integration events or any of several others, you will eventually no longer need to have the older records from those tables in your operational database. Usually, you can just purge the aged records and recognize an immediate boost in performance, but in some cases policy or Law may require that you keep that data readily available for several years. The Purdue University Banner team has developed and automated an archive and purge process that greatly simplifies the maintenance of aged data. Database administrators in particular will benefit from this detailed review of our process and discussion of the various obstacles we had to overcome to make the process work.