临时数据库结构。是对还是不对? [英] Temp DB structure. Is it right or not?
问题描述
大家好,
Hi guys,
我有一个实例,在我移动了一些数据库之后给了我一些问题。我认为这与新数据库在实例中带来的进程有关,特别是在Temp Db中。现在我检查了一下,临时数据库在两个文件中被分割为
,这很好,但我觉得映射是好的,因为它现在是:
I have an instance which is giving me some problem after I moved some databases on it. I think that this is related with the processes that the new databases brought in the instance and in particular in the Temp Db. Now I checked and the Temp db is split in two file, this is good but I don't feel that the mapping is good as it is at the moment:
逻辑  ;  类型     文件组 初始尺寸自动增长
Logical Type Filegroup initial Size Autogrowth
tempdev ROWS ... PRIMARY 253          256 MB,无限
tempdev ROWS... PRIMARY 253 By 256 MB, Unlimited
tempdev2 ROWS ... PRIMARY 253          256 MB,无限
tempdev2 ROWS... PRIMARY 253 By 256 MB, Unlimited
templog   LOG      不是Appl。 147        256 MB,无限制
templog LOG Not Appl. 147 By 256 MB, Unlimited
您如何看待?可以吗?
谢谢
推荐答案
为什么你会相信这些问题由于额外的工作量,特别与tempdb相关而不是其他资源使用?
Why do you believe the problems are particularly related to tempdb instead of other resource usage due to the additional workload?
如果有必要,您可以添加额外的tempdb文件以减轻tempdb latch争用。有关详细信息,请参阅 https://www.brentozar.com/archive/2014/05/tell-need-tempdb-files/。
You could add additional tempdb files to alleviate tempdb latch contention if warranted. See https://www.brentozar.com/archive/2014/05/tell-need-tempdb-files/ for details.
这篇关于临时数据库结构。是对还是不对?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!