August 22, 2014 at 12:40 pm
Hi,
i have a production sql server, and i have a production report server. I need to ensure that the report server is fairly up to date during the day from the production sql server. What is the best way to achieve this? It can be a slight lag, as in a couple of hours or so, but it needs to be fairly updated.
Thank you,
Jen
August 22, 2014 at 4:11 pm
Replication is one option. Replication is a bit of a bear to maintain though. You could also look to log shipping, although that has some shortcomings too.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 2, 2014 at 12:56 pm
i am using logshipping for this, but is there a way to minimize the downtime for when its restoring? Right now, the restore to the report server takes about 2 minutes, and it runs every 15 minutes, which means the users are getting errors when using the reports.
October 7, 2014 at 4:31 am
A two minute restore for logs is kind of long unless you just have tons of transactions. There's no really effective ways to speed up restores. I have an article [/url]on some things that can be done, but I suspect none will help here. Another option to explore would be moving to 2014 (skip 2012 at this point) and looking at the Availability Groups and their read only databases that are maintained asynchronously. I'm just not a fan of replication. Maintenance of it is almost a full-time job.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 8, 2014 at 3:27 pm
Another option is mirroring with rolling snapshots.
Still that has its own set of issues and admin challenges.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply