Page 1 of 1

how to use TM1 solution?

Posted: Fri Dec 17, 2010 1:05 am
by Sean
Recellently, I will work on a TM1 project, we have identified that the data source is from relational database(operational database), the datasource is very messy. My question is that do we need to create a data warehouse(Data mart) as a data source for TM1 or TI is powerful enough to do the ETL work?

Re: how to use TM1 solution?

Posted: Fri Dec 17, 2010 1:36 am
by Alan Kirk
Sean wrote:Recellently, I will work on a TM1 project, we have identified that the data source is from relational database(operational database), the datasource is very messy. My question is that do we need to create a data warehouse(Data mart) as a data source for TM1 or TI is powerful enough to do the ETL work?
TI is, by definition, an ETL tool.

That having been said, I do recommend that you try to "unmess" the data source first and get as much done on the server side as possible to reduce your load times. I'd be looking at creating views, and using the views (as opposed to direct queries against the tables) as the data source via ODBC. If the relational database is really badly designed (meaning long query times), and you don't need real time interfaces, you may want to even look at doing an export from it to text files, and loading the files.

Cleaning up the database would of course be the optimal solution, but I'm assuming that that isn't an option.

Re: how to use TM1 solution?

Posted: Fri Dec 17, 2010 1:48 am
by Sean
Alan Kirk wrote:
Sean wrote:Recellently, I will work on a TM1 project, we have identified that the data source is from relational database(operational database), the datasource is very messy. My question is that do we need to create a data warehouse(Data mart) as a data source for TM1 or TI is powerful enough to do the ETL work?
TI is, by definition, an ETL tool.

That having been said, I do recommend that you try to "unmess" the data source first and get as much done on the server side as possible to reduce your load times. I'd be looking at creating views, and using the views (as opposed to direct queries against the tables) as the data source via ODBC. If the relational database is really badly designed (meaning long query times), and you don't need real time interfaces, you may want to even look at doing an export from it to text files, and loading the files.

Cleaning up the database would of course be the optimal solution, but I'm assuming that that isn't an option.

Many thanks for your suggestion, it is really helpful.