25000 records is not a lot for SQL Server to handle... I have clients with tables in the 10's of millions of records, and performance is fast and furious! In 10 years, you would only have 3,000,000 records in your biggest table - that's not a lot.

I have never been an advocate of moving data to a history table because when I want to see multiple months/years/whatever, I have to join them back together and take a chance of losing information 1)on the move to history, and 2) on the joining back. So from a business standpoint, IMO it is a bad idea to move the data to separate tables.

>We're trying to keep them "lean and mean" for the benefit of everyone, but especially remote users who only have dialup access <g>

That should not be a problem if you have views of the data that are created correctly.

>
>I've looked at BCP but it's a bit of a pain to have to drop and rebuild the indices each time. I thought there might be other options.

Seems to me that DTS would be the simplest to implement what you need - you are moving all records to a new table, and deleting all records in the current database. Either that, or a fox program to do the same thing. Select all records from the source to the target, run validation reports to confirm the data is exactly the same, delete from source.