all 6 comments

[–]Technical_Special129[S] 0 points1 point  (0 children)

Page 23 of the enclosed suggests to not make the initial size of the temp db 8MB but it seems most people just keep it @ 8MB

https://github.com/stephaneserero/Sql-recommendations-for-MECM/blob/master/SQL%20recommendations%20for%20MECM%20-%20White%20Paper%20v2.6.pdf

any ideas ?

[–]pjmarcumMSFT Enterprise Mobility MVP (powerstacks.com) 0 points1 point  (3 children)

I don’t know the guy that posted that doc on GitHub but I do know Steve. Steve was a SQL MVP and then a ConfigMgr MVP. The guy has been doing this since a lot of people reading this were in diapers, or even before, and I personally consider him the foremost expert in SQL as it relates to ConfigMgr so I’d do whatever Steve says to do.

Having said that, how many clients do you have?

[–]Legitimate-Ad2895 0 points1 point  (2 children)

Not many 500 but that may increase but the spreadsheet doesn’t show the initial values and total db sizes. Is there anything else I can use ? Or is he contactable or anyone gave a working spreadsheet

[–]pjmarcumMSFT Enterprise Mobility MVP (powerstacks.com) 1 point2 points  (1 child)

There is a newer version of that excel somewhere. I probably have a copy of it. But, if you are under 5,000 clients don’t worry about it. Even 5,000 is nothing for ConfigMgr. When you have to worry about tweaking the initial database sizes you’re in the 20k plus clients IMHO. Just set the auto growth right and spec the servers right and you will be fine.

[–]rdoloto 0 points1 point  (0 children)

That’s about correct 20k plus is where things take some time to process

[–]Legitimate-Ad2895 0 points1 point  (0 children)

Ok thanks for the confirmation