<< I went back and tried to replicate this, and you are correct, but *only* if
you turn *off* the RequestSensitive property for the query.

Why is this ?  Because in such a case you're not reading the rows from the
source table during navigation, you're reading them from the result set of
the query, of which *most* of the rows remain buffered in memory and, as
such, don't need to be written to, or read from, the disk.  Therefore, they
don't need to be encrypted/decrypted at all.

So, you can achieve parity by making sure that the result set sensitivity is
equivalent in both cases. >>

Thanks Tim, I really appreciate all of your help with this, and for the detailed explanations.

= Steve