locked
crm reporting database options? RRS feed

  • Question

  • Hello, what has your experience been with cRM reporting?  Specifically, many applications use the concept of a reporting database.  For example, a nightly job might be run to copy all data from the OLTP database to a reporting database. The reporting database would have a known delay of 24 hours.  This type of pattern helps prevent locking in the primary database from overuse and runaway queries.  Have you implemented something like this in CRM?  Is there a standard approach for implementing this pattern in CRM?

    Tuesday, January 7, 2014 7:23 PM

All replies

  • Hi,

    The pattern would typically be the following. The diagram goes one step further in explaining deployment scenario with global and multiple CRM instances but the idea is the same. You would still need to move data out of CRM with SSIS, use SSAS for historical/dimensional data.


    Ronald

    Tuesday, January 7, 2014 7:58 PM
  • Thanks Ronald - that's a great diagram!  Did you find the diagram at a particular url?  Or did you create this diagram yourself?
    Wednesday, January 8, 2014 2:41 AM