很多獨(dú)立服務(wù)器客戶反饋數(shù)據(jù)庫日志文件過大，嚴(yán)重浪費(fèi)磁盤資源，數(shù)據(jù)庫實(shí)際大小為600M, 日志文件實(shí)際大小為33M, 但MSSQL日志文件占用空間為2.8G!!!
我們及時(shí)反饋給我們的研發(fā)部門，他們寫了一個(gè)腳本，就可以將日志文件縮小到自己想要的大小了。把代碼COPY到查詢分析器里，，然后修改其中的3個(gè)參數(shù)(紅色字體部分)，運(yùn)行即可(測試通過，請獨(dú)立服務(wù)器客戶測試)
-----
SET NOCOUNT ON
DECLARE @LogicalFileName sysname,
@MaxMinutes INT,
@NewSize INT
USE data_db -- 要操作的數(shù)據(jù)庫名
SELECT @LogicalFileName = 'data_db_log', -- 日志文件名
@MaxMinutes = 10, -- Limit on time allowed to wrap log.
@NewSize = 100 -- 你想設(shè)定的日志文件的大小(M)
-- Setup / initialize
DECLARE @OriginalSize int
SELECT @OriginalSize = size
FROM sysfiles
WHERE name = @LogicalFileName
SELECT 'Original Size of ' + db_name() + ' LOG is ' +
CONVERT(VARCHAR(30),@OriginalSize) + ' 8K pages or ' +
CONVERT(VARCHAR(30),(@OriginalSize*8/1024)) + 'MB'
FROM sysfiles
WHERE name = @LogicalFileName
CREATE TABLE DummyTrans
(DummyColumn char (8000) not null)
DECLARE @Counter INT,
@StartTime DATETIME,
@TruncLog VARCHAR(255)
SELECT @StartTime = GETDATE(),
@TruncLog = 'BACKUP LOG ' + db_name() + ' WITH TRUNCATE_ONLY'
DBCC SHRINKFILE (@LogicalFileName, @NewSize)
EXEC (@TruncLog)
-- Wrap the log if necessary.
WHILE @MaxMinutes > DATEDIFF (mi, @StartTime, GETDATE()) -- time has not expired
AND @OriginalSize = (SELECT size FROM sysfiles WHERE name = @LogicalFileName)
AND (@OriginalSize * 8 /1024) > @NewSize
BEGIN -- Outer loop.
SELECT @Counter = 0
WHILE ((@Counter < @OriginalSize / 16) AND (@Counter < 50000))
BEGIN -- update
INSERT DummyTrans valueS ('Fill Log')
DELETE DummyTrans
SELECT @Counter = @Counter + 1
END
EXEC (@TruncLog)
END
SELECT 'Final Size of ' + db_name() + ' LOG is ' +
CONVERT(VARCHAR(30),size) + ' 8K pages or ' +
CONVERT(VARCHAR(30),(size*8/1024)) + 'MB'
FROM sysfiles
WHERE name = @LogicalFileName
DROP TABLE DummyTrans
SET NOCOUNT OFF
以上代碼用T-SQL語言實(shí)現(xiàn)。
- 關(guān)于MYSQL日志文件詳細(xì)介紹請查看： “mysql日志文件詳細(xì)介紹以及如何修改MSSQL數(shù)據(jù)庫日志文件位置 ”一文 http://m.dnkh.cn/faq/zhuji/mysql-log.html
