InfoCaptor is not a replacement for ETL tool but complimentary to Data-warehousing tools and products as you can quickly create prototypes of dashboards once your facts and dimension are ready. Just for comparison, DBI for instance requires the source tables and views to be in certain format, you have additional overhead of creating objects within DBI so this prolongs the development cycle. I believe same is the case with Siebel dashboards, as it requires additional layers to be built before final presentation.

Thanks
Nilesh

I’m writing this without having tried InfoCaptor, but I’ll make one more observation that seems safe: Your assumption seems to be that the data required for your dashboard can be extracted from your various sources with a relatively small number of SQL queries that are easy to compose and performant given the structure of the underlying data sources… In fairness, the Infocaptor home page does say ‘It is the right solution when: You just need to create dashboards using simple SQL queries…’ but this may well not be true, once you get past trivial examples, or you may need to make changes in the underlying databases or other data sources to synthesize information at the database level, where the performance will be better.

I’m sure there are cases where InfoCaptor can solve straightforward problems with less effort than some of the alternatives, but each user must look realistically at the complexities of their situation.