June 3, 2021 at 10:36 pm
Does cycling error log is needed? We restart our servers monthly for windows patching would that not take care of it?
Another question our database is set to autogrow so does there is a need to setup a job to Alter database and modify file based on the growth?
June 4, 2021 at 9:36 am
Hi,
we start every night a new ERRORLOG. It is very easy so find errors, but I think, it is not necessary.
Autogrowth,
hm, just check your settings, and take care, there are no autogrowth like 10% or something like this.
Autogrowth should fit to your database size. And take care, there is enough space on your drive for some autogrowth events.
good luck,
Andreas
June 4, 2021 at 3:32 pm
It depends. If there's a large volume of data written to your SQL log even when there are no errors, then you should probably switch the logs more often (and, as part of that, increase the number of logs you keep -- the default of 6 is likely too low anyway).
Yes. There should be automated check to make sure that autogrowth is:
(A) never a %, only a fixed amount
(B) is reasonable given the size of the filegroup. For example, typically a 5MB autogrowth is absurdly low on a 1TB file, while 100MB could be absurdly high on a 10MB file.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply