Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

High Log flush time??? Expand / Collapse
Author
Message
Posted Thursday, May 21, 2009 6:26 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 13, 2010 10:33 AM
Points: 282, Visits: 757
Hi,
We are using Spot light for Monitoring SQL Server 2005 and we are getting the below error frequently.
What this error referencing to? What is the corrective action to get rid of this? Is this a serious issue? We are getting this for all most all databases
Time Connection Action Details Severity Alarm
05/20/2009 4:01:32 PM ABC Alarm raised the database Search_DB has a high Log Flush Wait time (515 ms). Low Databases - Log Flush Wait Time Alarm.
Post #721776
Posted Sunday, May 24, 2009 2:47 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, August 24, 2012 8:11 AM
Points: 1,097, Visits: 2,157
klnsuddu (5/21/2009)
Hi,
We are using Spot light for Monitoring SQL Server 2005 and we are getting the below error frequently.
What this error referencing to? What is the corrective action to get rid of this? Is this a serious issue? We are getting this for all most all databases
Time Connection Action Details Severity Alarm
05/20/2009 4:01:32 PM ABC Alarm raised the database Search_DB has a high Log Flush Wait time (515 ms). Low Databases - Log Flush Wait Time Alarm.


This means SQL server cannot write the log files onto the disk in a timely manner. Do you have DB mirroring set up by any chance to this database?

What is your physical disk layout and also could I ask you what is the frequency of your tlog backups?

Post #722694
Posted Sunday, May 24, 2009 1:05 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Sunday, March 02, 2014 4:34 PM
Points: 724, Visits: 1,001
Is it share point by any chance and they are rebuilding indexes this could take for ages.....
Post #722763
Posted Thursday, May 28, 2009 11:15 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 13, 2010 10:33 AM
Points: 282, Visits: 757
Yes, these are share point databases and we have log backups twice a day. It is in pre-production, later we will change the log backup schedule to every 1 hour.

This error is because of not having frequent log backups?
Post #725270
Posted Thursday, May 28, 2009 9:03 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Sunday, March 02, 2014 4:34 PM
Points: 724, Visits: 1,001
No shouldn't be because of lack of backups...1 hours is good..or could do 15 minutes if they are very big logs to keep them down a bit when backing them up. Ask the sharepoint guys if they are doing search indexes and if they are on MOSS which i think is the latest version of sharepoint.
Also ask them if they are doing rebuilds on the app side or setting up new search indexs on the apps.

Thread i found looks interesting.
http://sqlcat.com/technicalnotes/archive/2008/12/09/diagnosing-transaction-log-performance-issues-and-limits-of-the-log-manager.aspx
Post #725578
Posted Friday, June 05, 2009 5:14 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 13, 2010 10:33 AM
Points: 282, Visits: 757
Hi,

We have share point databases in sql server 2005 EE x64 and we do NOT have mirroing setup.

and No Index rebuilds and Integrity checks happening. But Still we are frequently getting the high Log flush wait itme alarms? is this a critical to databases?

how to rectify the cause of this alarm?
Post #730102
Posted Saturday, June 06, 2009 9:14 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Sunday, March 02, 2014 4:34 PM
Points: 724, Visits: 1,001
Put on profiler and capture what is running at this time.
Post #730261
Posted Monday, November 19, 2012 4:33 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, April 17, 2014 3:16 AM
Points: 21, Visits: 1,034
I know this thread is old (very old but it may help someone else)
But with a high log flush I would look at the autogrowth settings. SQL 2008 has sensable growth defaults but SQL 2000 and 2005 use 10% growth settings.
Post #1386293
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse