The SQL Server transaction log is full and the 'primary'

The SQL Server transaction log is full and the 'primary'

1. This problem occurs because the log file reaches the limit of a single file. There are two ways to solve this problem.

1. log deletion: The solution is as follows:Dump TransactionDatabase NameWithNo_log executes this SQL statement

You can also contract the log file of the database: Right-click the database node and click[Task (t)] -> [Shrinkage (s)] -> [File (f)] After all, this is not a long-term solution.

2. Add data files

Solution: You can also add new data files to the primary group to solve this problem.
Alter database name Add file (name = logical file name, filename = 'C: \ filename. ndf'

Or select database> Properties> file to add a new file.

The first method is recommended because the SQL server log is too large, so it should be cleared frequently and save space.

This is the solution

SQL Server transaction log full and 'Primary'