February 17, 2009 at 1:26 am
The initial size of our tempdb is set to 12GB and it locates in a drive in which the free space is about 200MB. in some cases, the tempdb becomes full and the SQLserver stops running. I've moved tempdb to a new location and am gathering information from developers to define tempdb size properly. I'd like to know if its safe and legal to resize initial size of tempdb besides, does it help if I bind tempdb to its own cache, which is separate from data cache?
Any idea is appreciated
February 17, 2009 at 6:55 am
Yes it is safe and legal set the initial size of tempdb. It is actually recommended as growth is expensive.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 17, 2009 at 6:59 am
ok good 🙂
February 18, 2009 at 3:18 am
You cannot have a dedicated buffer pool for tempdb. All databases share the same buffer pool.
In a large system there would be performance benefits to be gained if you could dedicate a buffer pool to tempdb. For a system with a 200MB tempdb it is unlikely that using multiple buffer pools (if they were available) would give a measureable performance benefit. There is a request on Connect to provide this feature.
The previous reply saying you need to alter the size of tempdb to meet the requirements of your workload is right. It is important to do this.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply