log truncation occurs at
1. backup log statement,
2.every time a checkpoint is processed,if the database in truncate mode,
checkpoint can generated whenever the number of log becomes 70% full,
so it is no probleum,
but truncate mode when both these conditions are true.
1. database option is set to true (trunc.log on chkpt)
2.a backup log statement referencing the database is executed
谢谢各位的回答,我还想确认一下,如果我把日志文件分配固定的空间,如10M,而且我设置了trunc log on chkpt 选项,是不是还需要定期执行backup log databasename with no_log and truncate_only?系统不会自动截断日志日志吗?
可以告诉大家,我以前没想到日志文件如此厉害,结果数据文件才500M,日志文件已经
达到4G,结果造成数据再不能存储(d:4G多),这种情况下使用backup log databasename with no_log and truncate_only,日志文件还能变小吗?
使用命令 dump transaction databasename with no_log and truncate_only 可以删除日志文件。
如果是SQL Server 7.0 可以使用 backup log databasename with no_log and truncate_only