tomnibus Posted April 10, 2007 Report Share Posted April 10, 2007 Most of you probably limit your transaction log files. However, with an application we have installed, they have it set NOT to limit the file. So, for one of our databases it's 37GB. Our DBA suspects that the reason why it's so large is because Retrospect's Agent is creating them. However, if that were true, the second database which is set to the same is not having the same problem. Any ideas on this? Quote Link to comment Share on other sites More sharing options...
sporri Posted May 14, 2007 Report Share Posted May 14, 2007 The reason for the large transaction log is because you have not made a transaction log backup of the database. http://support.microsoft.com/kb/272318 Quote Link to comment Share on other sites More sharing options...
erins Posted July 16, 2007 Report Share Posted July 16, 2007 Yes, I am looking for how to work with large transaction log, I find DBCC SHRINKFILE will slow sql server. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.