none
ldf file too big RRS feed

  • Question

  • running sharepoint connected to a 2008 sql server.  All DBs are on the sql server.  however i have a file C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\SharePoint_Config_3e0700f0-6c84-40aa-b533-a83eb26ff68f_log.LDF thats on the sharepoint server.

    Its 6.5 GB and eating up valuable disk space.   I thought that by putting the sharepoint DBs on a sperate sql server that i wouldn't have to deal with these types of issues.  How do i shrink this ldf file?  And why is it local and not over on the SQL server with the rest of the DBs and associated files?

    • Moved by Mike Walsh FIN Wednesday, May 12, 2010 4:11 PM admin q (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))
    Wednesday, May 12, 2010 3:02 PM

Answers

All replies

  • I would use SQL Server Management Studio to determine which database that LOG file belongs to.  It will probably be the SharePoint_Config database.  I'm not sure why the .LDF file is local to your SharePoint server though.  All I can think is that the SharePoint server was a single server solution in the past and the files were moved to the SQL Server, but not removed from the SharePoint Server.

    Check the last update time stamp on the .LDF file.  If it is currently being updated actively, you'll notice that and it would mean that SharePoint is NOT using the SQL Server, but is using a local instance of SQL Server on the SharePoint Server.

    Another sure fire way to determine if that's the case is to STOP the SQL Server services on the SharePoint Server.  If SharePoint is using the local server rather than the remote SQL Server, stopping the services will "break" SharePoint.  (NOT RECOMMENDED IN PRODUCTION WITHOUT SCHEDULING AN OUTAGE!!!)

    Once you've determined if the .LDF file is in use, you can determine what to do about it.

     


    I trust that answers your question...

    Thanks
    C

    http://www.cjvandyk.com/blog
    Wednesday, May 12, 2010 4:24 PM
    Answerer
  • Thanks...

    Here's the thing - the sharepoint install was setup from the beginning to run off a seperate SQL server.  Even stranger is that there is no SQL server or services running on the sharepoint server.  If i go to services.msc - there is no sql service or agent or any sql related service listed.  So i can't connect to the sharepoint server with sql studio as there does not appear to be any type of sql instance or service running on this sharepoint server.

    However in the local C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\  also exists:

    tempdb.mdf
    templog.ldf
    model.mdf
    modellog.ldf
    msdbdata.mdf
    msdblog.ldf
    master.mdf
    mastlog.ldf
    sharepoint_admincontent_xxxxx.mdf
    sharepoint_admincontent_xxxx.LDF
    Sharepoint_config_xxxx.mdf
    wss_search_vm-sharepoint.mdf
    wss_search_vm-sharepoitn_log.ldf
    sharepoitn_config_xxxx_log.ldf  (this is the large one - 6.5GB that needs to be shrunk)

     

     Also - this is Sharepoint Services 3.0 -  not Sharepoint Server

    Wednesday, May 12, 2010 6:26 PM
  • Hi,

    Set your DB to Simple Recovery Model and not in Full Recovery Model. Check the below link for suggestions on the same:

    http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/413ca1fc-2914-4ee9-801d-f7b6c17df409

    Also, check these helpful material on shrinking your LDF file:

    http://technet.microsoft.com/en-us/library/ee721075(office.12).aspx
    http://boris.gomiunik.net/2008/10/sharepoint-config-database-log-file-too-big-reduce-it/

    Hope this helps!!


    BR, PM
    • Marked as answer by utilweb Thursday, December 22, 2011 5:11 PM
    Wednesday, July 28, 2010 1:40 AM