Hello, We have a few layers where the model requires joining a few database tables together. For some we define the join in GeoServer using SQL view, but for others we pre-join the tables together as part of ETL to produce the final desired table.
1. My assumption is that pre-joining the tables and create a layer on top of the output table will yield better performance than defining the join in GeoServer SQL view. Is this correct? 2. If so, how much performance gains are we talking about? I am trying to see if it's worth simplifying preprocessing tasks at the cost of some performance because if there is a change in data model I have to rerun the entire preprocessing job which can be time consuming where as if I defined the SQL view in GeoServer I can easily change it on the fly. Thanks, Danny
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
