Historically, the OEM and ISV market for database products has largely been focused around transactional environments and the supply of applications for particular horizontal or vertical sectors. As time has gone by, these solutions have been extended to support not just reporting but also conventional business intelligence capabilities. However, there is an increasing requirement in many sectors for non-transactional capability where the focus is on analytic functions that extend beyond the capabilities of standard business intelligence.
It is our belief that in order to support analytic requirements, whether in a pre-packaged analytic application or in a looser platform style environment, there are special considerations that need to be taken into account over and above those traditionally involved with selecting a database to be embedded in a transactional application. In this paper we propose 10 rules for selecting an embedded analytic database.
We will conclude by taking a brief look at one such analytic database provider, Infobright, and discuss how it matches up with our 10 rules.