SQL Server compresses logs and database file size

Source: Internet
Author: User

Please follow these steps. Do not take the following steps if the previous steps are not performed to avoid damage to your database.

Generally, steps 4 and 6 are not recommended. Steps 4 are not secure and may damage the database or cause data loss. If the log reaches the upper limit in step 1, subsequent database processing will fail and the log can be restored after being cleared.

1. Clear logs

Dump transaction database name WITH NO_LOG

2. truncate transaction logs

Backup log database name WITH NO_LOG

3. Shrink database files(If not compressed, the database file will not be reduced)

Enterprise Manager -- Right-click the database you want to compress -- all tasks -- contract database -- contract file

-- Select log file -- select to shrink to XXM in the contraction mode. Here, a minimum number of MB allowed to be shrunk is displayed. Enter this number directly and click OK.

-- Select data file -- select to shrink to XXM in the contraction mode. Here, a minimum number of MB allowed to be shrunk is displayed. Enter this number directly and click OK.

You can also use SQL statements:

-- Shrink Database

Dbcc shrinkdatabase (customer profile)

-- Contract the specified data file. 1 indicates the file number. You can use this statement to query:

select * from sysfiles 
DBCC SHRINKFILE(1)

4. To minimize log files(If SQL 7.0 is used, this step can only be performed in the query analyzer)

A. Separate the database:

Enterprise Manager -- server -- database -- Right-click -- detach Database

B. Delete LOG files in my computer

C. Additional database:

Enterprise Manager -- server -- database -- Right-click -- attach Database

This method generates a new LOG with a size of more than 500 K.

Or use the code:

The following example separates pubs and attaches a file in pubs to the current server.

A. Separation

EXEC sp_detach_db @dbname = 'pubs'

B. Delete log files

C. append:

EXEC sp_attach_single_file_db @dbname = 'pubs', 
@physname = 'c:\Program Files\Microsoft
SQL Server\MSSQL\Data\pubs.mdf'

5. to automatically contract laterMake the following settings:

Enterprise Manager -- server -- Right-click Database -- Property -- option -- select "auto contract"

-- SQL statement setting method:

EXEC sp_dboption 'database name ',
'Autoshrink', 'true'

6. If you want to prevent the log from increasing too much in the future.

Enterprise Manager -- server -- Right-click Database -- properties -- transaction log

-- Limit file growth to xM (x is the maximum data file size you allow)

-- SQL statement settings:

Alter database name modify file (name = logical file name, maxsize = 20)

Related Articles]

  • Memory usage during SQL Server SQL statement execution
  • How to solve the memory usage problem of SQL Server
  • SQL Server database synchronization problems

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.