The company's SharePoint system uses databases and other applications sharing the same database. In the planning period, due to lack of experience, only considering the size of the content stored in SharePoint, the size of the log of SharePoint database transactions is not considered. Those familiar with SharePoint know that almost all content in the Windows SharePoint Service V2 and SharePoint Portal Server systems are stored in the database, that is, every time the SharePoint site, there will be a number of access to the database, so ShaerPoint The transaction log file for the database is very fast. The data file in our system is only about 10 g, but the log file has reached nearly 30G. When the transaction log of the database is full, many applications cannot be accessed. So how to solve this problem? First, we should consider this problem when planning, so I suggest that you put the SharePoint database and other applications of the database in different partitions, and consider keeping enough space to store the log. Second, it is recommended to make a space separately to store the log. Third, it is to regularly contract the database. You can use the automatic maintenance task, however, sometimes the effect of automatic contraction is not very good. So, I suggest that you regularly contract. The steps are as follows: First modify the fault recovery mode of the database as "simple" mode, then shrink the database, and finally, the standard mode.
