Any WHERE conditions in particular.  Typically StartTime is (almost) always compared against log-type tables.  And/or the data is summarized by StartTime periods (day, week, etc.).  If so, cluster the table...

CASE WHEN ALTotalUnits / TotalProfiledHours >= 3 THEN <higher than 3 weeks>
CASE WHEN ALTotalUnits / TotalProfiledHours < 3 THEN <lower than 3 weeks>

Alter the schema on those tables/views to 'dbo', then you should be able to view them just fine.

If it doesn't allow that, you'd have to script them out,...

Yeah, STUFF is good stuff!

Another thing to note is that you need to STUFF from right to left.  Otherwise the stuffed chars throw off the byte locations.

If you're literally using "*" in the view, refreshing the view is often needed too.  Not sure if that works for remote tables, but presumably it would (or SQL would...

Cluster the table by the most common search.  Most searches aren't totally random each time.  If this one really is, use an int (or bigint) key, not a char(20) one...

It doesn't look like you're passing a date, you're passing an id instead, which will get interpreted as a date but it won't be the date you expect or want.

You should seriously consider specifying "ON DELETE SET NULL" in the FK relationship and let SQL do this for you rather than writing it yourself.