Comments for Data RuminationsThis engineer has worked with the Oracle DBMS since 1998, and is obsessed with data integrity. Join him as he applies these concepts and technologies to provide improved business processes and value.Comment by naga07 on Cognos Reporting Tuning, an example- May 19, 2008 it's really nice code !!Click here to go to this entry !!http://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/data-ruminations... Comment by ganotedp on Data Has A Long Tail- May 5, 2008 We just (re)demonstrated how poorly "future use" fields work in practice. After I stomped on adding more to our reporting databases, I was asked "but what about the 6 existing 'future use fields' that came with the ERP (our source system)" Time for a quick review. We traced the "pre-built" future-use columns, and found some had been given defined uses (before we "went live" with the system). Those fields got data moved and transformed into appropriately named columns on the reportinhttp://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/data-ruminations... Comment by Mau_Leyzaola on Cognos Reporting Tuning, an example- May 4, 2008 Good solution and I agree with you in that Cognos sometimes creates really annoiying SQL by itself.Shouldn't it be better to create Materialized Views instead of regular Views In such case I think you could schedule to refresh right after your DWH is uploaded and transformed.Well, this is just an idea who knows if it would work for your business.Thanks for posting anyway. !!http://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/data-ruminations... |