This content has been marked as final. Show 4 replies
If you are adding conditions then it is probably cleaner to write that into the SQL or perform transformations on the database side before loading to essbase, as I am sure many will say essbase and load rules are not really an ETL tools.
as I am sure many will say essbase and load rules are not really an ETL tools.
Glenn is going to counter with a "I know how to do this in three steps using create column as text, join, and a oft-overlooked but awesome command that everyone but Tom Tortolani (I think I have the spelling on that right -- he was the Arbor employee that wrote Load Rules) forgot.
I 100% agree with John -- why not do it in SQL?
Edited by: CL on Jan 23, 2013 6:33 AM
Misspelt Tom's name
Thanks for your reply. Doing it in SQL is what we thought, but wanted to know if this can be done in Essbase. We have decided to do it in SQL and get the measures into one table and then rule files will take over from there.
As per my limited knowledge, the same cannot be done in essbase.