June 16, 2016 at 2:39 pm
Hello friends. I've moved to a new job recently. The prior DBA left in a hurry, and so I am working to account for all of the processes that are in place. Many alerts are set up on various SQL Servers, and I understand most of them, but one that I can't quite wrap my head around is the log flushes per second. There is an alert set up to notify us when log flushes per second exceed a certain amount, and that amount is different per database.
My question is two-fold: 1) how do I know how many log flushes per second is too much, and 2) why do I care about log flushes per second at all?
Thanks,
Clint
June 17, 2016 at 10:42 am
I'd be more concerned with log waits and/or dynamic log growth than with log flushes per second. If you're writing a lot of data, you will have a lot of log flushes, it's unavoidable.
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".
June 18, 2016 at 10:34 am
I agree with Scott. Don't worry about this.
June 27, 2016 at 12:12 pm
Thanks guys. Much appreciated.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply