The problem is that the time it takes to perform queries on the view seems to grow exponentially as the number of rows in TABLE1 grows. I guess this happens because of the way that SAPDB performs the query (i.e. join first to create the view, then perform query), so a huge intermediate table has to be created.
as far as i can imagine, SAPDB uses a sub-query to query results from a view. SAPDB down't support query-rewriting, which might optimize a query on a sub-query to one query. so one shouldn't use to do queries on them - i guess.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
