Which F# query constructs ensure server-side pagination in EF Core?

Bounding Large Datasets with Query Expressions

When working with large datasets in F# using Entity Framework Core (version 6.0+), the standard approach to pagination involves utilizing Skip and Take clauses within query expressions to bound the result set.

While these constructs typically map to SQL OFFSET and FETCH clauses, there is uncertainty regarding how different LINQ providers handle these calls when the underlying data source has specific constraints or when using older provider versions. If a provider fails to translate these methods, the query may default to client-side evaluation, loading the entire dataset into memory before slicing.

What is the most reliable way to verify that Skip and Take are being translated to server-side SQL rather than executing in-memory? Does F# provide a mechanism to force server-side evaluation for pagination to prevent potential out-of-memory errors?