Thanks GilaMonster and Jonathan.

The update, at the end of the MSDN blog, explains exactly the behaviour I am experiencing. Thank you for the link.

I am still a little mystified as to what, exactly, the memory utilization % means; with gigabytes of free memory, why does MSSQL think it is using a high percentage?

In the example log entry:

Duration: 28853 seconds. Working set (KB): 76176, committed (KB): 170992, memory utilization: 44%.

If I understand correctly: the SQL Process has committed memory of 167MB and a working set of 74MB; thus 44% is used; the process only requires 74MB of 167MB allocated, which seems absolutely fine.

So why is a "significant part of sql server process memory" paged out? Especially when there are gigabytes of free memory waiting to help?

I do understand that, without a load on the system, the memory figures here are slightly artificial. I will start to migrate databases over the next few days, and will carefully monitor what happens to the memory allocations.

Andy