A bit more background.... We are self-hosting a vendor supplied application so I didn't think about changing with the physical database attributes. Additionally because the vendor is rather tight with their code I can't really go in and make any assessments on their code and why it is bloating the database the way it does.

The best I can do is reach out to the vendors technical team to inform them of what is going on to see if they can remedy the issues going forward. What appears to be odd is the fact that this process that is bloating the database has been in place since we went live with this system. I have to see if someone can point me to a change request that would have changed the dynamics of this process.

Thanks for the heads up on pre-allocating the database size.

Now on a related point, on the auto growth feature of SQL Server, my first impression is that the database will grow during a load process, which would make sense. I have found situations where it appeared the database was somewhat quiet and found it to grow. Could that be possible?

Thanks again.

Kurt