the setting control of the tempDB data file and log file size
Posted on 2013-12-10
as we have vendor to support our MS SQL 2008 R2 and sometime they do something funny that, for example, increase the initial size of hte tempdB log to 2/3 of the disk that holds the tempdb log.
But when the log growth, we can't shrink it to the level smaller than that size.
we will then recieve that the tempeDB log full message and the application stop to work too.
anyway to restrict thyis kind of person, who also has the dba related login to the MS SQL, to change the tempdb data file and log size?