|
方法一
一般情况下,sql数据库的收缩并不能很大程度上减小数据库大小,其主要作用是收缩日志大小,应当定期进行此操作以免数据库日志过大 1、设置数据库模式为简单模式:打开sql企业管理器,在控制台根目录中依次点开microsoft sql server-->sql server组-->双击打开你的服务器-->双击打开数据库目录-->选择你的数据库名称(如论坛数据库forum)-->然后点击右键选择属性-->选择选项-->在故障还原的模式中选择“简单”,然后按确定保存 2、在当前数据库上点右键,看所有任务中的收缩数据库,一般里面的默认设置不用调整,直接点确定 3、收缩数据库完成后,建议将您的数据库属性重新设置为标准模式,操作方法同第一点,因为日志在一些异常情况下往往是恢复数据库的重要依据
方法二
set nocount on declare @logicalfilename sysname, @maxminutes int, @newsize int
use tablename -- 要操作的数据库名 select @logicalfilename = "tablename_log", -- 日志文件名 @maxminutes = 10, -- limit on time allowed to wrap log. @newsize = 1 -- 你想设定的日志文件的大小(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
|