SQLRNNR (2/18/2014)
Jeff Moden (2/18/2014)
IIRC correctly, there was a bug that cause this behaviour depending on the INITIAL SIZE and GrOWTH SETTINGS of a database in SQL Server 2005. I believe that SP3 fixed it. What service pack is your 2005 instance sitting at?According to the OP, this is a 2012 instance. I wonder if it was re-introduced.
Could be. They've supposedly fixed things like the connection leaks reportedly cause by sp_OA* usage, what, 17 times now? 😀
--Jeff Moden
Change is inevitable... Change for the better is not.