Updated: AX 2012 - Run Reports without hitting the Production DB
I hope everyone is enjoying their weekend. I did want to post that I plated my recent post about how to setup a reporting database, that would enable the execution of AX 2012 reports, without hitting the production database. AX 2012 - Run Reports without hitting the Production DB
To sum up, here is the update:
" a reader of this post pointed out that this would not work for the setup using log shipping. Using log shipping is for HA, and he is 100% correct. The log shipped db will remain in standby mode and therefore the .net bc would fail in connecting to it. So instead of using log shipping replace that concept either with replication, or mirroring. The other points that people have brought up, including the same reader, is the cost for the license for the SQL server as well as the extra AOS needed. This is true, however if the desire is to offload the processing of reporting resources from the production, transactional db, then the cost of the extra license would have to be used in order to weight the value in which such a setup could bring. With this, still it is possible to have a reporting database that is different than the production transactional db."
It's still a valid possible solution, but with any such solution, of course there is a cost weight associated with it. Thanks to everyone who shared with me their thoughts on this. The concept was meant to be something that was refined and could give the community a possible solution for enabling such a need.
That's all for now, check back soon as more to come. Till next time!