SharePoint - content database transaction log files (LDF)

All replies

• 

  

  0

  Sign in to vote

  you can shrink the transaction log. Transaction is important for SQL server.

  read these 2  article will help you understand: http://blogs.technet.com/b/wbaer/archive/2007/05/08/database-management-concepts-for-large-and-growing-content-databases.aspx

   

  and http://drewmace.blogspot.com/2008/02/sql-database-management-for-sharepoint.html

   

  hope this help

  thanks

  -ws

  ---

  SharePoint administrator, MCTS,MCITP

  Thursday, December 9, 2010 2:56 PM
• 

  

  0

  Sign in to vote

  You need to find out why you sharepoint server is generating too many large log files. Normally they should be small in size. You may take a SQL profile trace to find it out. For the current log file, you can simply shrink it but remember it better to find out if that log file contains any data or its stuck in doing some transaction and then basically growing unwanted size.

  ---

  MCP & MCTS [WSS 3.0/MOSS] Visit: http://yagyashree.wordpress.com/

  Thursday, December 9, 2010 3:05 PM
• 

  

  0

  Sign in to vote

  Hi,

   

  If you are using SQL 2008 just backup the transaction log and it should shrink it,
  If you are using SQL 2005 you can do:
  - backup the transaction log then shrinking the log file
  - use truncate log statement

   

  In addition, you can traction log file with PowerShell.

  http://sharepoint.microsoft.com/Blogs/fromthefield/Lists/Posts/Post.aspx?ID=111

   

  I wish you every success in your important work.

  Best regards,

  David Hu

  • Marked as answer by Peng Lei Thursday, December 16, 2010 8:38 AM

  Friday, December 10, 2010 2:00 AM
• 

  

  0

  Sign in to vote

  Hi David,

              Is it possible sharepoint contentdatabase itself not sql server?

  ---

  tirupal

  Thursday, August 2, 2012 7:29 AM