Actually, this:
WHERE P_MS.DateReceived > getdate() - 365
can use an index on DateReceived. The function call is on the right of the conditional and will only be calculated once.
Hmmm... positive? Since 'getdate()' is a non-deterministic function, like all non-deterministic functions, we've always assigned them to a scalar variable to ensure the dbms won't perform a table-scan...although admittedly, these days they seem to be more implementation dependent.
From SQL Server Help...
For example, the function GETDATE() is nondeterministic. SQL Server puts restrictions on various classes of nondeterminism. Therefore, nondeterministic functions should be used carefully. The lack of strict determinism of a function can block valuable performance optimizations. Certain plan reordering steps are skipped to conservatively preserve correctness. Additionally, the number, order, and timing of calls to user-defined functions is implementation-dependent. Do not rely on these invocation semantics.
JFWIW...
Dr. Les Cardwell, DCS-DSS
Enterprise Data Architect
Central Lincoln PUD