Hi,

> 2. Page is read/write beacause of big sort operation

>> Sort IO is directed into separate temporary files and it is nor cached by the engine, nor paged.
>> Unfortunately, engine doesn't collect Sort statistics.

Will be good to see this on trace output and accumulated stats on mon$tables

>>You could try to use OS utlities to look at performance stats at the file level, btw

this is not accurate

> 3. Page is read/write from temp object bigger then memory buffer e.g big global temporary table, others?

>> GTT's data go thru the common page cache as all other database operations.

What happen when GTT will be bigger then whole mem cache? It will go to disk?
If yes, how to catch such situation?

Is there some other situation where some “buffer” go to disk?

P.S. Should i create ticket with feature request about collection of this stats?

regards,
Karol Bieniaszewski

---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
https://www.avast.com/antivirus


[Non-text portions of this message have been removed]