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

Log ship to local db for ETL source data Expand / Collapse
Author
Message
Posted Friday, June 7, 2013 10:02 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, September 5, 2014 11:55 AM
Points: 46, Visits: 152
I'm using log shipping to maintain a failover copy of my main db on a secondary server. I'd like to put our Analysis Services on the secondary. If we have to failover to the secondary then Analysis Services would be turned off until we got things back in normal operation.

It occurs to me that, during normal operation, I could run the nightly ETL jobs against the copy of the db on the secondary, putting everything local on that machine. It should improve performance, reduce execution time and relieve load on the primary instance, yes?

Am I missing something? Any comments on this idea?
Post #1461148
Posted Monday, June 10, 2013 6:22 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, January 28, 2014 8:15 AM
Points: 3,068, Visits: 4,639
rray 44280 (6/7/2013)
I'm using log shipping to maintain a failover copy of my main db on a secondary server. I'd like to put our Analysis Services on the secondary. If we have to failover to the secondary then Analysis Services would be turned off until we got things back in normal operation.

It occurs to me that, during normal operation, I could run the nightly ETL jobs against the copy of the db on the secondary, putting everything local on that machine. It should improve performance, reduce execution time and relieve load on the primary instance, yes?


Assesment is correct, sourcing from secondary is not going to have any impact on primary.

Having said that...
1- Make sure business is comfortable and on agreement with the idea of not having Analysis Services up in case of a DR situation.
2- Make sure there is a way to source all the "missed" ETL cycles once DR situation gets back to normal.


_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #1461507
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse