I have just migrated my production SQL Server to a new box and found that the memory usage for sqlservice in Task Manager seemed to be giving a very awkward figure: 118KB which is impossible as the usage before the migration was 1,800,234Kb.
I did some checking by capturing the perfmon counters: Total and Target Memory in SQL Server and both counters returning the max server memory value (4GB) which I had allocated for SQL Server.
I worried that this might be indicating that there's something wrong with the memory allocation but having hard time finding the root cause of it.
I wouldn't get too 'bent out of shape" about the values reported by Task Manager. The memory configuration looks Ok to me.
Keep in mind that there are two radically different kinds of memory usage supported and reported by Windows. 32 bit tasks can have AWE or conventional memory allocated to them. Conventional memory is allocated in the 32 bit tasks address space, which can be 2 Gb in normal configuraitons, and can be set to 3 Gb in special cases (which you've already done). This memory is "visible" to Windows Task Manager. AWE memory can be allocated anywhere that Windows has usable memory, without any regard for the 2 or 3 Gb limit. This is the only way that a 32 bit task can address more than 3 Gb of RAM, but AWE lies completely ouside the scope of WIndows Task Manager.
i see.. thanks for pointing this out one question though, I did a check on Perfmon's SQL counters: Target Memory vsTotal Memory and found that both the memory value are almost the same (4GB)..does this means that the server has memory bottleneck? Because the Max memory that i allocate for this server is 5GB.