Why dont you setup a ESS to have that table inside your relationship graph so you can treat like any other table in your database
I know, right!? ESS was cool while it lasted. We still use ESS for other smaller tables - just not the orders views we were having issues with.
With the uncontrollable caching and FMS crashing, we were forced to not use ESS. Sadly, we had to resort to routine imports bringing the order data into native FM tables.
Good news is that server crashes have apparently ceased. But, I wondered why importing 1 order basically took the same amount of time to import 600 orders. This is when I noticed the redundancy in the calls made to Sql Server.
Just curious if others have used SQL Server Profile to actually watch what FMS sends it.