hi i have a complicated set of tables and data in sql which i want to model for reporting and for use to build cubes. Just wondering if i should do all modeling in cognos or should i have this developed in sql first and then build evertyhthing i need in coognos after. I have a database person who is really good at sql programming inform me it would be better and easier for everyone if all inportant and complex modeling be as to how i want all reporting and cube info built in sql and then use frameowkr manager to refine and finallize.
any ideas or suggestions woujld be greatly appreciated
bunker
I am pretty sure that fixing things in a database will lead to the most efficient solution in terms of performance. The trade-off is that you need to maintain that part as well. The alternative is to use Cognos SQL objects which will give you the choice in terms of Cognos,native and passthrough definitions. A native SQL object will work very much the same as a database view , but it will be database-specific. A Cognos SQL object will be more limited in scope, but will offer portability to other RDBMS.
Fixing things within the database WILL prompt you to have good documentation drawn up from the SQL developer, whereas keeping everything within the framework more or less makes the framework the source of documentation..