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

Accessing reports from secondary server: Expand / Collapse
Author
Message
Posted Saturday, January 19, 2013 4:14 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 8:03 AM
Points: 26, Visits: 483
Hi ,

I have a question related to our environment. We maintain reporting services and users access it anytime . we have sql server 2008r2 standard editions . We experienced slowness in our production environment. So we configured logshipping and accessed reports from secondary server to avoid slowness in production environment. In logshipping , standby mode users can access,but at the time of logshipping restore users will be disconnected or restore doesnt happen.. Can you please suggest me if any other setup can bring out better performance for accessing reports than this?
Post #1409176
Posted Saturday, January 19, 2013 5:50 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, June 12, 2014 2:04 PM
Points: 1,789, Visits: 1,014
Use replication and have the reports connect to the subscriber for a read only copy of the data.

Jayanth Kurup
Post #1409191
Posted Saturday, January 19, 2013 1:00 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 8:03 AM
Points: 26, Visits: 483
Hi Jayanth,

transactional replication is not a good fit for near to real time reporting since you have to pause the replication, then mount the database before it can be queried/reported against, take a snapshot of the replicated data, run the report, then after the report is run dismount the database, and then sync up the transactional data that has been held in a queue by restarting replication. If that is the case, then transactional replication would certainly not meet our reporting needs! Can you let me know for any other ideas ..
Post #1409228
Posted Monday, January 21, 2013 4:54 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, June 12, 2014 2:04 PM
Points: 1,789, Visits: 1,014
Please look here for details on how Transactional replcaition works

http://msdn.microsoft.com/en-in/library/ms151706%28v=sql.105%29.aspx

I think you ahv confused it with snapshot replcaition which needs to occur they first time in order to have a synced copy of the databases to begin with. The agents in transactional replcaition can be scheduled or running continously.


Jayanth Kurup
Post #1409484
Posted Monday, January 21, 2013 5:37 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 8:03 AM
Points: 26, Visits: 483
Thanks a Lot... Is repliation the best possible way.. Nothing else can be done ?
Post #1409509
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse