SQL的完整备份 [英] Full backup of SQL
问题描述
我的办公室里有一个 辩论作为我们的主要数据库日志获取 迅速增加。
辩论如下
I have a debate in my office as our main DB log getting rapidly increase.
the debate as following
we are taking a full backup for the SQL DB daily. and we think that after this full backup transaction log should be shrinking. as we did full backup. but still after full back up the size of the transaction
log still the same.
the vendor is asking us to do a manual shrinking for the DB everyday. asn we belive we dot need this as we are taking this full backup daily.
can someone answer this for me.is full backup for SQL should reduce the log size for that DB, or not? 这篇关于SQL的完整备份的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
我们每天都在为SQL DB进行完整备份。我们认为在此完整备份之后,事务日志应该在缩小。我们做了 完整 备份。但仍然在完全备份后,交易的大小仍然是相同的.b / b> b / p>
供应商是要求我们为DB进行手动收缩 每天。 asn 我们 belive 我们需要这个,因为我们每天都在进行这个完整备份。
有人可以为我解答这个问题。完全备份对于SQL应该减少该数据库的日志大小吗?完全备份只备份数据库,它不会像收缩那样做任何事情日志文件或数据文件。要收缩数据或日志文件,您需要运行dbcc shrinkfile命令
Full backup only backups up the database it does not do anything like shrinking or log file or data file. To shrink data or log file you need to run dbcc shrinkfile command