Follow the steps to avoid damaging your database if you do not follow the previous steps.
Generally do not recommend to do 4th, 62 steps, 4th step unsafe, it is possible to damage the database or loss of data. 6th step if the log reaches the upper limit, subsequent database processing will fail, and the log will not be restored until it is cleaned.
1. Empty log
1, determine the SQL database installation path and the SQL database name used.
such as: e:\Program Files\Microsoft SQL Server\mssql\data\j200.mdf '
2, the database J200 renamed to other names, such as J2008, what names can.
3. Use the system you use to recreate a new "J200" database.
4, click Start-Program--microsoft SQL
First of allUse [database name];exec sp_helpfile;
Use the sp_helpfile query to know the logical name of the log file, and then you can use DBCC to reduce the log fileBACKUP LOG [database name] WITH TRUNCATE_ONLYDBCC SHRINKFILE (logical name of log
Label:The company has to standardize the size of the personnel library every month.The following is a SQL Server with the size of the SQL repository:SELECT db_name(database_id) as [Database Name], [Name] as [Logical Name], ((Size* 8)/ 1024x768) as [Size (MB)],--the original unit of size is bit, so multiply 8 to byte and multiply by 1024 to MByte. [Differential_base_time] as [differential Base ti
always closed), normal after the big file can be deleted.Of course, the best way is to plan in advance, set up, add a job schedule, so that will automatically back up, shrinkage and the like, control in a certain size range.After learning, the other simple processing methods:1: Empty the LogDUMP TRANSACTION Library name with NO_LOG2: Shrink LogEnterprise Manager--Right click on the database you want to shrink--all tasks--shrink the database--Shrink t
Original: SQL Server bulk log file processingOptimized processing for SqlServer2000, SqlServer2005, SqlServer2008, SqlServer2012, and SqlServer2014 library log files, reducing disk space.Processing method:The following columns are SqlServer2012: Recovery mode: Complete-Simple, then click OK Right-click the database,
When you restore a database from a database backup, you find that the log file actually has more than 120 g, not through the SQL management, resolute use DBCC statement cleanup success! Free space! and clear and speed!
First of all, it's important to look at the type of backup data, or not to clean up
Select Name, Recovery_model_desc from sys.databases
After e
A valid method is to execute the following script: (Bigdata is the database name) use database name; go alter database database name set RECOVERY Simple; -- Set the simple recovery model go DBCC Shrinkfile (database name _log, 1 go alter database database name set RECOVERY full ; -- revert to original mode go Back up the database first before executing. Reference: http://www.cnblogs.com/downmoon/archive/2009/12/13/1623004.html[Go] How to clear the large
With the Lognet component, you can view the site log later without having to go to the server to downloadLog component: LogNet.DLL, reference can be usedWrite Method:1, LogNet.Log.WriteLog (" log title " " log content ");2, LogNet.Log.WriteLog (" log title ",new Exception ());Log
Tags: SQL Server 2014 log shipping13.2.4 Deploying log shipping with Management StudioUse SQL Server Management Studio to deploy the log shipping steps as follows:(1) Open the Properties page for the primary database DB01 as log s
$ Master_ssl_verify_server_cert:noPanax NotoginsengLast_io_errno:1236
-Last_io_error:got Fatal Error1236 fromMaster when reading data fromBinary log:'Could not find first log file name in binary log index file'
theLast_sql_errno:0
+ Last_sql_error: A Replicate_ignore_se
preceding log file.Access. after running log on the WEB server for a long time, it may reach dozens or hundreds of megabytes. If an error occurs during Apache running, the error occurs. the log size will also increase to dozens of megabytes. It is very memory-consuming for the system to read and write a large text
Reset slave clears all slave Database Replication information.General application scenarios: for example, switching to different masters, master-slave Redo, etc;1. Run the command on the slave. You must stop the slave before execution.2. after reset slave is executed, all replication-related information, including master.info, relay-log.info, and unconditional deletion of all relay logs are cleared ). note that it is unconditional, that is, it does not manage whether your slave
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.