October 29, 2015 at 9:02 am
This is the scenarion in my environment
WaitType Wait_Sec Resource_Sec Signal_Sec Wait Count Wait Percentage
WRITELOG920039.89887485.89 32554.00 23446032975.02
October 29, 2015 at 9:43 am
Gerald Britton, Pluralsight courses
October 30, 2015 at 5:16 am
ensure your logs are sized appropriately and make sure they're segregated to fast disks would be a start
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 30, 2015 at 6:54 am
Log file is used in sequentially . Unless first log is completely filled .Tranactions wont go to another log which is in other disk. so ho come it brings the write log count down. Please clariffy
October 30, 2015 at 7:04 am
Segregated from database files, not from other log files in the same database.
John
October 30, 2015 at 7:07 am
In my environment .mdf files are in one drive and .ldf files are in another drive. we had tranactional replication in the instance where i am getting the performance issue.
October 30, 2015 at 7:12 am
m.rajesh.uk (10/30/2015)
Log file is used in sequentially . Unless first log is completely filled .Tranactions wont go to another log which is in other disk. so ho come it brings the write log count down. Please clariffy
not sure what you're referring to?
Keep the number of transaction log VLFs to a minimum by appropriately sizing your transaction logs and separate the logs onto separate fast disks
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 30, 2015 at 7:24 am
m.rajesh.uk (10/30/2015)
we had tranactional replication in the instance where i am getting the performance issue.
I suppose if your Log Reader Agent is reading from the logs then access is no longer sequential and so you'd expect more WRITELOG waits. You might try reducing the frequency at which the Agent runs.
John
October 30, 2015 at 7:26 am
Are the WRITELOG waits occurring throughout the day during normal operation of application or intermittedly during something like a batch load /delete or re-index?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
October 30, 2015 at 8:22 am
WRITE Log is occurring through out the normal operation of application.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply