August 28, 2014 at 5:40 am
Hi,
We are using 208r2. We used to generate simple reports against to prod. The production is running slow. Just we need the production fresh copy all the time. We are using mainly one database. So I need to have read only copy of that particular database which is sync with the production.
I think logsipping, Replication is not good idea. I need like always on replica but I don't want to migrate
What is the good solution?
Thanks,
August 28, 2014 at 6:26 am
Replication if you need real-time. Log shipping the DB will be be behind prod. The less often the log backups are restored, the more behind it can get. The more often they are restored, the more disruptive it is to the users as they have to be disconnected when the restore runs.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 28, 2014 at 8:35 am
Another issue with log-shipping is that if you have the secondary database in standby mode so that it's readable, every time a log file is restored, any users will be disconnected, so that could be quite irritating if you're trying to use it for reporting.
August 30, 2014 at 7:44 pm
How in synch do you need it? Log shipping will be a pain with the users disconnecting, so I'd look at replication as suggested by Gail.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply