Guys,
User apparently can only execute one stored proc. from a Crystal Reports. There are lots of different types of queries and he would like to cut-down on the number of Crystal Reports he would need. He wishes to create a table with session i.d. as primary key that will be used to insert aggregate records (rolling averages, etc.) so that he doesn't have to do this. I am concerned about even just 12 concurrent users (maybe?), 67 rows, primary key and index inserts and deletes are unnecessarily incurring I/O. I am suggesting using DBMS_SQL but don't know if there are limitations to the type of SQL you can write - we have inline views/hints/etc.? I just think it would be a more efficient way to do the same thing. He is saying he has been burned before by code generators. I am trying to say that this is a supplied package and not really a code generator and in my experience quite flexible. Help!!!! Am I making too much of this? What about metadata tables? In otherwords, keep report name, columns involved or even store query and view name then query actually based on the metadata. Probably what the ad hoc query tools do anyway.
