As many of you know, when you are using stored procedures in TM1 Turbo Integrator to import data and metadata into TM1, you can bring it in from many sources. You can use comma-delimited ASCII files, other TM1 cubes and views, MSAS (Microsoft Analysis Service) and relational database tables that are accessible through an ODBC connection. For this blog, we are going to concentrate on relation database tables through SQL and what you may not know is that using multiple tables and writing multiple joins query in SQL using the Turbo Integrator query box can make the pull of the data very slow!

An easy way to correct this is to write your join statements in SQL using SQL Server Management Studio. Write your joins to create a “summary table” of all the fields you want pulled into TM1. Now create a stored procedure that uses the joins, creates your new table and subsequently updates the summary table based on the schedule you have set.

So, instead of using the long join statement in the Turbo Integrator query box, simply write a statement to execute a stored procedure in the query box. BAM! Your query is much quicker and returns your data as you would expect!

Did you like this blog on Stored Procedures in TM1 Turbo integrator, if so, then check out this blog on how to assign TM1 Element Security Within a Dimension by clicking here.

If you need help setting this up our excellent services is here to help!  Reach out to us at services@lodestarsolutions.com today!  Also, if you have not joined our community, go to lodestarsolutions.com and join now!  Don't miss out on the latest programs, events and educational blog like this one!  It is easy to join and takes less than 1 minute!