MemToLeave in SS2KEE with AWE

How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how to
see it by using win perfmon?
thanks
lzhu@.dba1.com
Hi
Please visit at http://www.sql-server-performance.com/awe_memory.asp
"lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
to
> see it by using win perfmon?
> thanks
> lzhu@.dba1.com
|||Actually I believe the default is 256MB.
Andrew J. Kelly SQL MVP
"lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
> to
> see it by using win perfmon?
> thanks
> lzhu@.dba1.com
|||256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
using AWE.
"Andrew J. Kelly" wrote:

> Actually I believe the default is 256MB.
> --
> Andrew J. Kelly SQL MVP
>
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>
>
|||I've been there many times ;). Nowhere mentioned MemtoLeave for AWE.
thanks
"Uri Dimant" wrote:

> Hi
> Please visit at http://www.sql-server-performance.com/awe_memory.asp
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> to
>
>
|||The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256MB for SQL Server 2000. This is documented in SQL Server BOL topic 'Using Startup Parameters':
Specifies the amount of virtual address space (in megabytes) SQL Server will leave available for memory allocations within the SQL Server process, but outside the SQL Server memory pool. This is the area used by SQL Server for loading items such as extended procedure .dll files, the OLE DB providers referenced by distributed queries, and automation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).
The values are not modified when AWE is enabled. There are no counters in PerfMon to show this value.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
using AWE.
"Andrew J. Kelly" wrote:

> Actually I believe the default is 256MB.
> --
> Andrew J. Kelly SQL MVP
>
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>
>
|||Thanks for the reply. Interestingly there are different numbers ... Both Ken
Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
256mb for sql7.
"Ryan Stonecipher [MSFT]" wrote:

> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256MB for SQL Server 2000. This is documented in SQL Server BOL topic 'Using Startup Parameters':
> Specifies the amount of virtual address space (in megabytes) SQL Server will leave available for memory allocations within the SQL Server process, but outside the SQL Server memory pool. This is the area used by SQL Server for loading items such as exte
nded procedure .dll files, the OLE DB providers referenced by distributed queries, and automation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).[vbcol=seagreen]
> The values are not modified when AWE is enabled. There are no counters in PerfMon to show this value.
> Thanks,
> Ryan Stonecipher
> SQL Server Storage Engine
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
> using AWE.
> "Andrew J. Kelly" wrote:
|||I have seen this stated both ways myself but I do believe as Ryan stated it
is 256MB for 2000.
Andrew J. Kelly SQL MVP
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:B782B0E4-C276-47A9-959F-64C47F3B1A1F@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply. Interestingly there are different numbers ... Both
> Ken
> Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
> 256mb for sql7.
> "Ryan Stonecipher [MSFT]" wrote:
|||A follow up question: I'm using 8GB with AWE and have set sql max mem to 6GB.
Does this mean that MemtoLeave will come from 2GB which I left for OS and 6GB
is resvered sql BPOOL?
thanks
lzhu
"Ryan Stonecipher [MSFT]" wrote:

> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256MB for SQL Server 2000. This is documented in SQL Server BOL topic 'Using Startup Parameters':
> Specifies the amount of virtual address space (in megabytes) SQL Server will leave available for memory allocations within the SQL Server process, but outside the SQL Server memory pool. This is the area used by SQL Server for loading items such as exte
nded procedure .dll files, the OLE DB providers referenced by distributed queries, and automation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).[vbcol=seagreen]
> The values are not modified when AWE is enabled. There are no counters in PerfMon to show this value.
> Thanks,
> Ryan Stonecipher
> SQL Server Storage Engine
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
> using AWE.
> "Andrew J. Kelly" wrote:
|||No the memtoleave is always taken from the 2GB of directly addressable
memory for SQL Server. The OS has it's own 2GB. AWE has no bearing on this
and the only thing within sql server that can use AWE memory (or memory
above 2 or 3GB depending on /3GB) is the data cache. Everything else must
come from the directly addressable memory.
Andrew J. Kelly SQL MVP
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:C32428CD-5EE8-4B4F-B3C1-6761C5FECF26@.microsoft.com...[vbcol=seagreen]
>A follow up question: I'm using 8GB with AWE and have set sql max mem to
>6GB.
> Does this mean that MemtoLeave will come from 2GB which I left for OS and
> 6GB
> is resvered sql BPOOL?
> thanks
> lzhu
> "Ryan Stonecipher [MSFT]" wrote:

MemToLeave in SS2KEE with AWE

How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how to
see it by using win perfmon?
thanks
lzhu@.dba1.comHi
Please visit at http://www.sql-server-performance.com/awe_memory.asp
"lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
to
> see it by using win perfmon?
> thanks
> lzhu@.dba1.com|||Actually I believe the default is 256MB.
--
Andrew J. Kelly SQL MVP
"lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
> to
> see it by using win perfmon?
> thanks
> lzhu@.dba1.com|||256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
using AWE.
"Andrew J. Kelly" wrote:
> Actually I believe the default is 256MB.
> --
> Andrew J. Kelly SQL MVP
>
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> > How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
> > to
> > see it by using win perfmon?
> > thanks
> > lzhu@.dba1.com
>
>|||I've been there many times ;). Nowhere mentioned MemtoLeave for AWE.
thanks
"Uri Dimant" wrote:
> Hi
> Please visit at http://www.sql-server-performance.com/awe_memory.asp
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> > How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
> to
> > see it by using win perfmon?
> > thanks
> > lzhu@.dba1.com
>
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0087_01C4BB43.16A63210
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
The default value in SQL Server 7.0 is 128 MB, and was adjusted up to =256MB for SQL Server 2000. This is documented in SQL Server BOL topic ='Using Startup Parameters':
Specifies the amount of virtual address space (in megabytes) SQL Server =will leave available for memory allocations within the SQL Server =process, but outside the SQL Server memory pool. This is the area used =by SQL Server for loading items such as extended procedure .dll files, =the OLE DB providers referenced by distributed queries, and automation =objects referenced in Transact-SQL statements. The default is 256 =megabytes (MB).
The values are not modified when AWE is enabled. There are no counters =in PerfMon to show this value.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message =news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the =same when using AWE.
"Andrew J. Kelly" wrote:
> Actually I believe the default is 256MB.
> > -- > Andrew J. Kelly SQL MVP
> > > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in =message > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> > How much RAM does sql2K EE with AWE set by default? Is it 384MB? =And how > > to
> > see it by using win perfmon?
> > thanks
> > lzhu@.dba1.com > > >
--=_NextPart_000_0087_01C4BB43.16A63210
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

