tag:blogger.com,1999:blog-4889748320010274206.post1269308305208095100..comments2024-03-29T02:03:40.652-04:00Comments on AX WONDERS: AX 2012 - Run Reports without hitting the Production DBAxWondershttp://www.blogger.com/profile/01901411966215366187noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-4889748320010274206.post-30433274065121568222012-02-02T01:43:26.086-05:002012-02-02T01:43:26.086-05:00There are many ways to accomplish the task either ...There are many ways to accomplish the task either using Log shipping,mirroring,transactional replication.I think it needs to be tested before come to conclusion.For example transactional replication we need all the tables to have primary key ,without this it is impossible to achieve.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-57122214172725383462012-02-02T01:27:59.358-05:002012-02-02T01:27:59.358-05:00If you just need a reporting database, consider tr...If you just need a reporting database, consider transactional replication.<br /><br />Mirroring is a DR solution or Log shipping , not intended for creation of a reporting DB. Snapshots on mirroring are kinda a way to make a failover server useful until it's needed for failover. <br /><br />Regards,<br />Xavier FernandesAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-13733034591043981162012-01-07T08:14:44.920-05:002012-01-07T08:14:44.920-05:00Jagjeet,
This is an interesting approach to consi...Jagjeet,<br /><br />This is an interesting approach to consider. Thanks for the feedback.AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-24570221636465111352012-01-06T20:08:57.036-05:002012-01-06T20:08:57.036-05:00Hi,
I see a problem here, if you enable log shipp...Hi,<br /><br />I see a problem here, if you enable log shipping the 2nd database will marked as read only database and for getting the reports executed you need to have BC setup for which you need another instance of AOS. <br /><br />You cannot start AOS unless you have the database in non restricted mode because when you start AOS it inserts records in the tables.<br /><br /><br /><br />The other option you can do is by using 3 databases <br />1. your production database <br />2. your log shipping database <br />3. restored copy of your log shipping database which is not restricted.<br /><br /><br /><br />Now connect your 2nd AOS instance to your 3rd database and point your SSRS to the 3rd database.Jagjeet Singhhttps://www.blogger.com/profile/07689543771745714891noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-39562159209472413512012-01-06T08:57:40.790-05:002012-01-06T08:57:40.790-05:00Hi Steve,
There is no really a problem when you ...Hi Steve, <br /><br />There is no really a problem when you do this. What the post is trying to say is that you have a choice (although not tested a 100%) to run the reports from a DB other than the production one. This is helpful when you have limited memory resources regarding processing power.<br /><br />I guess the only real drawback is licensing, but if you have the licenses and a low processing power, this option can be useful to divert processing from the Prod DB to an SSRS DB that will replicate some data. <br /><br />I hope this is clear ... ;)AxWondershttps://www.blogger.com/profile/01901411966215366187noreply@blogger.comtag:blogger.com,1999:blog-4889748320010274206.post-81102831575989784892012-01-06T08:46:06.295-05:002012-01-06T08:46:06.295-05:00Hi.
I fail to see the problem with running reports...Hi.<br />I fail to see the problem with running reports off your production/live system. Can you shed some insight as to what the problem is?Stevenoreply@blogger.com