November 1, 2015 at 11:28 am
Hello .
I have a prod server running SQL 2012 Standard which host our DB which is about 50 GB . We have enabled logshipping on a secondary sever which is in another region . Now we need to implement reporting solution for which we need to have another copy of DB . I can't implement transactional replication since it works only for tables with primary keys . Merge replication is also out of question.DB mirroring is also out of question.i do not want the logshipped DB to be used for reporting.
Could you please tell me the best strategy to implement the reporting on secondary server ?
Thanks in advance.
November 1, 2015 at 3:51 pm
rohan1424 (11/1/2015)
Hello .I have a prod server running SQL 2012 Standard which host our DB which is about 50 GB . We have enabled logshipping on a secondary sever which is in another region . Now we need to implement reporting solution for which we need to have another copy of DB . I can't implement transactional replication since it works only for tables with primary keys . Merge replication is also out of question.DB mirroring is also out of question.i do not want the logshipped DB to be used for reporting.
Could you please tell me the best strategy to implement the reporting on secondary server ?
Thanks in advance.
Quick question, can you outline the requirements for the reporting instance, i.e. sync latency etc.?
:w00t:
November 1, 2015 at 7:37 pm
Duplicate post. Please see the following original post to post your answers so we can keep them all together.
http://www.sqlservercentral.com/Forums/Topic1732694-2799-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply