Quantcast
Channel: SharePoint 2010 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 13778

Transaction log blowing out

$
0
0

We have a SP2010 installation which runs our external website. As is commonly the case, it was set up by a consultant who has since left. The database server was underspeced and has always been a problem: it keeps running out of space, and our website falls over. We changed the recovery method to Simple, and this fixed the problem for a while. But then we had another crash, and now the transaction log for our content database is blowing out again. BUT: it is suffixed _1, and the transaction log for the actual database has changed to that of another database. That is, the content database is named XXXX_SharePoint_2010, and the transaction log that is bowing out is named XXXX_SharePoint_2010_1.LDF. But SQL Management Studio shows that the file for XXXX_SharePoint_2010 is WSS_Content_ee856e88d0554e77ba1410809c87e9ad, and its transaction log is shown as WSS_Content_ee856e88d0554e77ba1410809c87e9ad_log.

What is going on? The transaction log is now at 73 GB, and the disk is full. How can I free space to keep our website running, at least until we manage to move the databases onto another server?

Any advice would be gratefully accepted :)))



Viewing all articles
Browse latest Browse all 13778

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>