Is there a trick to reverse engineering Oracle Materialized Views? SA treats them as tables but during the import processes they are brought in without any column definitions. As they are treated as tables, there is no visibility to the generating SQL either. Anyone dealt with this before? I'd be interested on feedback on how to handle. Thanks.