The default value in SQL Server =7.0 is 128 MB, and was adjusted up to 256MB for SQL Server 2000. This is =documented in SQL Server BOL topic 'Using Startup Parameters':
Specifies the amount of virtual address space (in megabytes) SQL =Server will leave available for memory allocations within the SQL Server =process, but outside the SQL Server memory pool. This is the area used by SQL Server =for loading items such as extended procedure .dll files, the OLE DB =providers referenced by distributed queries, and automation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).
The values are not modified =when AWE is enabled. There are no counters in PerfMon to show this =value.
Thanks,
Ryan Stonecipher
SQL Server Storage =Engine
"lzhu" wrote in message news:631=5334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when = using AWE."Andrew J. Kelly" wrote:> Actually I =believe the default is 256MB.> > -- > Andrew J. =Kelly SQL MVP> > > "lzhu@.dba1.com" wrote in message > news:34B=AFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...> > How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how > > to> > see it by using win = perfmon?> > thanks> > lzhu@.dba1.com > > >

---

--=_NextPart_000_0087_01C4BB43.16A63210--|||Thanks for the reply. Interestingly there are different numbers ... Both Ken
Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
256mb for sql7.
"Ryan Stonecipher [MSFT]" wrote:
> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256MB for SQL Server 2000. This is documented in SQL Server BOL topic 'Using Startup Parameters':
> Specifies the amount of virtual address space (in megabytes) SQL Server will leave available for memory allocations within the SQL Server process, but outside the SQL Server memory pool. This is the area used by SQL Server for loading items such as extended procedure .dll files, the OLE DB providers referenced by distributed queries, and automation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).
> The values are not modified when AWE is enabled. There are no counters in PerfMon to show this value.
> Thanks,
> Ryan Stonecipher
> SQL Server Storage Engine
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
> using AWE.
> "Andrew J. Kelly" wrote:
> > Actually I believe the default is 256MB.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
> > > to
> > > see it by using win perfmon?
> > > thanks
> > > lzhu@.dba1.com
> >
> >
> >|||I have seen this stated both ways myself but I do believe as Ryan stated it
is 256MB for 2000.
--
Andrew J. Kelly SQL MVP
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:B782B0E4-C276-47A9-959F-64C47F3B1A1F@.microsoft.com...
> Thanks for the reply. Interestingly there are different numbers ... Both
> Ken
> Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
> 256mb for sql7.
> "Ryan Stonecipher [MSFT]" wrote:
>> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to
>> 256MB for SQL Server 2000. This is documented in SQL Server BOL topic
>> 'Using Startup Parameters':
>> Specifies the amount of virtual address space (in megabytes) SQL Server
>> will leave available for memory allocations within the SQL Server
>> process, but outside the SQL Server memory pool. This is the area used by
>> SQL Server for loading items such as extended procedure .dll files, the
>> OLE DB providers referenced by distributed queries, and automation
>> objects referenced in Transact-SQL statements. The default is 256
>> megabytes (MB).
>> The values are not modified when AWE is enabled. There are no counters
>> in PerfMon to show this value.
>> Thanks,
>> Ryan Stonecipher
>> SQL Server Storage Engine
>> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
>> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
>> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same
>> when
>> using AWE.
>> "Andrew J. Kelly" wrote:
>> > Actually I believe the default is 256MB.
>> >
>> > --
>> > Andrew J. Kelly SQL MVP
>> >
>> >
>> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in
>> message
>> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB?
>> And how
>> > > to
>> > > see it by using win perfmon?
>> > > thanks
>> > > lzhu@.dba1.com
>> >
>> >
>> >|||A follow up question: I'm using 8GB with AWE and have set sql max mem to 6GB.
Does this mean that MemtoLeave will come from 2GB which I left for OS and 6GB
is resvered sql BPOOL?
thanks
lzhu
"Ryan Stonecipher [MSFT]" wrote:
> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256MB for SQL Server 2000. This is documented in SQL Server BOL topic 'Using Startup Parameters':
> Specifies the amount of virtual address space (in megabytes) SQL Server will leave available for memory allocations within the SQL Server process, but outside the SQL Server memory pool. This is the area used by SQL Server for loading items such as extended procedure .dll files, the OLE DB providers referenced by distributed queries, and automation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).
> The values are not modified when AWE is enabled. There are no counters in PerfMon to show this value.
> Thanks,
> Ryan Stonecipher
> SQL Server Storage Engine
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
> using AWE.
> "Andrew J. Kelly" wrote:
> > Actually I believe the default is 256MB.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
> > > to
> > > see it by using win perfmon?
> > > thanks
> > > lzhu@.dba1.com
> >
> >
> >|||No the memtoleave is always taken from the 2GB of directly addressable
memory for SQL Server. The OS has it's own 2GB. AWE has no bearing on this
and the only thing within sql server that can use AWE memory (or memory
above 2 or 3GB depending on /3GB) is the data cache. Everything else must
come from the directly addressable memory.
--
Andrew J. Kelly SQL MVP
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:C32428CD-5EE8-4B4F-B3C1-6761C5FECF26@.microsoft.com...
>A follow up question: I'm using 8GB with AWE and have set sql max mem to
>6GB.
> Does this mean that MemtoLeave will come from 2GB which I left for OS and
> 6GB
> is resvered sql BPOOL?
> thanks
> lzhu
> "Ryan Stonecipher [MSFT]" wrote:
>> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to
>> 256MB for SQL Server 2000. This is documented in SQL Server BOL topic
>> 'Using Startup Parameters':
>> Specifies the amount of virtual address space (in megabytes) SQL Server
>> will leave available for memory allocations within the SQL Server
>> process, but outside the SQL Server memory pool. This is the area used by
>> SQL Server for loading items such as extended procedure .dll files, the
>> OLE DB providers referenced by distributed queries, and automation
>> objects referenced in Transact-SQL statements. The default is 256
>> megabytes (MB).
>> The values are not modified when AWE is enabled. There are no counters
>> in PerfMon to show this value.
>> Thanks,
>> Ryan Stonecipher
>> SQL Server Storage Engine
>> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
>> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
>> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same
>> when
>> using AWE.
>> "Andrew J. Kelly" wrote:
>> > Actually I believe the default is 256MB.
>> >
>> > --
>> > Andrew J. Kelly SQL MVP
>> >
>> >
>> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in
>> message
>> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB?
>> And how
>> > > to
>> > > see it by using win perfmon?
>> > > thanks
>> > > lzhu@.dba1.com
>> >
>> >
>> >|||This is a multi-part message in MIME format.
--=_NextPart_000_0008_01C4BB66.6640D640
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
I see the confusion: the default value of -g is 256MB in SQL2K. =However, there is an additional amount of space reserved for thread =stacks. By default, we reserve space for 255 worker threads at 512KB =per thread stack, leaving an additional 128MB of space in MTL. That's =the 384MB that Ken's book refers to. (It's the same in SQL 7, resulting =in 256MB of MTL space.)
Sorry for the confusion.
Thanks,
--R
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:OvMj865uEHA.1404@.TK2MSFTNGP11.phx.gbl...
No the memtoleave is always taken from the 2GB of directly addressable =
memory for SQL Server. The OS has it's own 2GB. AWE has no bearing =on this and the only thing within sql server that can use AWE memory (or =memory above 2 or 3GB depending on /3GB) is the data cache. Everything else =must come from the directly addressable memory.
-- Andrew J. Kelly SQL MVP
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:C32428CD-5EE8-4B4F-B3C1-6761C5FECF26@.microsoft.com...
>A follow up question: I'm using 8GB with AWE and have set sql max mem =to >6GB.
> Does this mean that MemtoLeave will come from 2GB which I left for =OS and > 6GB
> is resvered sql BPOOL?
> thanks
> lzhu
>
> "Ryan Stonecipher [MSFT]" wrote:
>
>> The default value in SQL Server 7.0 is 128 MB, and was adjusted up =to >> 256MB for SQL Server 2000. This is documented in SQL Server BOL =topic >> 'Using Startup Parameters':
>>
>> Specifies the amount of virtual address space (in megabytes) SQL =Server >> will leave available for memory allocations within the SQL Server >> process, but outside the SQL Server memory pool. This is the area =used by >> SQL Server for loading items such as extended procedure .dll files, =the >> OLE DB providers referenced by distributed queries, and automation >> objects referenced in Transact-SQL statements. The default is 256 >> megabytes (MB).
>>
>> The values are not modified when AWE is enabled. There are no =counters >> in PerfMon to show this value.
>>
>> Thanks,
>> Ryan Stonecipher
>> SQL Server Storage Engine
>> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message >> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
>> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's =the same >> when
>> using AWE.
>>
>> "Andrew J. Kelly" wrote:
>>
>> > Actually I believe the default is 256MB.
>> >
>> > -- >> > Andrew J. Kelly SQL MVP
>> >
>> >
>> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote =in >> message
>> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>> > > How much RAM does sql2K EE with AWE set by default? Is it =384MB? >> And how
>> > > to
>> > > see it by using win perfmon?
>> > > thanks
>> > > lzhu@.dba1.com
>> >
>> >
>> >
--=_NextPart_000_0008_01C4BB66.6640D640
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

I see the confusion: the default value of -g =is 256MB in SQL2K. However, there is an additional amount of space reserved =for thread stacks. By default, we reserve space for 255 worker threads at =512KB per thread stack, leaving an additional 128MB of space in MTL. That's =the 384MB that Ken's book refers to. (It's the same in SQL 7, =resulting in 256MB of MTL space.)
Sorry for the confusion.
Thanks,
--R
"Andrew J. Kelly" wrote in message news:OvMj865uEHA.1404=@.TK2MSFTNGP11.phx.gbl...No the memtoleave is always taken from the 2GB of directly addressable =memory for SQL Server. The OS has it's own 2GB. AWE has no =bearing on this and the only thing within sql server that can use AWE memory =(or memory above 2 or 3GB depending on /3GB) is the data cache. Everything else must come from the directly addressable =memory.-- Andrew J. Kelly SQL MVP"lzhu" wrote in message news:C32=428CD-5EE8-4B4F-B3C1-6761C5FECF26@.microsoft.com...>A follow up question: I'm using 8GB with AWE and have set sql max mem to = >6GB.> Does this mean that MemtoLeave will come from 2GB =which I left for OS and > 6GB> is resvered sql BPOOL?> thanks> lzhu>> "Ryan Stonecipher [MSFT]" wrote:>> The default value in SQL Server 7.0 is 128 =MB, and was adjusted up to > 256MB for SQL Server 2000. This =is documented in SQL Server BOL topic > 'Using Startup Parameters':>> Specifies the amount of virtual =address space (in megabytes) SQL Server > will leave available for =memory allocations within the SQL Server > process, but outside =the SQL Server memory pool. This is the area used by > SQL Server =for loading items such as extended procedure .dll files, the > =OLE DB providers referenced by distributed queries, and automation => objects referenced in Transact-SQL statements. The default is 256 => megabytes (MB).>> The values are not modified =when AWE is enabled. There are no counters > in PerfMon to =show this value.>> Thanks,> Ryan Stonecipher> SQL Server Storage =Engine> "lzhu" wrote in message > news:631=5334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...> &=nbsp; 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the =same > when> using AWE.>> "Andrew J. Kelly" wrote:>> > Actually I believe the =default is 256MB.> >> > -- = > > Andrew J. Kelly SQL MVP> >> >> > "lzhu@.dba1.com" wrote in > message> > news:34B=AFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...> &=nbsp; > > How much RAM does sql2K EE with AWE set by default? Is =it 384MB? > And how> > > to> > > see it by using win perfmon?> > > =thanks> > > lzhu@.dba1.com> >> >> >

---

--=_NextPart_000_0008_01C4BB66.6640D640--|||The discrepancy is probably because there are two components to MemToLeave.,
Most people just think of MemToLeave as being for the special memory
allocations outside of the buffer pool, and that is 256MB in SQL 2000.
However, there is another component which is the worker thread stacks, which
is .5MB for each work thread. The default number of worker threads is 255,
so that would give us another 128MB, with a total of 384. Since the space
for worker threads is variable is you reconfigure, most people leave it out
of the discussion and only talk about the MemToLeave aread of large
allocations.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:B782B0E4-C276-47A9-959F-64C47F3B1A1F@.microsoft.com...
> Thanks for the reply. Interestingly there are different numbers ... Both
> Ken
> Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
> 256mb for sql7.
> "Ryan Stonecipher [MSFT]" wrote:
>> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to
>> 256MB for SQL Server 2000. This is documented in SQL Server BOL topic
>> 'Using Startup Parameters':
>> Specifies the amount of virtual address space (in megabytes) SQL Server
>> will leave available for memory allocations within the SQL Server
>> process, but outside the SQL Server memory pool. This is the area used by
>> SQL Server for loading items such as extended procedure .dll files, the
>> OLE DB providers referenced by distributed queries, and automation
>> objects referenced in Transact-SQL statements. The default is 256
>> megabytes (MB).
>> The values are not modified when AWE is enabled. There are no counters
>> in PerfMon to show this value.
>> Thanks,
>> Ryan Stonecipher
>> SQL Server Storage Engine
>> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
>> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
>> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same
>> when
>> using AWE.
>> "Andrew J. Kelly" wrote:
>> > Actually I believe the default is 256MB.
>> >
>> > --
>> > Andrew J. Kelly SQL MVP
>> >
>> >
>> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in
>> message
>> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB?
>> And how
>> > > to
>> > > see it by using win perfmon?
>> > > thanks
>> > > lzhu@.dba1.com
>> >
>> >
>> >|||Very good point Kalen. Thanks for bringing that up.
--
Andrew J. Kelly SQL MVP
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%23tFdBJ6uEHA.1264@.TK2MSFTNGP12.phx.gbl...
> The discrepancy is probably because there are two components to
> MemToLeave., Most people just think of MemToLeave as being for the special
> memory allocations outside of the buffer pool, and that is 256MB in SQL
> 2000. However, there is another component which is the worker thread
> stacks, which is .5MB for each work thread. The default number of worker
> threads is 255, so that would give us another 128MB, with a total of 384.
> Since the space for worker threads is variable is you reconfigure, most
> people leave it out of the discussion and only talk about the MemToLeave
> aread of large allocations.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
> news:B782B0E4-C276-47A9-959F-64C47F3B1A1F@.microsoft.com...
>> Thanks for the reply. Interestingly there are different numbers ... Both
>> Ken
>> Hendson's book and an artical on sqljunkies are saying 384mb for sql2k
>> and
>> 256mb for sql7.
>> "Ryan Stonecipher [MSFT]" wrote:
>> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to
>> 256MB for SQL Server 2000. This is documented in SQL Server BOL topic
>> 'Using Startup Parameters':
>> Specifies the amount of virtual address space (in megabytes) SQL Server
>> will leave available for memory allocations within the SQL Server
>> process, but outside the SQL Server memory pool. This is the area used
>> by SQL Server for loading items such as extended procedure .dll files,
>> the OLE DB providers referenced by distributed queries, and automation
>> objects referenced in Transact-SQL statements. The default is 256
>> megabytes (MB).
>> The values are not modified when AWE is enabled. There are no counters
>> in PerfMon to show this value.
>> Thanks,
>> Ryan Stonecipher
>> SQL Server Storage Engine
>> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
>> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
>> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the
>> same when
>> using AWE.
>> "Andrew J. Kelly" wrote:
>> > Actually I believe the default is 256MB.
>> >
>> > --
>> > Andrew J. Kelly SQL MVP
>> >
>> >
>> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in
>> message
>> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB?
>> And how
>> > > to
>> > > see it by using win perfmon?
>> > > thanks
>> > > lzhu@.dba1.com
>> >
>> >
>> >
>|||I understand Memtoleave has to be in the 2GB addressable mem. Given that I've
allocated 6GB (out 8GB) to sql via max mem setting, is this 6GB totally for
BPOOL and 128MB of Memtoleave (for work threads)? and the rest 256MB
memtoleave won't come from this 6GB. Am I right?
thanks
"Andrew J. Kelly" wrote:
> No the memtoleave is always taken from the 2GB of directly addressable
> memory for SQL Server. The OS has it's own 2GB. AWE has no bearing on this
> and the only thing within sql server that can use AWE memory (or memory
> above 2 or 3GB depending on /3GB) is the data cache. Everything else must
> come from the directly addressable memory.
> --
> Andrew J. Kelly SQL MVP
>
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
> news:C32428CD-5EE8-4B4F-B3C1-6761C5FECF26@.microsoft.com...
> >A follow up question: I'm using 8GB with AWE and have set sql max mem to
> >6GB.
> > Does this mean that MemtoLeave will come from 2GB which I left for OS and
> > 6GB
> > is resvered sql BPOOL?
> > thanks
> > lzhu
> >
> > "Ryan Stonecipher [MSFT]" wrote:
> >
> >> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to
> >> 256MB for SQL Server 2000. This is documented in SQL Server BOL topic
> >> 'Using Startup Parameters':
> >>
> >> Specifies the amount of virtual address space (in megabytes) SQL Server
> >> will leave available for memory allocations within the SQL Server
> >> process, but outside the SQL Server memory pool. This is the area used by
> >> SQL Server for loading items such as extended procedure .dll files, the
> >> OLE DB providers referenced by distributed queries, and automation
> >> objects referenced in Transact-SQL statements. The default is 256
> >> megabytes (MB).
> >>
> >> The values are not modified when AWE is enabled. There are no counters
> >> in PerfMon to show this value.
> >>
> >> Thanks,
> >> Ryan Stonecipher
> >> SQL Server Storage Engine
> >> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
> >> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> >> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same
> >> when
> >> using AWE.
> >>
> >> "Andrew J. Kelly" wrote:
> >>
> >> > Actually I believe the default is 256MB.
> >> >
> >> > --
> >> > Andrew J. Kelly SQL MVP
> >> >
> >> >
> >> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in
> >> message
> >> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> >> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB?
> >> And how
> >> > > to
> >> > > see it by using win perfmon?
> >> > > thanks
> >> > > lzhu@.dba1.com
> >> >
> >> >
> >> >
>
>|||thanks for the clarification! Is 'Inside sql2005' coming soon?;)
"Kalen Delaney" wrote:
> The discrepancy is probably because there are two components to MemToLeave.,
> Most people just think of MemToLeave as being for the special memory
> allocations outside of the buffer pool, and that is 256MB in SQL 2000.
> However, there is another component which is the worker thread stacks, which
> is .5MB for each work thread. The default number of worker threads is 255,
> so that would give us another 128MB, with a total of 384. Since the space
> for worker threads is variable is you reconfigure, most people leave it out
> of the discussion and only talk about the MemToLeave aread of large
> allocations.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
> news:B782B0E4-C276-47A9-959F-64C47F3B1A1F@.microsoft.com...
> > Thanks for the reply. Interestingly there are different numbers ... Both
> > Ken
> > Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
> > 256mb for sql7.
> >
> > "Ryan Stonecipher [MSFT]" wrote:
> >
> >> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to
> >> 256MB for SQL Server 2000. This is documented in SQL Server BOL topic
> >> 'Using Startup Parameters':
> >>
> >> Specifies the amount of virtual address space (in megabytes) SQL Server
> >> will leave available for memory allocations within the SQL Server
> >> process, but outside the SQL Server memory pool. This is the area used by
> >> SQL Server for loading items such as extended procedure .dll files, the
> >> OLE DB providers referenced by distributed queries, and automation
> >> objects referenced in Transact-SQL statements. The default is 256
> >> megabytes (MB).
> >>
> >> The values are not modified when AWE is enabled. There are no counters
> >> in PerfMon to show this value.
> >>
> >> Thanks,
> >> Ryan Stonecipher
> >> SQL Server Storage Engine
> >> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
> >> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> >> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same
> >> when
> >> using AWE.
> >>
> >> "Andrew J. Kelly" wrote:
> >>
> >> > Actually I believe the default is 256MB.
> >> >
> >> > --
> >> > Andrew J. Kelly SQL MVP
> >> >
> >> >
> >> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in
> >> message
> >> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> >> > > How much RAM does sql2K EE with AWE set by default? Is it 384MB?
> >> And how
> >> > > to
> >> > > see it by using win perfmon?
> >> > > thanks
> >> > > lzhu@.dba1.com
> >> >
> >> >
> >> >
>
>|||Hi Izhu
This is not quite accurate. Ken Henderson's SQL Server Architecture book has
the most detailed description of SQL Server memory management. I learn
something new every time I read the memory chapter. Here is an exerpt from
it:
http://msdn.microsoft.com/SQL/sqlarchitecture/?pull=/library/en-us/dnsqldev/html/sqldev_01262004.asp
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:0933B681-31AF-4180-971B-327EBFE0B5B6@.microsoft.com...
>I understand Memtoleave has to be in the 2GB addressable mem. Given that
>I've
> allocated 6GB (out 8GB) to sql via max mem setting, is this 6GB totally
> for
> BPOOL and 128MB of Memtoleave (for work threads)? and the rest 256MB
> memtoleave won't come from this 6GB. Am I right?
> thanks
>
> "Andrew J. Kelly" wrote:
>> No the memtoleave is always taken from the 2GB of directly addressable
>> memory for SQL Server. The OS has it's own 2GB. AWE has no bearing on
>> this
>> and the only thing within sql server that can use AWE memory (or memory
>> above 2 or 3GB depending on /3GB) is the data cache. Everything else
>> must
>> come from the directly addressable memory.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
>> news:C32428CD-5EE8-4B4F-B3C1-6761C5FECF26@.microsoft.com...
>> >A follow up question: I'm using 8GB with AWE and have set sql max mem to
>> >6GB.
>> > Does this mean that MemtoLeave will come from 2GB which I left for OS
>> > and
>> > 6GB
>> > is resvered sql BPOOL?
>> > thanks
>> > lzhu
>> >
>> > "Ryan Stonecipher [MSFT]" wrote:
>> >
>> >> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to
>> >> 256MB for SQL Server 2000. This is documented in SQL Server BOL topic
>> >> 'Using Startup Parameters':
>> >>
>> >> Specifies the amount of virtual address space (in megabytes) SQL
>> >> Server
>> >> will leave available for memory allocations within the SQL Server
>> >> process, but outside the SQL Server memory pool. This is the area used
>> >> by
>> >> SQL Server for loading items such as extended procedure .dll files,
>> >> the
>> >> OLE DB providers referenced by distributed queries, and automation
>> >> objects referenced in Transact-SQL statements. The default is 256
>> >> megabytes (MB).
>> >>
>> >> The values are not modified when AWE is enabled. There are no
>> >> counters
>> >> in PerfMon to show this value.
>> >>
>> >> Thanks,
>> >> Ryan Stonecipher
>> >> SQL Server Storage Engine
>> >> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message
>> >> news:6315334A-491C-4B35-B1E8-6667E9A55B90@.microsoft.com...
>> >> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the
>> >> same
>> >> when
>> >> using AWE.
>> >>
>> >> "Andrew J. Kelly" wrote:
>> >>
>> >> > Actually I believe the default is 256MB.
>> >> >
>> >> > --
>> >> > Andrew J. Kelly SQL MVP
>> >> >
>> >> >
>> >> > "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in
>> >> message
>> >> > news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>> >> > > How much RAM does sql2K EE with AWE set by default? Is it
>> >> 384MB?
>> >> And how
>> >> > > to
>> >> > > see it by using win perfmon?
>> >> > > thanks
>> >> > > lzhu@.dba1.com
>> >> >
>> >> >
>> >> >
>>

MemToLeave in SS2KEE with AWE

How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how t
o
see it by using win perfmon?
thanks
lzhu@.dba1.comHi
Please visit at http://www.sql-server-performance.com/awe_memory.asp
"lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
to
> see it by using win perfmon?
> thanks
> lzhu@.dba1.com|||Actually I believe the default is 256MB.
Andrew J. Kelly SQL MVP
"lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> How much RAM does sql2K EE with AWE set by default? Is it 384MB? And how
> to
> see it by using win perfmon?
> thanks
> lzhu@.dba1.com|||256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
using AWE.
"Andrew J. Kelly" wrote:

> Actually I believe the default is 256MB.
> --
> Andrew J. Kelly SQL MVP
>
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>
>|||I've been there many times ;). Nowhere mentioned MemtoLeave for AWE.
thanks
"Uri Dimant" wrote:

> Hi
> Please visit at http://www.sql-server-performance.com/awe_memory.asp
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
> to
>
>|||The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256MB
for SQL Server 2000. This is documented in SQL Server BOL topic 'Using Star
tup Parameters':
Specifies the amount of virtual address space (in megabytes) SQL Server will
leave available for memory allocations within the SQL Server process, but o
utside the SQL Server memory pool. This is the area used by SQL Server for l
oading items such as extended procedure .dll files, the OLE DB providers ref
erenced by distributed queries, and automation objects referenced in Transac
t-SQL statements. The default is 256 megabytes (MB).
The values are not modified when AWE is enabled. There are no counters in P
erfMon to show this value.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-491C-
4B35-B1E8-6667E9A55B90@.microsoft.com...
256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same when
using AWE.
"Andrew J. Kelly" wrote:

> Actually I believe the default is 256MB.
>
> --
> Andrew J. Kelly SQL MVP
>
>
> "lzhu@.dba1.com" <lzhu@.dba1.com@.discussions.microsoft.com> wrote in message
> news:34BAFBDC-BDDB-4509-9F02-972DBD30567F@.microsoft.com...
>
>
>|||Thanks for the reply. Interestingly there are different numbers ... Both Ken
Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
256mb for sql7.
"Ryan Stonecipher [MSFT]" wrote:

> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256M
B for SQL Server 2000. This is documented in SQL Server BOL topic 'Using St
artup Parameters':
> Specifies the amount of virtual address space (in megabytes) SQL Server will leave
available for memory allocations within the SQL Server process, but outside the SQL
Server memory pool. This is the area used by SQL Server for loading items such as e
xte
nded procedure .dll files, the OLE DB providers referenced by distributed queries, and autom
ation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).[vbco
l=seagreen]
> The values are not modified when AWE is enabled. There are no counters in
PerfMon to show this value.
> Thanks,
> Ryan Stonecipher
> SQL Server Storage Engine
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-4
91C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same
when
> using AWE.
> "Andrew J. Kelly" wrote:
>|||I have seen this stated both ways myself but I do believe as Ryan stated it
is 256MB for 2000.
Andrew J. Kelly SQL MVP
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:B782B0E4-C276-47A9-959F-64C47F3B1A1F@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply. Interestingly there are different numbers ... Both
> Ken
> Hendson's book and an artical on sqljunkies are saying 384mb for sql2k and
> 256mb for sql7.
> "Ryan Stonecipher [MSFT]" wrote:
>|||A follow up question: I'm using 8GB with AWE and have set sql max mem to 6GB
.
Does this mean that MemtoLeave will come from 2GB which I left for OS and 6G
B
is resvered sql BPOOL?
thanks
lzhu
"Ryan Stonecipher [MSFT]" wrote:

> The default value in SQL Server 7.0 is 128 MB, and was adjusted up to 256M
B for SQL Server 2000. This is documented in SQL Server BOL topic 'Using St
artup Parameters':
> Specifies the amount of virtual address space (in megabytes) SQL Server will leave
available for memory allocations within the SQL Server process, but outside the SQL
Server memory pool. This is the area used by SQL Server for loading items such as e
xte
nded procedure .dll files, the OLE DB providers referenced by distributed queries, and autom
ation objects referenced in Transact-SQL statements. The default is 256 megabytes (MB).[vbco
l=seagreen]
> The values are not modified when AWE is enabled. There are no counters in
PerfMon to show this value.
> Thanks,
> Ryan Stonecipher
> SQL Server Storage Engine
> "lzhu" <lzhu@.discussions.microsoft.com> wrote in message news:6315334A-4
91C-4B35-B1E8-6667E9A55B90@.microsoft.com...
> 256MB is sql7 and 384MB for sql2000. I'm just not sure if it's the same
when
> using AWE.
> "Andrew J. Kelly" wrote:
>|||No the memtoleave is always taken from the 2GB of directly addressable
memory for SQL Server. The OS has it's own 2GB. AWE has no bearing on this
and the only thing within sql server that can use AWE memory (or memory
above 2 or 3GB depending on /3GB) is the data cache. Everything else must
come from the directly addressable memory.
Andrew J. Kelly SQL MVP
"lzhu" <lzhu@.discussions.microsoft.com> wrote in message
news:C32428CD-5EE8-4B4F-B3C1-6761C5FECF26@.microsoft.com...[vbcol=seagreen]
>A follow up question: I'm using 8GB with AWE and have set sql max mem to
>6GB.
> Does this mean that MemtoLeave will come from 2GB which I left for OS and
> 6GB
> is resvered sql BPOOL?
> thanks
> lzhu
> "Ryan Stonecipher [MSFT]" wrote:
>sql

Memory, Available Bytes

I'm using a performance console system monitor to observe memory performance
of a Win 2K server, running 2K SQL server.
The available bytes indicates less than half of the system's total physical
memory of
4 gig. Could this be a possible indication of a memory leak. What, if any
possible
solutions are available. Thanks to everyone for being there to help.Hi
If the Server has 4GB RAM, and is Enterprise Edition of Windows 2000, is the
/3GB flag set in boot.ini ?
If not, only 2GB of the possible 3GB is presented to applications. The other
1GB is always reserved for the OS.
If it is Standard Edition of Windows 2000, supported is only 2GB of the 4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"coenzyme" wrote:

> I'm using a performance console system monitor to observe memory performan
ce
> of a Win 2K server, running 2K SQL server.
> The available bytes indicates less than half of the system's total physica
l
> memory of
> 4 gig. Could this be a possible indication of a memory leak. What, if any
> possible
> solutions are available. Thanks to everyone for being there to help.

Memory, Available Bytes

I'm using a performance console system monitor to observe memory performance
of a Win 2K server, running 2K SQL server.
The available bytes indicates less than half of the system's total physical
memory of
4 gig. Could this be a possible indication of a memory leak. What, if any
possible
solutions are available. Thanks to everyone for being there to help.
Hi
If the Server has 4GB RAM, and is Enterprise Edition of Windows 2000, is the
/3GB flag set in boot.ini ?
If not, only 2GB of the possible 3GB is presented to applications. The other
1GB is always reserved for the OS.
If it is Standard Edition of Windows 2000, supported is only 2GB of the 4GB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"coenzyme" wrote:

> I'm using a performance console system monitor to observe memory performance
> of a Win 2K server, running 2K SQL server.
> The available bytes indicates less than half of the system's total physical
> memory of
> 4 gig. Could this be a possible indication of a memory leak. What, if any
> possible
> solutions are available. Thanks to everyone for being there to help.

Memory, Available Bytes

I'm using a performance console system monitor to observe memory performance
of a Win 2K server, running 2K SQL server.
The available bytes indicates less than half of the system's total physical
memory of
4 gig. Could this be a possible indication of a memory leak. What, if any
possible
solutions are available. Thanks to everyone for being there to help.Hi
If the Server has 4GB RAM, and is Enterprise Edition of Windows 2000, is the
/3GB flag set in boot.ini ?
If not, only 2GB of the possible 3GB is presented to applications. The other
1GB is always reserved for the OS.
If it is Standard Edition of Windows 2000, supported is only 2GB of the 4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"coenzyme" wrote:
> I'm using a performance console system monitor to observe memory performance
> of a Win 2K server, running 2K SQL server.
> The available bytes indicates less than half of the system's total physical
> memory of
> 4 gig. Could this be a possible indication of a memory leak. What, if any
> possible
> solutions are available. Thanks to everyone for being there to help.sql

Memory Usage Following ISA Installation

Hi There
I have just installed ISA 2004 to a Win 2003 server. This had also installed
an instance of SQL MSDE which is eating up the memory. Is there an easy
command prompt statement or registry hack I can run to restrict the maximum
memory usage possible as we are regularly getting "Low Virtual Memory" errors
as it does not seem to be releasing the memory quickly enough. I'm not very
familiar with SQL, so any help out be greatly appriciated. There is no SQL or
MSDE option under the programs list in the Start Menu, so I can't open
Enterprise manager like you would on a normal SQL box. However, there is a
SQL folder within the Program Files directory although this looks a bit slim
compared to a normal install. Failing being able to restrict memory usage, is
it feasble to remove the MSDE installation? I also have Backup Exec running
which is dependant upon the MSSQL service.
Many thanks
Bob
INF: SQL Server Memory Usage:
http://support.microsoft.com/default...;en-us;q321363
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Bob Sampson" wrote:

> Hi There
> I have just installed ISA 2004 to a Win 2003 server. This had also installed
> an instance of SQL MSDE which is eating up the memory. Is there an easy
> command prompt statement or registry hack I can run to restrict the maximum
> memory usage possible as we are regularly getting "Low Virtual Memory" errors
> as it does not seem to be releasing the memory quickly enough. I'm not very
> familiar with SQL, so any help out be greatly appriciated. There is no SQL or
> MSDE option under the programs list in the Start Menu, so I can't open
> Enterprise manager like you would on a normal SQL box. However, there is a
> SQL folder within the Program Files directory although this looks a bit slim
> compared to a normal install. Failing being able to restrict memory usage, is
> it feasble to remove the MSDE installation? I also have Backup Exec running
> which is dependant upon the MSSQL service.
> Many thanks
> Bob
|||Thanks for the reply, however, maybe its me, but I didn't think that really
answered my problem, maybe I'm not looking in the right places, but where is
the Min and Max memory settings? Is it something I have to do from a command
prompt?
Bob
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> INF: SQL Server Memory Usage:
> http://support.microsoft.com/default...;en-us;q321363
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Bob Sampson" wrote:
|||Hi
Yes. MSDE does not have a UI, you need to run T-SQL code through OSQL.
To set a minimum of 64Mb and a Maximum of 256Mb, run from the command
prompt:
osql -Q"sp_configure 'min server memory', 64 RECONFIGURE WITH OVERRIDE" -E
osql -Q"sp_configure 'sp_configure 'max server memory', 256 RECONFIGURE WITH
OVERRIDE" -E
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Bob Sampson" <BobSampson@.discussions.microsoft.com> wrote in message
news:44FB02FD-8B86-4061-B8AC-D2D4F9F38165@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply, however, maybe its me, but I didn't think that
> really
> answered my problem, maybe I'm not looking in the right places, but where
> is
> the Min and Max memory settings? Is it something I have to do from a
> command
> prompt?
> Bob
> "Mike Epprecht (SQL MVP)" wrote:

Memory Problem

Hello,
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. The
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times every
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can see
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
over.
Anyone any ideas why this is happening?
Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
related error messages? If you still didn't find anything, you should open a case with MS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache. The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times every
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can see
> inline with this login process the memory sqlservr.exe uses increases). The
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> over.
> Anyone any ideas why this is happening?
|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:

> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
> related error messages? If you still didn't find anything, you should open a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>
>
|||I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and that you would need
assistance from MS to either work around it or have them prepare a hotfix for you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> KB articles that cover the issue, can't find anything on web at all really (a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:

> I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and that you would need
> assistance from MS to either work around it or have them prepare a hotfix for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
>
>
|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
burt_king@.yahoo.com
"BenUK" wrote:
[vbcol=seagreen]
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
|||no problem, will do
"burt_king" wrote:
[vbcol=seagreen]
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.

Memory Problem

Hello,
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. The
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times every
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can see
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
over.
Anyone any ideas why this is happening?Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
related error messages? If you still didn't find anything, you should open a case with MS.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache. The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times every
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can see
> inline with this login process the memory sqlservr.exe uses increases). The
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> over.
> Anyone any ideas why this is happening?|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:
> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for the
> related error messages? If you still didn't find anything, you should open a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > Hello,
> >
> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > fine and dandy, except for one application that's causing me a headache. The
> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > and sits on a dual processor box with 2GB of RAM.
> > Through profiler and performance monitor I can see the app logs into SQL,
> > runs a sql statement, and logs out again - it does this circa 250 times every
> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > release it, seemingly it's due to this login process (on perfmon I can see
> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > inline with this login process the memory sqlservr.exe uses increases). The
> > memory increases at a rate of around 116mb per hour, and when it hits the
> > physical limit, SQL crashes. The actual error in the log relates to
> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > over.
> >
> > Anyone any ideas why this is happening?
>
>|||I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and that you would need
assistance from MS to either work around it or have them prepare a hotfix for you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> KB articles that cover the issue, can't find anything on web at all really (a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
>> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
>> the
>> related error messages? If you still didn't find anything, you should open a case with MS.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
>> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>> > Hello,
>> >
>> > I look after several SQL server DB's, all are SQL 2000 standard edition,
>> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
>> > fine and dandy, except for one application that's causing me a headache. The
>> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
>> > and sits on a dual processor box with 2GB of RAM.
>> > Through profiler and performance monitor I can see the app logs into SQL,
>> > runs a sql statement, and logs out again - it does this circa 250 times every
>> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
>> > release it, seemingly it's due to this login process (on perfmon I can see
>> > when the logins occur every 30 seconds or so, and using taskmanager I can see
>> > inline with this login process the memory sqlservr.exe uses increases). The
>> > memory increases at a rate of around 116mb per hour, and when it hits the
>> > physical limit, SQL crashes. The actual error in the log relates to
>> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
>> > over.
>> >
>> > Anyone any ideas why this is happening?
>>|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:
> I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and that you would need
> assistance from MS to either work around it or have them prepare a hotfix for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > KB articles that cover the issue, can't find anything on web at all really (a
> > part from a couple with slight relavance)
> >
> > "Tibor Karaszi" wrote:
> >
> >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> >> the
> >> related error messages? If you still didn't find anything, you should open a case with MS.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> >> > Hello,
> >> >
> >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> >> > fine and dandy, except for one application that's causing me a headache. The
> >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> >> > and sits on a dual processor box with 2GB of RAM.
> >> > Through profiler and performance monitor I can see the app logs into SQL,
> >> > runs a sql statement, and logs out again - it does this circa 250 times every
> >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> >> > release it, seemingly it's due to this login process (on perfmon I can see
> >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> >> > inline with this login process the memory sqlservr.exe uses increases). The
> >> > memory increases at a rate of around 116mb per hour, and when it hits the
> >> > physical limit, SQL crashes. The actual error in the log relates to
> >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> >> > over.
> >> >
> >> > Anyone any ideas why this is happening?
> >>
> >>
> >>
>
>|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
--
burt_king@.yahoo.com
"BenUK" wrote:
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
> > I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> > that your code hit a memory leak in that code section of SQL Server, and that you would need
> > assistance from MS to either work around it or have them prepare a hotfix for you.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > > KB articles that cover the issue, can't find anything on web at all really (a
> > > part from a couple with slight relavance)
> > >
> > > "Tibor Karaszi" wrote:
> > >
> > >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> > >> the
> > >> related error messages? If you still didn't find anything, you should open a case with MS.
> > >>
> > >> --
> > >> Tibor Karaszi, SQL Server MVP
> > >> http://www.karaszi.com/sqlserver/default.asp
> > >> http://www.solidqualitylearning.com/
> > >>
> > >>
> > >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > >> > Hello,
> > >> >
> > >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > >> > fine and dandy, except for one application that's causing me a headache. The
> > >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > >> > and sits on a dual processor box with 2GB of RAM.
> > >> > Through profiler and performance monitor I can see the app logs into SQL,
> > >> > runs a sql statement, and logs out again - it does this circa 250 times every
> > >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > >> > release it, seemingly it's due to this login process (on perfmon I can see
> > >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > >> > inline with this login process the memory sqlservr.exe uses increases). The
> > >> > memory increases at a rate of around 116mb per hour, and when it hits the
> > >> > physical limit, SQL crashes. The actual error in the log relates to
> > >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > >> > over.
> > >> >
> > >> > Anyone any ideas why this is happening?
> > >>
> > >>
> > >>
> >
> >
> >|||no problem, will do
"burt_king" wrote:
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
> > Thanks for your help Tibor :-)
> >
> > "Tibor Karaszi" wrote:
> >
> > > I did a quick Google search and I guess we found similar cases. Not exactly your case. My guess is
> > > that your code hit a memory leak in that code section of SQL Server, and that you would need
> > > assistance from MS to either work around it or have them prepare a hotfix for you.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > > news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
> > > > Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
> > > > KB articles that cover the issue, can't find anything on web at all really (a
> > > > part from a couple with slight relavance)
> > > >
> > > > "Tibor Karaszi" wrote:
> > > >
> > > >> Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Did you search KB for
> > > >> the
> > > >> related error messages? If you still didn't find anything, you should open a case with MS.
> > > >>
> > > >> --
> > > >> Tibor Karaszi, SQL Server MVP
> > > >> http://www.karaszi.com/sqlserver/default.asp
> > > >> http://www.solidqualitylearning.com/
> > > >>
> > > >>
> > > >> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> > > >> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> > > >> > Hello,
> > > >> >
> > > >> > I look after several SQL server DB's, all are SQL 2000 standard edition,
> > > >> > some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> > > >> > fine and dandy, except for one application that's causing me a headache. The
> > > >> > SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1,
> > > >> > and sits on a dual processor box with 2GB of RAM.
> > > >> > Through profiler and performance monitor I can see the app logs into SQL,
> > > >> > runs a sql statement, and logs out again - it does this circa 250 times every
> > > >> > 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
> > > >> > release it, seemingly it's due to this login process (on perfmon I can see
> > > >> > when the logins occur every 30 seconds or so, and using taskmanager I can see
> > > >> > inline with this login process the memory sqlservr.exe uses increases). The
> > > >> > memory increases at a rate of around 116mb per hour, and when it hits the
> > > >> > physical limit, SQL crashes. The actual error in the log relates to
> > > >> > CImageHelper:: and dbghelp.dll and gets posted several times before SQL falls
> > > >> > over.
> > > >> >
> > > >> > Anyone any ideas why this is happening?
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.

Memory Problem

Hello,
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. Th
e
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1
,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times ever
y
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can se
e
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL fall
s
over.
Anyone any ideas why this is happening?Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Di
d you search KB for the
related error messages? If you still didn't find anything, you should open a
case with MS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache.
The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 S
P1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times ev
ery
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn'
t
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can
see
> inline with this login process the memory sqlservr.exe uses increases). T
he
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL fa
lls
> over.
> Anyone any ideas why this is happening?|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (
a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:

> Sounds like you hit a bug in SQL Server. Are you current on Service Pack?
Did you search KB for the
> related error messages? If you still didn't find anything, you should open
a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>
>|||I did a quick Google search and I guess we found similar cases. Not exactly
your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and tha
t you would need
assistance from MS to either work around it or have them prepare a hotfix fo
r you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find an
y
> KB articles that cover the issue, can't find anything on web at all really
(a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
>|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:

> I did a quick Google search and I guess we found similar cases. Not exactl
y your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and t
hat you would need
> assistance from MS to either work around it or have them prepare a hotfix
for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
>
>|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
--
burt_king@.yahoo.com
"BenUK" wrote:
[vbcol=seagreen]
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
>|||no problem, will do
"burt_king" wrote:
[vbcol=seagreen]
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
>|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.

Memory Management: SQL Enterprise, 2000 Adv. Srv.

Questions
A) If I have the /3GB /PAE variables in the Win 2k Server boot.ini and only have 2 gig of memory will this cause issues with memory readings I am seeing in Performance Monitor? (I know it doesn't make sense to have but happened out of circumstance
B) From what I am reading if "SQLServer: Memory Manager -- Target Server Memory (KB)" provides the same value as "SQLServer: Memory Manager -- Total Server Memory (KB)" then SQL is content and has as much memory as it needs. What I am seeing on my SQL server is that the two numbers match but are using all the memory on the server which is 2 GB. I assume that this means increase the amount of memory on the box. Am I correct in this assumption
C) Again from reading my understanding is that when using AWE (under 16 GB), SQL at startup will grab the specified chunk of RAM you have alotted to it. I was wondering if there are any counters within Performance Monitor that will tell me exactly how much of that RAM (AWE) SQL Server is using
Thanks...Anyone?

Memory management (fixed memory, AWE)

Hi,

I am going to install SQL Server 2000 (then SQL 2K5) on a Win Server 2K3 with 8 GB of ram, but it will be 16 GB in the near future.

I would like to reserve a fixed memory (for momemt less than 3-4 GB) for SQL Server and the rest for application (virtualization).

Without AWE enabled, max memory for SQL Server 2K5 is 4GB as for SQL Server 2000?

How can I manage and optimize memory keeping in mind AWE. (any doc, website available?)

Thank

I forgot to write that SQL server is 2000 Standard Ed:

On Windows Server 2003, max memory is 2 or 4 GB

And in the case of SQL Server 2K5?

Thank

|||

I am a bit confused by your questions but I can tell you that SQL 2005 Std. edition UNLIKE 2000's max memory is only bound by the OS it runs on. Thus I have deployed sql 2005 std on 2003 server ent. with 16GBs of memory in them.

Derek

|||fasttrack, did this solve your problems? Can you update thread?|||

Thank,

how to solve:

/PAE for win server 2003 Enterprise edition.

If SQL server 2000 Std, not enable AW, because max memory is 4 gb.

If SQL server 2000 Ent AWE enable to take advantage of all memory available. Setted max memory for other applications.

If SQL server 2005, both std and Ent AWE is enable. Max memory setted for others applications

Memory management (fixed memory, AWE)

Hi,

I am going to install SQL Server 2000 (then SQL 2K5) on a Win Server 2K3 with 8 GB of ram, but it will be 16 GB in the near future.

I would like to reserve a fixed memory (for momemt less than 3-4 GB) for SQL Server and the rest for application (virtualization).

Without AWE enabled, max memory for SQL Server 2K5 is 4GB as for SQL Server 2000?

How can I manage and optimize memory keeping in mind AWE. (any doc, website available?)

Thank

I forgot to write that SQL server is 2000 Standard Ed:

On Windows Server 2003, max memory is 2 or 4 GB

And in the case of SQL Server 2K5?

Thank

|||

I am a bit confused by your questions but I can tell you that SQL 2005 Std. edition UNLIKE 2000's max memory is only bound by the OS it runs on. Thus I have deployed sql 2005 std on 2003 server ent. with 16GBs of memory in them.

Derek

|||fasttrack, did this solve your problems? Can you update thread?|||

Thank,

how to solve:

/PAE for win server 2003 Enterprise edition.

If SQL server 2000 Std, not enable AW, because max memory is 4 gb.

If SQL server 2000 Ent AWE enable to take advantage of all memory available. Setted max memory for other applications.

If SQL server 2005, both std and Ent AWE is enable. Max memory setted for others applications