September 19, 2013 at 12:07 pm
I have configured mirroring in Sql Server.
There is a update statement on my production server which works very fine before mirroring configuration but after mirroring configuration, its work very slow...
Can any one suggest me what i have to do to resolve this problem..
Please help me its very urgent bcz due to this my production server works very slow.
Regards
Dharmendra Kumar
09717765141:hehe:
September 19, 2013 at 3:37 pm
Did you set mirroring to be synchronous or asynchrounous?
Could you post the code for the UPDATE statement?
How many rows does it affect, appoxamitely?
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
September 20, 2013 at 12:37 am
Hi,
I configure mirroring with High Safety with automatic failover mode,
approximately 3 Lac records updated on principal Server,
September 20, 2013 at 1:27 am
With high safety, the statement does not complete until the update has been hardend in the log on the mirror. If you have a slow network connection, or the mirror has poor hardware, this can be painful with that many rows.
But that is still speculation, you need to gain knowledge what is actually taking time. On my web site there is a stored procedure, sp_sqltrace which permits you to run a batch and then compiles trace and wait-stats information about that batch. In this case the wait-stats information is the most important. If you see wait-stats with MIRROR in the name, the problem is as I suggested above.
You find sp_sqltrace on http://www.sommarskog.se/sqlutil/sqltrace.html.
[font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply