October 30, 2014 at 8:45 am
Hi
I am getting WriteLog waits on a simple updates. Is there a way to get Commits to process faster? I'm new at this so any insight is welcome.
Thanks
Kathy
This is an example of a 'simple' update
UPDATE xyz
SET actualHours = (@RecActual + @actualHours)
WHERE ( dept = @dept AND
extractDateTime = @extractDateTime)
October 30, 2014 at 1:34 pm
If it's waiting on the log, you need to look to contention within your I/O system. Can you separate your log and data onto different disks and disk controllers? Can you put the log on a faster disk?
You could also be seeing other performance issues around the query. Anything with a WHERE clause needs good indexes and statistics to ensure it selects the data in an efficient fashion.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 4, 2014 at 5:29 am
Thanks Grant
I added indexes and I was able to bring cpu down. I have more tuning to do. I am ready through your book 'SQL Server Execution Plans'. Your book is giving me a good foundation. I have a lot to learn.
Thanks again
Kathy
November 4, 2014 at 6:05 am
Glad to hear it's proving useful. Let me know if you have questions.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply