SQL Server 2012 log files are oversized, clearing the process of logging

Source: Internet
Author: User

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

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.