Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ferrethouse
Constraint Violating Yak Guru
352 Posts |
 Posted - 2013-04-26 : 11:57:39
|
| I didn't realize that standard edition had a 64 gig memory limit. I expanded to 96 gigs and allocated 90 gigs to SQL Server. It seemed to gobble it all up (in process explorer). Does it appear to use all 90 gigs but actually only use 64 gigs? Or does it actually use 90 and I'm just violating the license agreement?thanks. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2013-04-26 : 23:19:07
|
| How are you determining that it is all being used? It should limit you to 64GB AFAIK.-Chad |
 |
|
|
ferrethouse
Constraint Violating Yak Guru
352 Posts |
Posted - 2013-04-27 : 10:20:38
|
quote:
Originally posted by chadmat
How are you determining that it is all being used? It should limit you to 64GB AFAIK.-Chad
Task manager was showing that the sql server process was using over 64 gigs (90). So I don't know if it was actually "using" it or just grabbing onto it. |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2013-04-27 : 15:53:57
|
| Interesting. Check Total and Target server memory in perfmon, and you might use some of the memory DMVs to see what are the actual sizes of the various memory pools.-Chad |
|
|
|
ferrethouse
Constraint Violating Yak Guru
352 Posts |
Posted - 2013-05-08 : 18:40:09
|
| It does in fact appear to be a hard limit. While SQL Server will grab as much memory as you allow it to (we set a 100 gig max) it appears to only actually use 64 gigs.At least according to this query...select sum(pages_kb)+ sum(virtual_memory_committed_kb) from sys.dm_os_memory_clerksWhich does not appear to go above 64 gigs and change. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-05-08 : 23:12:24
|
| It is a hard limit |
|
|
|
|
|
|
Is standard edition memory limit a hard limit?