Thin line between legacy reports and DWH/BI reporting
One case showed significant issue about where to deploy and use reports. Dillema was to place all the reports into Data Warehouse or to leave part of them in legacy system and to export more complicated once to DWH/BI. Actually, there was no dillema at all for user (department). Department and director wanted to transfer all the reports into DWH/BI and to leave loyalty system without any reporting.
This might sound like a good decision on local level.
On company level, problem should be seen differently.
Natural environment in meaning of data and processes should be always used to produce simple reports for every day work.If the reports are standrd for system, generated reports will be quick, will not choke system prime role and that is gathering and processing information.
On the other hand DWH/BI should be allways used for:
- more resource demanding reports in sense of techniqual demnds on platform resources, that results with poor reporting performance (long time to generate report),
- inadequate reproting API, visualization,
- or if mixture with other data from other sources is necessary, higher level of data processing.