When deploying Sharepoint, pay attention to the transaction log files of SQL Server.

The databases used by the company's SharePoint system share the same database with other applications. During the planning period, due to lack of experience, only the size of the content stored in SharePoint was taken into account, and the log size of SharePoint database transactions was not taken into account at all. Anyone familiar with SharePoint knows that almost all the content in Windows SharePoint service V2 and SharePoint Portal Server systems is stored in the database. That is to say, every time a Sharepoint site is accessed, therefore, the transaction log file of the shaerpoint database grows very fast. The data file in our system is about 10 Gb, but the log file is nearly 30 GB. When the transaction logs of the database are full, many applications ProgramAnd cannot be accessed.
So how can we solve this problem?
First of all, we need to consider this issue during planning. Therefore, we recommend that you store SharePoint databases and other application databases in different partitions and reserve enough space to store logs.
Second, we recommend that you create a separate space to store logs.
Third, it is necessary to regularly shrink the database. You can use automatic maintenance tasks, but sometimes the effect of automatic contraction is not very good. So, I suggest you perform regular manual contraction. The procedure is as follows:
First, change the fault recovery mode of the database to "simple", then contract the database, and then return to the standard mode.