We have an I64 server with 12 GB of Ram. On this server we have an instance
of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
SSMS. This instance seems to be running fine but is always using all the 6
GB of memory according to task manager (if I increase the max memory it will
use it). We also have an instance of SQL 2005 Enterprise with max memory set
to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AWE
on 64 bit servers but I did just in case. I hope this is enough server info
so I'll get on with the problem. The 2005 instance doesn't seem to be
running very well and from the task manager I've never seen it use more then
124 MB of memory. It seems to have way too much I\O writes and between the
two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
Model 2 Stepping 1 1596 MHz CPUs.
I talked to someone at Microsoft and they said to ignore Task Manager reading
(nice). You can tell SQL memory usage by using Performance Monitor object
SQL Memory Management counters "Target Server Memory" and "Total Server
Memory". So, unless you are a DBA and know about this, Task Manager misleads
you.
"Kenny" wrote:
> We have an I64 server with 12 GB of Ram. On this server we have an instance
> of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
> SSMS. This instance seems to be running fine but is always using all the 6
> GB of memory according to task manager (if I increase the max memory it will
> use it). We also have an instance of SQL 2005 Enterprise with max memory set
> to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AWE
> on 64 bit servers but I did just in case. I hope this is enough server info
> so I'll get on with the problem. The 2005 instance doesn't seem to be
> running very well and from the task manager I've never seen it use more then
> 124 MB of memory. It seems to have way too much I\O writes and between the
> two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
> Model 2 Stepping 1 1596 MHz CPUs.
>
Friday, February 24, 2012
Memory not being used by 2005 instance
We have an I64 server with 12 GB of Ram. On this server we have an instance
of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
SSMS. This instance seems to be running fine but is always using all the 6
GB of memory according to task manager (if I increase the max memory it will
use it). We also have an instance of SQL 2005 Enterprise with max memory se
t
to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AW
E
on 64 bit servers but I did just in case. I hope this is enough server info
so I'll get on with the problem. The 2005 instance doesn't seem to be
running very well and from the task manager I've never seen it use more then
124 MB of memory. It seems to have way too much I\O writes and between the
two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
Model 2 Stepping 1 1596 MHz CPUs.I talked to someone at Microsoft and they said to ignore Task Manager readin
g
(nice). You can tell SQL memory usage by using Performance Monitor object
SQL Memory Management counters "Target Server Memory" and "Total Server
Memory". So, unless you are a DBA and know about this, Task Manager mislead
s
you.
"Kenny" wrote:
> We have an I64 server with 12 GB of Ram. On this server we have an instan
ce
> of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on fr
om
> SSMS. This instance seems to be running fine but is always using all the
6
> GB of memory according to task manager (if I increase the max memory it wi
ll
> use it). We also have an instance of SQL 2005 Enterprise with max memory
set
> to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on
AWE
> on 64 bit servers but I did just in case. I hope this is enough server in
fo
> so I'll get on with the problem. The 2005 instance doesn't seem to be
> running very well and from the task manager I've never seen it use more th
en
> 124 MB of memory. It seems to have way too much I\O writes and between th
e
> two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
> Model 2 Stepping 1 1596 MHz CPUs.
>
of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
SSMS. This instance seems to be running fine but is always using all the 6
GB of memory according to task manager (if I increase the max memory it will
use it). We also have an instance of SQL 2005 Enterprise with max memory se
t
to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AW
E
on 64 bit servers but I did just in case. I hope this is enough server info
so I'll get on with the problem. The 2005 instance doesn't seem to be
running very well and from the task manager I've never seen it use more then
124 MB of memory. It seems to have way too much I\O writes and between the
two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
Model 2 Stepping 1 1596 MHz CPUs.I talked to someone at Microsoft and they said to ignore Task Manager readin
g
(nice). You can tell SQL memory usage by using Performance Monitor object
SQL Memory Management counters "Target Server Memory" and "Total Server
Memory". So, unless you are a DBA and know about this, Task Manager mislead
s
you.
"Kenny" wrote:
> We have an I64 server with 12 GB of Ram. On this server we have an instan
ce
> of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on fr
om
> SSMS. This instance seems to be running fine but is always using all the
6
> GB of memory according to task manager (if I increase the max memory it wi
ll
> use it). We also have an instance of SQL 2005 Enterprise with max memory
set
> to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on
AWE
> on 64 bit servers but I did just in case. I hope this is enough server in
fo
> so I'll get on with the problem. The 2005 instance doesn't seem to be
> running very well and from the task manager I've never seen it use more th
en
> 124 MB of memory. It seems to have way too much I\O writes and between th
e
> two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
> Model 2 Stepping 1 1596 MHz CPUs.
>
Memory not being used by 2005 instance
We have an I64 server with 12 GB of Ram. On this server we have an instance
of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
SSMS. This instance seems to be running fine but is always using all the 6
GB of memory according to task manager (if I increase the max memory it will
use it). We also have an instance of SQL 2005 Enterprise with max memory set
to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AWE
on 64 bit servers but I did just in case. I hope this is enough server info
so I'll get on with the problem. The 2005 instance doesn't seem to be
running very well and from the task manager I've never seen it use more then
124 MB of memory. It seems to have way too much I\O writes and between the
two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
Model 2 Stepping 1 1596 MHz CPUs.I talked to someone at Microsoft and they said to ignore Task Manager reading
(nice). You can tell SQL memory usage by using Performance Monitor object
SQL Memory Management counters "Target Server Memory" and "Total Server
Memory". So, unless you are a DBA and know about this, Task Manager misleads
you.
"Kenny" wrote:
> We have an I64 server with 12 GB of Ram. On this server we have an instance
> of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
> SSMS. This instance seems to be running fine but is always using all the 6
> GB of memory according to task manager (if I increase the max memory it will
> use it). We also have an instance of SQL 2005 Enterprise with max memory set
> to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AWE
> on 64 bit servers but I did just in case. I hope this is enough server info
> so I'll get on with the problem. The 2005 instance doesn't seem to be
> running very well and from the task manager I've never seen it use more then
> 124 MB of memory. It seems to have way too much I\O writes and between the
> two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
> Model 2 Stepping 1 1596 MHz CPUs.
>
of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
SSMS. This instance seems to be running fine but is always using all the 6
GB of memory according to task manager (if I increase the max memory it will
use it). We also have an instance of SQL 2005 Enterprise with max memory set
to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AWE
on 64 bit servers but I did just in case. I hope this is enough server info
so I'll get on with the problem. The 2005 instance doesn't seem to be
running very well and from the task manager I've never seen it use more then
124 MB of memory. It seems to have way too much I\O writes and between the
two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
Model 2 Stepping 1 1596 MHz CPUs.I talked to someone at Microsoft and they said to ignore Task Manager reading
(nice). You can tell SQL memory usage by using Performance Monitor object
SQL Memory Management counters "Target Server Memory" and "Total Server
Memory". So, unless you are a DBA and know about this, Task Manager misleads
you.
"Kenny" wrote:
> We have an I64 server with 12 GB of Ram. On this server we have an instance
> of SQL 2000 Enterprise with max memory set to 6 GB and AWE is turned on from
> SSMS. This instance seems to be running fine but is always using all the 6
> GB of memory according to task manager (if I increase the max memory it will
> use it). We also have an instance of SQL 2005 Enterprise with max memory set
> to 3 GB and AWE is turned on from SSMS. I know you don't have to turn on AWE
> on 64 bit servers but I did just in case. I hope this is enough server info
> so I'll get on with the problem. The 2005 instance doesn't seem to be
> running very well and from the task manager I've never seen it use more then
> 124 MB of memory. It seems to have way too much I\O writes and between the
> two they keep the CPUs pegged. This server has 2 Itanium 2 ia64 Family 31
> Model 2 Stepping 1 1596 MHz CPUs.
>
Memory More than 2G ==> 3GB switch
All,
We have a dell system with 2 processors(4 by the technique of
hyperthreading) and 4 GB of RAM.
This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
I have added the /3GB switch into the boot.ini and set the memory of
SQL fixed to 3043 MB RAM.
The problem is the following :
I think that my server isn't using the 3 Gig of Memory for
applications because of 2 reasons
- the error initdata: Warning: Could not set working set size to
1353312 KB.
- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
I know that sqlserveragent is not the same as sqlserver but I expect
then that the sqlserveragent should detect 1GB or 3GB - 3 is most
likely- and not 2 GB.
2 GB should be normal if the /3GB switch isn't used.
Question:
How can i really check if the 3 GB switch is activated and working.
I have found a document at microsoft but that link doesnt clarify
because on a server and on an enterprise edition the pagedpoolsize is
the same .
http://www.microsoft.com/resources/d..._4gt_tools.asp
Hi
This feature will work on Windows 2000 DataCenter or Advenced Server
machines. Do you have SQL Server installed on one of them?
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/d...003/all/techre
f/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp
|||What edition of the OS and SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<romaric_decoene@.yahoo.com> wrote in message news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/d..._4gt_tools.asp
|||- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
incorrectly reports what it can see rather than the amount of memory on the
server and is independent of what SQL Server can address.
Do you have Advanced Server and SQL2000 EE ?
Have you specified the "set working set size" ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/d...003/all/techre
f/en-us/w2k3tr_4gt_tools.asp
|||We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
edition.
The working set size is set to 1
Does this mean that SQLserver agent can't see that the 3gb switch is
enabled and therefore suppose thats it is the standard 2Gb for
applications and 2 Gb for system? Will it then compete with sql server
service for memory or with the system ?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
> incorrectly reports what it can see rather than the amount of memory on the
> server and is independent of what SQL Server can address.
> Do you have Advanced Server and SQL2000 EE ?
> Have you specified the "set working set size" ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> <romaric_decoene@.yahoo.com> wrote in message
> news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> http://www.microsoft.com/resources/d...003/all/techre
> f/en-us/w2k3tr_4gt_tools.asp
|||I would set the "set working set size" option to 0
exec sp_configure 'set working',0
reconfigure
and restart the server.
SQLAgent isn't large memory aware or compiled with the /3GB switch so it can
see the standard 2GB user mode address space that all normal win32 processes
can. It comptetes with SQL Server in the same sense that opening notepad on
the server does i.e. not much :-) it's all just virtual address space after
all.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405250329.482e96a9@.posting.google.c om...
> We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
> edition.
> The working set size is set to 1
> Does this mean that SQLserver agent can't see that the 3gb switch is
> enabled and therefore suppose thats it is the standard 2Gb for
> applications and 2 Gb for system? Will it then compete with sql server
> service for memory or with the system ?
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
but[vbcol=seagreen]
the[vbcol=seagreen]
http://www.microsoft.com/resources/d...003/all/techre[vbcol=seagreen]
We have a dell system with 2 processors(4 by the technique of
hyperthreading) and 4 GB of RAM.
This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
I have added the /3GB switch into the boot.ini and set the memory of
SQL fixed to 3043 MB RAM.
The problem is the following :
I think that my server isn't using the 3 Gig of Memory for
applications because of 2 reasons
- the error initdata: Warning: Could not set working set size to
1353312 KB.
- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
I know that sqlserveragent is not the same as sqlserver but I expect
then that the sqlserveragent should detect 1GB or 3GB - 3 is most
likely- and not 2 GB.
2 GB should be normal if the /3GB switch isn't used.
Question:
How can i really check if the 3 GB switch is activated and working.
I have found a document at microsoft but that link doesnt clarify
because on a server and on an enterprise edition the pagedpoolsize is
the same .
http://www.microsoft.com/resources/d..._4gt_tools.asp
Hi
This feature will work on Windows 2000 DataCenter or Advenced Server
machines. Do you have SQL Server installed on one of them?
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/d...003/all/techre
f/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp
|||What edition of the OS and SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<romaric_decoene@.yahoo.com> wrote in message news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/d..._4gt_tools.asp
|||- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
incorrectly reports what it can see rather than the amount of memory on the
server and is independent of what SQL Server can address.
Do you have Advanced Server and SQL2000 EE ?
Have you specified the "set working set size" ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/d...003/all/techre
f/en-us/w2k3tr_4gt_tools.asp
|||We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
edition.
The working set size is set to 1
Does this mean that SQLserver agent can't see that the 3gb switch is
enabled and therefore suppose thats it is the standard 2Gb for
applications and 2 Gb for system? Will it then compete with sql server
service for memory or with the system ?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
> incorrectly reports what it can see rather than the amount of memory on the
> server and is independent of what SQL Server can address.
> Do you have Advanced Server and SQL2000 EE ?
> Have you specified the "set working set size" ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> <romaric_decoene@.yahoo.com> wrote in message
> news:e4d6707e.0405240241.706d25f1@.posting.google.c om...
> http://www.microsoft.com/resources/d...003/all/techre
> f/en-us/w2k3tr_4gt_tools.asp
|||I would set the "set working set size" option to 0
exec sp_configure 'set working',0
reconfigure
and restart the server.
SQLAgent isn't large memory aware or compiled with the /3GB switch so it can
see the standard 2GB user mode address space that all normal win32 processes
can. It comptetes with SQL Server in the same sense that opening notepad on
the server does i.e. not much :-) it's all just virtual address space after
all.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405250329.482e96a9@.posting.google.c om...
> We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
> edition.
> The working set size is set to 1
> Does this mean that SQLserver agent can't see that the 3gb switch is
> enabled and therefore suppose thats it is the standard 2Gb for
> applications and 2 Gb for system? Will it then compete with sql server
> service for memory or with the system ?
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
but[vbcol=seagreen]
the[vbcol=seagreen]
http://www.microsoft.com/resources/d...003/all/techre[vbcol=seagreen]
Memory More than 2G ==> 3GB switch
All,
We have a dell system with 2 processors(4 by the technique of
hyperthreading) and 4 GB of RAM.
This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
I have added the /3GB switch into the boot.ini and set the memory of
SQL fixed to 3043 MB RAM.
The problem is the following :
I think that my server isn't using the 3 Gig of Memory for
applications because of 2 reasons
- the error initdata: Warning: Could not set working set size to
1353312 KB.
- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
I know that sqlserveragent is not the same as sqlserver but I expect
then that the sqlserveragent should detect 1GB or 3GB - 3 is most
likely- and not 2 GB.
2 GB should be normal if the /3GB switch isn't used.
Question:
How can i really check if the 3 GB switch is activated and working.
I have found a document at microsoft but that link doesnt clarify
because on a server and on an enterprise edition the pagedpoolsize is
the same .
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3tr_4gt_tools.aspHi
This feature will work on Windows 2000 DataCenter or Advenced Server
machines. Do you have SQL Server installed on one of them?
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
f/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||What edition of the OS and SQL Server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<romaric_decoene@.yahoo.com> wrote in message news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3tr_4gt_tools.asp|||- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
incorrectly reports what it can see rather than the amount of memory on the
server and is independent of what SQL Server can address.
Do you have Advanced Server and SQL2000 EE ?
Have you specified the "set working set size" ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
edition.
The working set size is set to 1
Does this mean that SQLserver agent can't see that the 3gb switch is
enabled and therefore suppose thats it is the standard 2Gb for
applications and 2 Gb for system? Will it then compete with sql server
service for memory or with the system ?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
> incorrectly reports what it can see rather than the amount of memory on the
> server and is independent of what SQL Server can address.
> Do you have Advanced Server and SQL2000 EE ?
> Have you specified the "set working set size" ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> <romaric_decoene@.yahoo.com> wrote in message
> news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> > All,
> >
> > We have a dell system with 2 processors(4 by the technique of
> > hyperthreading) and 4 GB of RAM.
> > This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> > I have added the /3GB switch into the boot.ini and set the memory of
> > SQL fixed to 3043 MB RAM.
> >
> > The problem is the following :
> >
> > I think that my server isn't using the 3 Gig of Memory for
> > applications because of 2 reasons
> > - the error initdata: Warning: Could not set working set size to
> > 1353312 KB.
> > - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> > detected
> >
> > I know that sqlserveragent is not the same as sqlserver but I expect
> > then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> > likely- and not 2 GB.
> > 2 GB should be normal if the /3GB switch isn't used.
> >
> > Question:
> >
> > How can i really check if the 3 GB switch is activated and working.
> > I have found a document at microsoft but that link doesnt clarify
> > because on a server and on an enterprise edition the pagedpoolsize is
> > the same .
> >
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
> f/en-us/w2k3tr_4gt_tools.asp|||I would set the "set working set size" option to 0
exec sp_configure 'set working',0
reconfigure
and restart the server.
SQLAgent isn't large memory aware or compiled with the /3GB switch so it can
see the standard 2GB user mode address space that all normal win32 processes
can. It comptetes with SQL Server in the same sense that opening notepad on
the server does i.e. not much :-) it's all just virtual address space after
all.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405250329.482e96a9@.posting.google.com...
> We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
> edition.
> The working set size is set to 1
> Does this mean that SQLserver agent can't see that the 3gb switch is
> enabled and therefore suppose thats it is the standard 2Gb for
> applications and 2 Gb for system? Will it then compete with sql server
> service for memory or with the system ?
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...
> > - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> > detected
> >
> > SQL Agent can't see more than 2 GB regardless of what SQL Server can see
but
> > incorrectly reports what it can see rather than the amount of memory on
the
> > server and is independent of what SQL Server can address.
> >
> > Do you have Advanced Server and SQL2000 EE ?
> > Have you specified the "set working set size" ?
> >
> > --
> > HTH
> >
> > Jasper Smith (SQL Server MVP)
> >
> > I support PASS - the definitive, global
> > community for SQL Server professionals -
> > http://www.sqlpass.org
> >
> >
> > <romaric_decoene@.yahoo.com> wrote in message
> > news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> > > All,
> > >
> > > We have a dell system with 2 processors(4 by the technique of
> > > hyperthreading) and 4 GB of RAM.
> > > This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> > > I have added the /3GB switch into the boot.ini and set the memory of
> > > SQL fixed to 3043 MB RAM.
> > >
> > > The problem is the following :
> > >
> > > I think that my server isn't using the 3 Gig of Memory for
> > > applications because of 2 reasons
> > > - the error initdata: Warning: Could not set working set size to
> > > 1353312 KB.
> > > - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> > > detected
> > >
> > > I know that sqlserveragent is not the same as sqlserver but I expect
> > > then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> > > likely- and not 2 GB.
> > > 2 GB should be normal if the /3GB switch isn't used.
> > >
> > > Question:
> > >
> > > How can i really check if the 3 GB switch is activated and working.
> > > I have found a document at microsoft but that link doesnt clarify
> > > because on a server and on an enterprise edition the pagedpoolsize is
> > > the same .
> > >
> >
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
> > f/en-us/w2k3tr_4gt_tools.asp
We have a dell system with 2 processors(4 by the technique of
hyperthreading) and 4 GB of RAM.
This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
I have added the /3GB switch into the boot.ini and set the memory of
SQL fixed to 3043 MB RAM.
The problem is the following :
I think that my server isn't using the 3 Gig of Memory for
applications because of 2 reasons
- the error initdata: Warning: Could not set working set size to
1353312 KB.
- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
I know that sqlserveragent is not the same as sqlserver but I expect
then that the sqlserveragent should detect 1GB or 3GB - 3 is most
likely- and not 2 GB.
2 GB should be normal if the /3GB switch isn't used.
Question:
How can i really check if the 3 GB switch is activated and working.
I have found a document at microsoft but that link doesnt clarify
because on a server and on an enterprise edition the pagedpoolsize is
the same .
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3tr_4gt_tools.aspHi
This feature will work on Windows 2000 DataCenter or Advenced Server
machines. Do you have SQL Server installed on one of them?
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
f/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||What edition of the OS and SQL Server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<romaric_decoene@.yahoo.com> wrote in message news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3tr_4gt_tools.asp|||- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
incorrectly reports what it can see rather than the amount of memory on the
server and is independent of what SQL Server can address.
Do you have Advanced Server and SQL2000 EE ?
Have you specified the "set working set size" ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
edition.
The working set size is set to 1
Does this mean that SQLserver agent can't see that the 3gb switch is
enabled and therefore suppose thats it is the standard 2Gb for
applications and 2 Gb for system? Will it then compete with sql server
service for memory or with the system ?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
> incorrectly reports what it can see rather than the amount of memory on the
> server and is independent of what SQL Server can address.
> Do you have Advanced Server and SQL2000 EE ?
> Have you specified the "set working set size" ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> <romaric_decoene@.yahoo.com> wrote in message
> news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> > All,
> >
> > We have a dell system with 2 processors(4 by the technique of
> > hyperthreading) and 4 GB of RAM.
> > This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> > I have added the /3GB switch into the boot.ini and set the memory of
> > SQL fixed to 3043 MB RAM.
> >
> > The problem is the following :
> >
> > I think that my server isn't using the 3 Gig of Memory for
> > applications because of 2 reasons
> > - the error initdata: Warning: Could not set working set size to
> > 1353312 KB.
> > - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> > detected
> >
> > I know that sqlserveragent is not the same as sqlserver but I expect
> > then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> > likely- and not 2 GB.
> > 2 GB should be normal if the /3GB switch isn't used.
> >
> > Question:
> >
> > How can i really check if the 3 GB switch is activated and working.
> > I have found a document at microsoft but that link doesnt clarify
> > because on a server and on an enterprise edition the pagedpoolsize is
> > the same .
> >
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
> f/en-us/w2k3tr_4gt_tools.asp|||I would set the "set working set size" option to 0
exec sp_configure 'set working',0
reconfigure
and restart the server.
SQLAgent isn't large memory aware or compiled with the /3GB switch so it can
see the standard 2GB user mode address space that all normal win32 processes
can. It comptetes with SQL Server in the same sense that opening notepad on
the server does i.e. not much :-) it's all just virtual address space after
all.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405250329.482e96a9@.posting.google.com...
> We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
> edition.
> The working set size is set to 1
> Does this mean that SQLserver agent can't see that the 3gb switch is
> enabled and therefore suppose thats it is the standard 2Gb for
> applications and 2 Gb for system? Will it then compete with sql server
> service for memory or with the system ?
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...
> > - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> > detected
> >
> > SQL Agent can't see more than 2 GB regardless of what SQL Server can see
but
> > incorrectly reports what it can see rather than the amount of memory on
the
> > server and is independent of what SQL Server can address.
> >
> > Do you have Advanced Server and SQL2000 EE ?
> > Have you specified the "set working set size" ?
> >
> > --
> > HTH
> >
> > Jasper Smith (SQL Server MVP)
> >
> > I support PASS - the definitive, global
> > community for SQL Server professionals -
> > http://www.sqlpass.org
> >
> >
> > <romaric_decoene@.yahoo.com> wrote in message
> > news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> > > All,
> > >
> > > We have a dell system with 2 processors(4 by the technique of
> > > hyperthreading) and 4 GB of RAM.
> > > This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> > > I have added the /3GB switch into the boot.ini and set the memory of
> > > SQL fixed to 3043 MB RAM.
> > >
> > > The problem is the following :
> > >
> > > I think that my server isn't using the 3 Gig of Memory for
> > > applications because of 2 reasons
> > > - the error initdata: Warning: Could not set working set size to
> > > 1353312 KB.
> > > - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> > > detected
> > >
> > > I know that sqlserveragent is not the same as sqlserver but I expect
> > > then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> > > likely- and not 2 GB.
> > > 2 GB should be normal if the /3GB switch isn't used.
> > >
> > > Question:
> > >
> > > How can i really check if the 3 GB switch is activated and working.
> > > I have found a document at microsoft but that link doesnt clarify
> > > because on a server and on an enterprise edition the pagedpoolsize is
> > > the same .
> > >
> >
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
> > f/en-us/w2k3tr_4gt_tools.asp
Monday, February 20, 2012
Memory More than 2G ==> 3GB switch
All,
We have a dell system with 2 processors(4 by the technique of
hyperthreading) and 4 GB of RAM.
This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
I have added the /3GB switch into the boot.ini and set the memory of
SQL fixed to 3043 MB RAM.
The problem is the following :
I think that my server isn't using the 3 Gig of Memory for
applications because of 2 reasons
- the error initdata: Warning: Could not set working set size to
1353312 KB.
- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
I know that sqlserveragent is not the same as sqlserver but I expect
then that the sqlserveragent should detect 1GB or 3GB - 3 is most
likely- and not 2 GB.
2 GB should be normal if the /3GB switch isn't used.
Question:
How can i really check if the 3 GB switch is activated and working.
I have found a document at microsoft but that link doesnt clarify
because on a server and on an enterprise edition the pagedpoolsize is
the same .
s/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3
tr_4gt_tools.asp" target="_blank">http://www.microsoft.com/resources/...r_4gt_tools.aspHi
This feature will work on Windows 2000 DataCenter or Advenced Server
machines. Do you have SQL Server installed on one of them?
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/...2003/all/techre
f/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||What edition of the OS and SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<romaric_decoene@.yahoo.com> wrote in message news:e4d6707e.0405240241.706d25f1@.posting.googl
e.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
s/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3
tr_4gt_tools.asp" target="_blank">http://www.microsoft.com/resources/...r_4gt_tools.asp|||- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
incorrectly reports what it can see rather than the amount of memory on the
server and is independent of what SQL Server can address.
Do you have Advanced Server and SQL2000 EE ?
Have you specified the "set working set size" ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
s/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre" target="_blank">http://www.microsoft.com/resources/...2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
edition.
The working set size is set to 1
Does this mean that SQLserver agent can't see that the 3gb switch is
enabled and therefore suppose thats it is the standard 2Gb for
applications and 2 Gb for system? Will it then compete with sql server
service for memory or with the system ?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message news:<#ChXD0bQEHA.3456@.TK2MSFTNG
P11.phx.gbl>...
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> SQL Agent can't see more than 2 GB regardless of what SQL Server can see b
ut
> incorrectly reports what it can see rather than the amount of memory on th
e
> server and is independent of what SQL Server can address.
> Do you have Advanced Server and SQL2000 EE ?
> Have you specified the "set working set size" ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> <romaric_decoene@.yahoo.com> wrote in message
> news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> -us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre" target="_blank">http://www.microsoft.com/resources/...2003/all/techre
> f/en-us/w2k3tr_4gt_tools.asp|||I would set the "set working set size" option to 0
exec sp_configure 'set working',0
reconfigure
and restart the server.
SQLAgent isn't large memory aware or compiled with the /3GB switch so it can
see the standard 2GB user mode address space that all normal win32 processes
can. It comptetes with SQL Server in the same sense that opening notepad on
the server does i.e. not much :-) it's all just virtual address space after
all.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405250329.482e96a9@.posting.google.com...
> We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
> edition.
> The working set size is set to 1
> Does this mean that SQLserver agent can't see that the 3gb switch is
> enabled and therefore suppose thats it is the standard 2Gb for
> applications and 2 Gb for system? Will it then compete with sql server
> service for memory or with the system ?
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
but[vbcol=seagreen]
the[vbcol=seagreen]
l=/resources/documentation/windowsServ/2003/all/techre" target="_blank">http://www.microsoft.com/resources/...2003/all/techre[vbcol=seagreen]
We have a dell system with 2 processors(4 by the technique of
hyperthreading) and 4 GB of RAM.
This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
I have added the /3GB switch into the boot.ini and set the memory of
SQL fixed to 3043 MB RAM.
The problem is the following :
I think that my server isn't using the 3 Gig of Memory for
applications because of 2 reasons
- the error initdata: Warning: Could not set working set size to
1353312 KB.
- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
I know that sqlserveragent is not the same as sqlserver but I expect
then that the sqlserveragent should detect 1GB or 3GB - 3 is most
likely- and not 2 GB.
2 GB should be normal if the /3GB switch isn't used.
Question:
How can i really check if the 3 GB switch is activated and working.
I have found a document at microsoft but that link doesnt clarify
because on a server and on an enterprise edition the pagedpoolsize is
the same .
s/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3
tr_4gt_tools.asp" target="_blank">http://www.microsoft.com/resources/...r_4gt_tools.aspHi
This feature will work on Windows 2000 DataCenter or Advenced Server
machines. Do you have SQL Server installed on one of them?
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
http://www.microsoft.com/resources/...2003/all/techre
f/en-us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||What edition of the OS and SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<romaric_decoene@.yahoo.com> wrote in message news:e4d6707e.0405240241.706d25f1@.posting.googl
e.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
s/Default.asp?url=/resources/documentation/windowsServ/2003/all/techref/en-us/w2k3
tr_4gt_tools.asp" target="_blank">http://www.microsoft.com/resources/...r_4gt_tools.asp|||- sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
detected
SQL Agent can't see more than 2 GB regardless of what SQL Server can see but
incorrectly reports what it can see rather than the amount of memory on the
server and is independent of what SQL Server can address.
Do you have Advanced Server and SQL2000 EE ?
Have you specified the "set working set size" ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> All,
> We have a dell system with 2 processors(4 by the technique of
> hyperthreading) and 4 GB of RAM.
> This system is fully dedicated to SQL 2000 sp 3a, hotfix 818.
> I have added the /3GB switch into the boot.ini and set the memory of
> SQL fixed to 3043 MB RAM.
> The problem is the following :
> I think that my server isn't using the 3 Gig of Memory for
> applications because of 2 reasons
> - the error initdata: Warning: Could not set working set size to
> 1353312 KB.
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> I know that sqlserveragent is not the same as sqlserver but I expect
> then that the sqlserveragent should detect 1GB or 3GB - 3 is most
> likely- and not 2 GB.
> 2 GB should be normal if the /3GB switch isn't used.
> Question:
> How can i really check if the 3 GB switch is activated and working.
> I have found a document at microsoft but that link doesnt clarify
> because on a server and on an enterprise edition the pagedpoolsize is
> the same .
>
s/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre" target="_blank">http://www.microsoft.com/resources/...2003/all/techre
f/en-us/w2k3tr_4gt_tools.asp|||We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
edition.
The working set size is set to 1
Does this mean that SQLserver agent can't see that the 3gb switch is
enabled and therefore suppose thats it is the standard 2Gb for
applications and 2 Gb for system? Will it then compete with sql server
service for memory or with the system ?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message news:<#ChXD0bQEHA.3456@.TK2MSFTNG
P11.phx.gbl>...
> - sqlserveragent agentlog [310] 4 processor(s) and 2048 MB RAM
> detected
> SQL Agent can't see more than 2 GB regardless of what SQL Server can see b
ut
> incorrectly reports what it can see rather than the amount of memory on th
e
> server and is independent of what SQL Server can address.
> Do you have Advanced Server and SQL2000 EE ?
> Have you specified the "set working set size" ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> <romaric_decoene@.yahoo.com> wrote in message
> news:e4d6707e.0405240241.706d25f1@.posting.google.com...
> -us/Default.asp?url=/resources/documentation/windowsServ/2003/all/techre" target="_blank">http://www.microsoft.com/resources/...2003/all/techre
> f/en-us/w2k3tr_4gt_tools.asp|||I would set the "set working set size" option to 0
exec sp_configure 'set working',0
reconfigure
and restart the server.
SQLAgent isn't large memory aware or compiled with the /3GB switch so it can
see the standard 2GB user mode address space that all normal win32 processes
can. It comptetes with SQL Server in the same sense that opening notepad on
the server does i.e. not much :-) it's all just virtual address space after
all.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<romaric_decoene@.yahoo.com> wrote in message
news:e4d6707e.0405250329.482e96a9@.posting.google.com...
> We are running Windows 2003 Enterprise Server with SQL 2000 Enterprise
> edition.
> The working set size is set to 1
> Does this mean that SQLserver agent can't see that the 3gb switch is
> enabled and therefore suppose thats it is the standard 2Gb for
> applications and 2 Gb for system? Will it then compete with sql server
> service for memory or with the system ?
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:<#ChXD0bQEHA.3456@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
but[vbcol=seagreen]
the[vbcol=seagreen]
l=/resources/documentation/windowsServ/2003/all/techre" target="_blank">http://www.microsoft.com/resources/...2003/all/techre[vbcol=seagreen]
Memory Mgt in SQL SERVER
I have a performance and memory management issues with SQL SERVER. I
feel SQL server does not releases the unused memory back to the OS. I
have been monitoring that at the end of the day the SQL SERVER
performance gets really bad. And it this point it has acquired all the
Cache it could. I have abt 4 GB of RAM on my server and out of it SQL
SERVER uses almost 2.7 GB whether there is load on the machine or not.
If there any way or tool to monitor this. Also is there any way to Free
memory from SQL server back to OS.Hi
feel SQL server does not releases the unused memory back to the OS. I
have been monitoring that at the end of the day the SQL SERVER
performance gets really bad. And it this point it has acquired all the
Cache it could. I have abt 4 GB of RAM on my server and out of it SQL
SERVER uses almost 2.7 GB whether there is load on the machine or not.
If there any way or tool to monitor this. Also is there any way to Free
memory from SQL server back to OS.Hi
If you have SQL Server configured to use memory dynamically, (Which is
the default and usually best left unless you have a speciffic reason to
change it) SQL Server will take as much memory as it needs. It then
does not release that memory unless another process needs it. It is
designed to work that way. I believe the only way to reset the memory
usage is to stop and start the SQL Server service. If it is not causing
a problem don't worry about it.
If it does cause a problem, set a limit on the amount of memory that
SQL Server can use.
Regards
John|||Take a look at:
http://support.microsoft.com/defaul...kb;en-us;321363
-Andy
"smileydip" <dipeshn.shah@.gmail.com> wrote in message
news:1112793252.056543.6430@.f14g2000cwb.googlegrou ps.com...
>I have a performance and memory management issues with SQL SERVER. I
> feel SQL server does not releases the unused memory back to the OS. I
> have been monitoring that at the end of the day the SQL SERVER
> performance gets really bad. And it this point it has acquired all the
> Cache it could. I have abt 4 GB of RAM on my server and out of it SQL
> SERVER uses almost 2.7 GB whether there is load on the machine or not.
> If there any way or tool to monitor this. Also is there any way to Free
> memory from SQL server back to OS.|||"smileydip" <dipeshn.shah@.gmail.com> wrote in message
news:1112793252.056543.6430@.f14g2000cwb.googlegrou ps.com...
> I have a performance and memory management issues with SQL SERVER. I
> feel SQL server does not releases the unused memory back to the OS.
Unless you're using AWE, it does release memory to the OS if the OS request.
However, as SQL is faster with as much memory as possible, it normally will
grab as much as it can and keep it as long as itcan.
> I
> have been monitoring that at the end of the day the SQL SERVER
> performance gets really bad. And it this point it has acquired all the
> Cache it could. I have abt 4 GB of RAM on my server and out of it SQL
> SERVER uses almost 2.7 GB whether there is load on the machine or not.
Sounds about right.
> If there any way or tool to monitor this. Also is there any way to Free
> memory from SQL server back to OS.
Why do you think this will help your performance issue? Almost certainly
the performance issue is related to something else.
Subscribe to:
Posts (Atom)