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

Very slow for running Query in Standby database? Expand / Collapse
Author
Message
Posted Monday, July 29, 2013 6:39 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 8:55 PM
Points: 1,076, Visits: 3,054
Hi.

Log shipping setup on of the table total Records count 1228976 in standby database, user have read access and using reporting purpose...

Particulare query executing 45 mints, what could be reason in standby database?
So, need to be check primary database for statistices , index rebuild if required?

thanks
ananda
Post #1478554
Posted Monday, July 29, 2013 7:22 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, November 28, 2014 8:09 AM
Points: 316, Visits: 592
The performance of a query on your standby logshipped destination database should be exactly same as the source providing the servers are of an identicle specification.

Have you looked at the execution plan of the users query? Is it possible there query is badly constructed?


MCITP SQL 2005, MCSA SQL 2012
Post #1478577
Posted Tuesday, July 30, 2013 8:05 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 10:17 AM
Points: 14,196, Visits: 28,520
I would not assume they're identical in all respects. You need to identify specifically why the query is running slowly. I'd start with sys.dm_exec_requests. That will show you if the query is blocked by another process. It will also show you what resource the query is currently waiting on if it's simply waiting.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of:
SQL Server Query Performance Tuning
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1479019
Posted Tuesday, July 30, 2013 10:53 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 8:55 PM
Points: 1,076, Visits: 3,054
Thank you for valuable reply..

In this situation, what will happend Logshipping in standby database..

still continuous apply the log or wait that query execution completion then next log will be applied in standby database?
Post #1479279
Posted Thursday, August 1, 2013 8:23 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 10:21 AM
Points: 6,737, Visits: 14,369
ananda.murugesan (7/30/2013)
Thank you for valuable reply..

In this situation, what will happend Logshipping in standby database..

still continuous apply the log or wait that query execution completion then next log will be applied in standby database?

The logs are restored based on the schedule that was implemented during setup, what settings did you use for the t-log restore job?


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1479966
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse