SQL Server 7 and 2000 are capable of dynamically increasing the size of database files based on configuration limits.

>> It seems rather odd that with terrabytes of empty disk space something like this could derail an entire applcation.

Most people don't put their transaction log on a drive with a TB of space unless the activity is enough to warrent it.

If all you want to do is to move the row from one table to another and the schemas are similar, I think I'd first look at using INSERT..SELECT. If you want to do any manipulation of the data, you might be able to stay with INSERT..SELECT pending the severity of the changes or you could go to DTS. Of course, you could just go with DTS since that's what the product was designed for.

-Mike

>The 25K is in one table <g>.
>
>I have experienced firsthand the problem with transaction logs while working on an ecommerce project in SQL 6. Fortunately, I wasn't the DBA; it was pretty ugly. But I thought one of the "Features" of later versions is that the database could adjust dynamically. It seems rather odd that with terrabytes of empty disk space something like this could derail an entire applcation.