March 6, 2017 at 6:13 am
I have as practice if database 900GB allocate 10% para Log , 20% for TempDB and 30% for growth. I would like to receive opinions about this.
March 6, 2017 at 7:13 am
I'm not sure I understand the question. The database is 900GB... what is a para Log? And what do you mean by 20% for TempDB?
TempDB gets created at a certain size and grows out of necessity as SQL Server requires it to. You shouldn't be messing with the size of TempDB unless something has gone completely FUBAR on your server and probably not even then.
As for 30% for growth... You mean you want it to grow 30% each time it grows and leave it as unlimited growth? Well, that depends on several factors. First, how big is your drive? Second, how much space do your transactions consume each time they run? How long does a 10% space increase last before it grows again compared to how long a 20% space increase? Have you considered increasing by specific MB or GB instead of by percentage points? Have you considered that it might be the log that needs more growth than the database file? They probably won't have the same growth requirements...
March 6, 2017 at 7:55 am
Jose Ianuck - Monday, March 6, 2017 6:13 AMI have as practice if database 900GB allocate 10% para Log , 20% for TempDB and 30% for growth. I would like to receive opinions about this.
I vaguely remember seeing some sizing suggestions like this back with maybe SQL Server 7.0 - remember the 10% for log. None of that is really applicable anymore, not sure it made sense back then either.
There are a lot of things to consider as Brandie has suggested so you'd want to look at how this is being used - especially that the log and data files likely won't grow at the same rate and tempdb is really an it depends.I don't know if anyone can really recommend initial sizing for your database system.
Sue
March 6, 2017 at 8:08 am
There's no good way to size the log and tempdb for a database. The amount required isn't based on the data size, but rather the workload. How much activity can determine space needs.
Lots of concurrent query activity can require more tempdb space due to worktables, spills, sorts, etc.
Lots of data changes requires more log space.
More frequent log backups mean less log space.
You can guess, and then adjust accordingly.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply