This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 57.99999999999999%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPB%3C/text%3E%3C/svg%3E)
Hello all,
we are having performance issues on clusterd instance. For example DB restore time increase from 50minutes to like 2h with the same DB size (1,3TB). SQL server version is Microsoft SQL Server 2012 - 11.0.5532.0 (X64) Enterprise Edition
On this cluster is running 13 SQL server instances.
But the main one lets call it DB01 has these issues.
For this instance there is set max memory limit of 96GB which all is used.
There is like 9 UserDBs in total 1,4TB.
What is strange to me is that even there is running lot of transactions currently 340 processes when checking sp_who2. TEMPDB is almost not used, it has unlimited growth on dedicated disc with more then 200GB space but TEMPDB usage looks like this>
How it is possible it is not using TEMPDB at all, like I know it should be good sign that things can be sorted in memory probably, but it is on max limit and perfromace dropped and it is strange TEMP is not used at all.
Is there any parameter to check specifically?
Running fullscan stats update for each DB and TEMPDB is still on same values - almost not used.
Is it possible that for some reason SQL is trying to not use TEMPDB but working just with buffer which is then overloaded? When querying waittype I got this >
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Peter Babic
We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.
It is very difficult to answer questions like this with only a scant amount of information.
But if the restore time has increased, this sounds more like an issue with the I/O subsystem. And RESTORE does not use tempdb a whole lot, if at all.
I guess the reason that your tempdb is not very heavily used is because your workload does not use that much temp tables and that.