"Is there anything we can do on this end, from a front end application design, that will minimize the log size or is that something we will just have to live with and manage with the backing up and truncating of the log on SQL?" Something that you may want to consider adding to either a "maintenance plan" or just a recurring job is to schedule a normal transaction log backup ever x hour (you fill in the time frame). Note, the normal transaction log backup versus a backup log truncate only command. Or if your disaster recovery requirements a such that you do not need a "point in time" restore, consider (gulp) setting your database to simple recovery and let SQL Server truncate the log upon evey checkpoint. If you have turned on 'auto shrink' then I assume that the transaction level on the SQL Server is relatively low ... so setting the server in an trunc. on checkpoint mode should not adversly affect the performance of the database ... only your ability to restore to a particular point in time in the event of a SQL Server crash. Your restore will only bring you back to the point of the last restore. Hope that this helps ....