January 19, 2013 at 4:14 am
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?
January 19, 2013 at 5:50 am
January 19, 2013 at 1:00 pm
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 ..
January 21, 2013 at 4:54 am
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.
January 21, 2013 at 5:37 am
Thanks a Lot... Is repliation the best possible way.. Nothing else can be done ?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply