February 10, 2013 at 10:51 am
Please some one help me .....
:-)What are best practices for setting transaction log size for tempdb?
February 10, 2013 at 2:35 pm
Rum a load test of your app, see how large TempDB gets. Set default size to slightly larger.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 10, 2013 at 5:58 pm
rajeshjaiswalraj (2/10/2013)
Please some one help me .....:-)What are best practices for setting transaction log size for tempdb?
I wouldn't call it a "best practice" but here's what I do...
I set it to 100MB with 100MB Growth and then I watch it. Whatever it get's to after a full monthly cycle has passed is probably a pretty accurate size. I'll add half a GB to that and use that for the Initial Size keeping the 100MB growth. Of course, the new intial size won't kick in until the next bounce of the service or reboot of the server. I typically will do the same with the MDF file.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2013 at 6:39 pm
GilaMonster (2/10/2013)
Rum a load test of your app, see how large TempDB gets. Set default size to slightly larger.
Same thing I do. Other option is to run it for a while and monitor. Then adjust your settings.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply