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 |
|
dbthj
Posting Yak Master
143 Posts |
 Posted - 2009-07-29 : 16:44:12
|
| SQL 2000 enterprise, sp4. AWE enabled with 32gig ram on box.Application with big non-parameterized queries blew outMemtoleave. (error WARNING: Failed to reserve contiguous memory of Size= 65536.) I opened case with Microsoft Premier support and they recommended using -g startup parameter of -g384. That worked for several months.Now the problem is back. They said if the problem came back, to increase -g.Questions:1. How big can I make it? How about doubling it? 2. Does AWE have an impact?3. What bad things happen if you make -g too big? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2009-08-10 : 17:08:43
|
| the -g value directly reduces memory avaiable to other parts of sql. connection buffers, querey memory and all manner of things that cannot use the AWE memory. Currently my server is set to -g400 the issue occurs very infrequently for me, and not at all if I install service packs monthly (probably because of a restart of the server) |
 |
|
|
|
|
|
-g startup parameter Max setting?