Jack,

Nope. Transaction logging is a very important component to SQL Server.

Now, for work-arounds. Probably the easiest is to enable the Truncate Log on Checkpoint database option. With this option enabled, SQL Server will throw away inactive transaction entries (those not participating within a transaction) when ever a checkpoint occurs - which is roughly once a minute.

If this is a production server, I would highly suggest that the option be re-enabled as soon as your upload is completed. You will also have to make a full database backup before you'll be able to continue with transaction log backups.

If you're submitting the changes within a transaction, you'll probably have to break the changes up into smaller transactions.

-Mike