MSSQL$<instance >:Memory Manager\Target Server Memory (KB): This indicates the idealsize for the buffer pool. Total and Target should be almost the same on a server with nomemory pressure that has been running for a while. If Total is significantly less than Target,then it’s likely that SQL Server cannot grow the buffer pool due to memory pressure, inwhich case you can investigate further

So it's the other way.i.e

If you have Total Server Memory (KB) and Target Server Memory (KB) are always same ---> NO memory pressure

If you have Total Server Memory (KB) less than the Target Server Memory (KB)---> Memory pressure

I appreciate your inputs and eliminate the confusion by clarifying which one is correct and why

Total is what SQL currently has. Target is what it thinks it wants under the current load. So if total is lower than target, either SQL is still building up the memory allocation, or it needs more than it has (ie it's under memory pressure)

MSSQL$<instance >:Memory Manager\Target Server Memory (KB): This indicates the idealsize for the buffer pool. Total and Target should be almost the same on a server with nomemory pressure that has been running for a while. If Total is significantly less than Target,then it’s likely that SQL Server cannot grow the buffer pool due to memory pressure, inwhich case you can investigate further

If Total > Target it means that SQL is trimming its working set due to a request from the OS. It can signify that the OS is under memory pressure, but not SQL.

Total > Target means that SQL is reducing its memory usage. It's not going to reduce its memory usage if it is under memory pressure. In fact, it won't reduce its memory usage unless either the OS tells it to or the max server memory setting is changed.