The description of
EntireTable cache on
msdn seems ambiguous. On the one hand,
all the records in the table are placed in the cache after the first select. On the other hand,
the SELECT statement WHERE clause must include equality tests on all fields of the unique index. Let's run several tests to analyse it.
Problem description
Analyse how
EntireTable cache works by tracing T-SQL statements and using
wasCached
method.
Hints
Run select statements with and without where clause on server and client.