Hello,
I have a situation with two solutions that I can think of and I'm curious to know if one would be a preferred method. I have a SQL database (sde) that has some feature classes copied over from my ESRI Geodatabase. The database has a very large table containing a list of service orders. The end goal is to have a web map that will symbolize points in the feature classes (added via REST URL) based on the work order status from the table. I have a unique ID that matches features to work orders. Users will not need to use the resulting display to edit anything, all service order editing is done in third-party software.
Option one:
Create a new SQL view that selects a desired subset of attributes from feature class and service order table, sets desired WHERE clause and join the feature class data to the service order data based on the unique ID. Include the view in an ArcPro document, publish to federated server.
Option two:
In Pro document, add the feature class, join the feature class to the table containing the service orders. Set definition query on the feature class, make undesired fields not visible, publish to federated server.
I can provide more specifics if necessary, but I suppose my main question is, from a performance standpoint, are joins superior to views? Vice verse?
