sql shrink database

When operating on a database, the program prompts that the data log is too large; open the Directory Check of the data file storage, it is found that the LDF file has reached more than 2 GB. The cleanup method is shown on the Internet. I tried it to achieve the desired effect. After completion, the LDF file is less than MB. Back up data before performing the operation...My operations are inQuery AnalyzerThe operation is completed as follows:1. dump tr

--Shrink SQL log --exec p_compdb ' test ' Create proc P_compdb @dbname sysname--The name of the database to compress @bkdatabase bit=1, because the database may be corrupted in the steps of separating the logs, so you can choose whether to automatically database @bkfname n

sys.database_files; GODBCC shrinkfile (1, truncateonly);D. Emptying the fileThe following example shows the steps to empty a file to remove it from the database. For this example, you first create a data file and assume that the file contains data.CopyUse ADVENTUREWORKS2008R2; go--Create A data file and assume it contains data. ALTER DATABASE adventureworks2008r2 ADD FILE ( NAME = test1data, FILENAME

Step 1: Query Analyzer: Dump transaction datebasename with no_log Part 2: Enterprise Manager: Right-click the database you want to compress -- all tasks -- contract database -- contract file -- Select log file -- select to contract to xxm in the contract mode, here we will provide a minimum number of M that can be reduced. Enter this number directly and click OK. If you do not want it to become larger lat

Tags: partially truncated recover technical log management cat sql2005 It's nbspSQL2008 's Shrink logBecause SQL2008 is optimized for file and log management, the following statements can be run in SQL2005 but have been canceled in SQL2008:(SQL2005)Backuplog Dnname with No_logGoDumptransaction Dnname with No_logGoUse DnnameDBCC Shrinkfile (2)Go--------------------------------------------------------------(SQL2008):Clearing the log in SQL2008 must be d

If the log file in the SQL database is too large, you can try the following code to narrow down the log file to the desired size. Copy the code to the query analyzer, modify the three parameters (Database Name, log file name, and target log file size), and run the command. Set nocount onDeclare @ logicalfilename sysname,@ Maxminutes int,@ Newsize int Use mydb --

A few days ago also encountered a large log file problem, the actual size of the database is 600M, the actual size of the log file is 33M, but the log files occupy a space of 2.8G!!! Try a variety of ways, Shirnk DATABASE, TRUNCATE LOG file, there is no way to reduce the file. Anyway, this should be a bug in SQL Server. Then find the following code, you can red

There are two steps:Step 1. Truncate the log content in the database The code is as follows:Copy code Backup log database name WITH TRUNCATE_ONLY Step 2 force the database to compress its size The code is as follows:Copy code Dbcc shrinkdatabase (database name, TRUNCATEONLY) These two steps need to be execute

Today in the development environment encountered a problem, we found that the hard disk space on the server is full, look at the next found that this disk storage database file should be the source of a not very large Coucay pair. After the inspection, it was found that a data file under this database accounted for 70% of the space under the drive letter, and most of the data came from a table. But even if

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, this should be done periodically to avoid the database log too large. 1, set the database