Hi,
I'm trying to get an understanding of SCCM 2012 R2 because we're going to use it at our enterprise. Having no more then about 1000 clients, we're going to implement a PS on one server. We're not sure if we're going to install SQL locally or remote, both
options are still open, though I'm aware that the local option is advised most of the time. I've been reading several topics on these fora and elsewhere and yesterday I've had a talk with our SQL dba about several requirements and options. He saw I wanted
to use autogrowth but didn't think it was a good idea. So I started to search the internet. Well, I think I must tell him he is right. Most of the documents are very clear about this : stay away from the autogrowth option and configure an initial disk size.
These are the blogs and topics I think are interesting. There are more, of course.
(sorry, no links until when I'm verified.....)
Most are very against autogrowth:
==> "consider pre-sizing files to utilize the entire disk on which the TempDB is saved, and turn off the autogrowth option. "
and
==> "Never,
I mean never, let the TempDB grow to its steady state size through auto-grow. You should only use auto-grow as a last resort but not as a strategy."
Even Microsoft warns about autogrowth, though it is enabled by default.
But some do take it seriously and use it :
==> "Database: 150GB Site DB .mdf 50% initial size with 1 % AutoGrowth and 90% Max Size. 75GB Site DB .ldf 50% intial size with 2% Autogrowth and 90% Max Size"
So, if I mix everything together I have to take - as an example - a disk sized 80GB and create 8 tempdb files each having 10TB as a fixed size. Right? Or not?
Enlighten me please. :-)
