There is a project using the SQL SERVER2012 version of the database, at first may not notice the log file, so that the log file is getting larger, when the use of sql2008 shrink file method to operate, the problem arises.
DUMP TRANSACTION bigdata with No_logbackup LOG bigdata with no_log
Using the method above does not solve the problem, since 2012 does not support transaction anymore.
Baidu search through a large number of previous solutions, and finally found a solution:
Give the original method source: http://www.itpub.net/thread-1601950-2-1.html
Confirm Log status via select Log_reuse_wait_desc from sys.databases where name= ' DBNAME '
Query to is log_backup, so my solution is
Use [dbname]gobackup log dbname to disk='D:\dbbackup\2014-08-24-2.log' GODBCC shrinkfile (N'a23648263485_log', truncateonly) GO
SQL Server 2012 log files are oversized, clearing the process of logging