sql database cleanup

Tags: style blog http using io strong file dataEvery time the database log to see the explosion of some big head, so random search a way to get rid of the log, the next big head, and search for half a day, so or write a blog, do not look for a mess.1. Set the database to Simple modeSelect the database you want to shrink, right-click Properties---options, select S

Tags: des blog http SP file Data 2014 issue log Scene: When we imported the Mr Data, we found that the disk space was not enough, the result is that our program is likely to throw an exception, we need to import data when the log to thin the body.Q 1: When importing data, does weight loss result in database exceptions? The DBA provides a solution: Answer question 1:No problem. Does not create a conflict. But make room for t

the system send broadcast, hard disk space is not enough, the system recycles the cache. Implementation method: Send a message to the operating system, I want to apply for a very large space. The cache is recycled.Implementation Step ①: Add a New button② find this control, click on the time to apply for a very large spacePackagemanager>>freestorageandnotify ( application space, observer interface );To request a free space, the observer returns the maximum amount of space to be requested (how mu

operation is to adjust the memory configuration size. Manual operation Method: 1. Open SQL Server Management (Enterprise Manager); 2. Open the Properties panel for the instance of SQL Server; 3. Locate the memory settings and change the maximum server memory usage. Use script action: [sql] --Force free memory create procedure [dbo]. Clearmemory as www.2cto.co

In the use of the process, we often encounter a very large database log, here are two ways to deal with ... Method One In general, the contraction of the SQL database does not greatly reduce the size of the database, its primary role is to shrink the log size, you should do this periodically to avoid the

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, Re

MySQL database cleanup MyISAMInnodb tables (MySQL 5.1.6 or later versions are supported) a large number of MyISAMlog tables in the data center need to be cleaned regularly, which is set to every weekend, about 10 Gb, 5 MySQL database cleanup MyISAM Innodb tables (MySQL 5.1.6 or later versions are supported) a large nu

650) this.width=650; "title=" DHCP database cleanup lease Grace Period.png "alt=" Wkiol1o9wu3qkh1gaakuazugoie442.jpg "src=" Http://s3.51cto.com/wyfs02/M01/3B/56/wKioL1O9Wu3QKh1gAAKuAzUGOiE442.jpg "/>650) this.width=650; "title=" DHCP database cleanup lease Grace Period_.png "alt=" Wkiol1o9wwxi1srnaakkgwvjbyu592.jpg "

XXM, here will give a allow to shrink to the minimum m number, directly enter this number, you can determine --Select the data file--in the contraction way to choose to shrink to XXM, here will give a allow to shrink to the minimum m number, directly enter this number, OK You can also use SQL statements to complete --Shrinking the database DBCC shrinkdatabase (library name) --Shrink the specified data

When I restored the database from the database backup, I found that there were more than 120 GB of log files, but I couldn't use SQL Management. I used the DBCC statement to clear it! Space released! And speed! First of all, we need to check the type of the backup data. This is very important, but it cannot be cleared. Select name, recovery_model_desc from sys.

[Recommended] (SqlServer) Batch cleanup all data in the specified database to establish a personal brand through knowledge sharing. In practical applications, when we want to hand over a project to the customer, we need to clear all the previous test data of all tables in the database to give the customer a clean database