We have data in two different databases (both in sql) that we need to join and publish to Portal. I believe that currently, ESRI does not support a relationship class where the feature layer is in one database and the table is in a different one. We are trying to avoid using a linked database in sql so I was wondering if anyone else has had this problem and what they did for a workaround.
Thanks!
Just out of curiosity, why are you trying to avoid a linked database? This provides a live connection so you won't need to have some type of update script if you had to pull data from database to another.