If you create indexes on proxy tables, you may experience performance degradation; you cannot run create index, because Adaptive Server cannot propogate the command to the remote view. However, if you map the proxy table to a user table, Adaptive Server can optimize the query plan by creating indexes on the proxy tables’ join column.
If the number of rows returned by the view varies drastically from one execution to another, performance degrades when you gather statistics on proxy tables.
If you are using proxy tables or views, Sybase makes these recommendations:
Do not run update statistics on proxy tables defined on views.
If you ran update statistics on a proxy table defined on a view, increase performance by dropping, then re-creating the proxy table. You cannot use delete statistics to remove the current statistics, because systabstats retains the original row count.
Convert the view to a permanent table.
Try using the command line trace flag 318 (force reformatting).
