December 28, 2010 at 12:53 am
In our Environment We have 5 Database Servers .
In that One Production Server and One report server . Here they are daily taking the the full backup of Production Database and restoring in Report Server . Our Live Production DB is of Size 85 GB . We need to configure it for Log SHipping from Live Server as Primary to Report Server as Secondary . Keeping the Report Server in StandBy mode , as i need to read the records from my Report Server DB . But some of the suggestions in the articles given are
1. Always use read only mode and dnt prefer Stand By mode for log shipping , because the Logs may not get restored when we we are fetching the records from Read - Only database .
The thing i need to know is
1. Is it possible to read records from Report DB by configuring it to log shipping Read only Mode .
2. Will the Performance of the production server get affected , if we configure Log Shipping .
December 28, 2010 at 2:01 am
yes you can configure your production database for reporting purpose using log shipping.
for this you need to restore the database in standby mode so that you can read the database simultaneously.
Performance of your production database will not be impacted much as on live you will be taking log backup and restoring it on your destination. The only affected area in this is how big your logs are growing and time taking in copying the file to destination. If you look for these figures you will come to know how much your live server is being affcted by log shipping.
----------
Ashish
December 28, 2010 at 3:41 am
personal for reporting situations where if teh object of the source database dont often change i like to use transactional replication
this prevents the logrestore/reporting user issue from happening
and afaik log shipping is more designed for a standby/failover situation
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply