The transaction log for SharePoint 2010 database xxx is full

Http://www.cnblogs.com/sygwin/p/6222428.html

Received leadership arrangements, said the customer has a problem to ask for assistance to resolve, the other side to show me the error log, as follows:

The transaction log for database ' Wss_content_xxxx ' is full. To find out why you cannot reuse space in the log, see Log_reuse_wait_dec column in Sy.databases

The result is that users can no longer upload files to the document library.

It seems that the corresponding database file, log file large and amazing, has more than 1.8T

As an old driver, the theoretical solution to this problem is to shrink the database. But we are a theory more than the practice of the old driver, although we have a magic formula, but also dare not too careless,

After all, it is someone else's product environment, the direct contraction of trade rashly, in case of problems this consequence I can not afford ~

For security reasons, it is recommended that customers back up the database first, but do not let the backup, because the log is full.

All right, let's get my brother hard. Execute the following SQL command:
Use wss_content_xxxx;

GO

--Set the database to the simple recovery model,

ALTER DATABASE wss_content_xxxx

SET RECOVERY Simple;

GO

--Compressed to 100M

DBCC shrinkfile (wss_content_xxxx _log, 100);

GO

--Recovery

ALTER DATABASE wss_content_xxxx

SET RECOVERY full;

GO

Log file dropped to 100M, after a preliminary test, SharePoint everything works! The whole world is quiet ~

(A lot of people may ask, what's the point of solving a problem and being quiet in the world?) I want to say, probably you have not experienced the product problem, the mail, the telephone, even QQ constantly has the customer feedback thing.

The transaction log for SharePoint 2010 database xxx is full