I have polygon Feature Classes joined to their attributes in a SQL Server Express database table. This way I don't have to keep a copy of the data in my Feature Class, and the data changes are reflected in my maps as soon as our DBA makes updates to the DB. This is also handy for data that's constantly updating. I've been doing this for a long time but whenever I share a joined Feature Class as a service I get the High Severity Code 10014 message saying that this type of join will slow performance. I've also noticed other limitations with this method like being unable to have Feature-Linked Annotation based on the joined fields, not being able to edit the joined fields, or being able to filter with a Web App because of the join.
Is there a better way to create live links between Feature Classes and SQL Tables and Views or do I just have to live with the performance hit and limitations?
BTW my ArcSDE Geodatabase is in the same SQL Server instance as the tables I'm joining to.
Thanks,
-Jon
