Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: SQL Server
Expertise: Beginner
Oct 12, 1998



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Log truncation

My database and log keep filling up and I can't truncate the log. Any suggestions?

There are two methods to empty the transaction log. One can regularly dump the transaction log to a file. This is the preferred option, because the dumps can then be used as part of backup plan. If you are in development and do not care to maintain transaction dumps you can set the database to "truncate log on checkpoint." The Server will then automatically clear out all committed transactions from the log whenever a checkpoint occurs. If you are using one of the above methods and still find the log filling up, you should investigate whether you have a large enough log, are dumping often enough, or have a long running transaction that prevents the log from being dumped (DBCC OPENTRAN (database name)).

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date