An application that is 99% inserts runs for between 6 and 12 hours then performance suffers dramatically. Say every 2 minutes the application inserts 40,000+ records and takes less than 1 minute to do so. After 6 to 12 hours the time increases to 15 minutes. Restarting the database will cause the performance to return. There is a clustered primary key on the tables identity column, and 2 non-unique single column indexes on the table (1 foreign key, 1 on a time field). I'm stumped as to what to look for. Misc info, the database grows ~1.5GB per day and is maintained between 75GB and 150GB (purged monthly).