Memory Usage on SQL 2000

Good Morning All,
I have a SQL server with 8GB of memory and 8 processors. The memory use in
Task Manager is showing over 7GB in use but the processes in Task Manager do
not add up to anywhere near that amount of RAM being used.
My question is how do I determine what is using all of the RAM on this server?
Thanks, SeanHi
Once you use PAE or AWE, task manager does not show the memory correctly.
You need to look at the Performance Counters presented in the OS perfmon
utility.
The see what is configured for SQL run the following in QA:
sp_configure 'show advanced options', 1
sp_configure 'awe enabled'
sp_configure 'min server memory'
sp_configure 'max server memory'
Regards
Mike
"Sean" wrote:
> Good Morning All,
> I have a SQL server with 8GB of memory and 8 processors. The memory use in
> Task Manager is showing over 7GB in use but the processes in Task Manager do
> not add up to anywhere near that amount of RAM being used.
> My question is how do I determine what is using all of the RAM on this server?
> Thanks, Sean

Memory Usage on SQL 2000

Good Morning All,
I have a SQL server with 8GB of memory and 8 processors. The memory use in
Task Manager is showing over 7GB in use but the processes in Task Manager do
not add up to anywhere near that amount of RAM being used.
My question is how do I determine what is using all of the RAM on this server?
Thanks, Sean
Hi
Once you use PAE or AWE, task manager does not show the memory correctly.
You need to look at the Performance Counters presented in the OS perfmon
utility.
The see what is configured for SQL run the following in QA:
sp_configure 'show advanced options', 1
sp_configure 'awe enabled'
sp_configure 'min server memory'
sp_configure 'max server memory'
Regards
Mike
"Sean" wrote:

> Good Morning All,
> I have a SQL server with 8GB of memory and 8 processors. The memory use in
> Task Manager is showing over 7GB in use but the processes in Task Manager do
> not add up to anywhere near that amount of RAM being used.
> My question is how do I determine what is using all of the RAM on this server?
> Thanks, Sean

Memory Usage on SQL 2000

Good Morning All,
I have a SQL server with 8GB of memory and 8 processors. The memory use in
Task Manager is showing over 7GB in use but the processes in Task Manager do
not add up to anywhere near that amount of RAM being used.
My question is how do I determine what is using all of the RAM on this serve
r?
Thanks, SeanHi
Once you use PAE or AWE, task manager does not show the memory correctly.
You need to look at the Performance Counters presented in the OS perfmon
utility.
The see what is configured for SQL run the following in QA:
sp_configure 'show advanced options', 1
sp_configure 'awe enabled'
sp_configure 'min server memory'
sp_configure 'max server memory'
Regards
Mike
"Sean" wrote:

> Good Morning All,
> I have a SQL server with 8GB of memory and 8 processors. The memory use i
n
> Task Manager is showing over 7GB in use but the processes in Task Manager
do
> not add up to anywhere near that amount of RAM being used.
> My question is how do I determine what is using all of the RAM on this ser
ver?
> Thanks, Sean

Memory Usage Active - Active

Dear all,
i am planing to implement a Windows 2003 Cluster with MS SQl 2000
Enterprise Edition. I have 2 Nodes (4 * XEON MP Processors) with 8 GB
RAM per Node.
I have the need for 6 SQL instances and would like to implement a
active-active cluster. What do you think it the best way to configure
the memory for the Servers ?
I would like to run 3 instanced per Node but can i allocate 7 GB per
Node for SQL (and 1 for the Operating System) ?
What is happening then i one server fails ?
Should i plan to allocate only 3 GB per Server for SQL to make sure
that one server can handle the load for all instances if one server
fails ?
Should i use the /AWE switch only in the boot.ini to allow more than 4
GB Memory ?
or should i use the /3 GB switch as well ?
Maybe somebody can give me a hint.
Best regards,
Walter
Answers inline...
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Walter" <2oznet@.gmx.de> wrote in message
news:58bb24fd.0412172354.505a3c4a@.posting.google.c om...
> Dear all,
> i am planing to implement a Windows 2003 Cluster with MS SQl 2000
> Enterprise Edition. I have 2 Nodes (4 * XEON MP Processors) with 8 GB
> RAM per Node.
> I have the need for 6 SQL instances and would like to implement a
> active-active cluster. What do you think it the best way to configure
> the memory for the Servers ?
Which instances need the most RAM? That is a lot of instance for only two
machines.

> I would like to run 3 instanced per Node but can i allocate 7 GB per
> Node for SQL (and 1 for the Operating System) ?
Again, what are the database/instance requirements.

> What is happening then i one server fails ?
>
You will then failover and have one heck of busy server!!! All 6 instances
will run, but I bet a lot slower.

> Should i plan to allocate only 3 GB per Server for SQL to make sure
> that one server can handle the load for all instances if one server
> fails ?
Can your applications handle that config? That is not a lot of memory for 3
copies of SQL to run under. Not a lot by any stretch.

> Should i use the /AWE switch only in the boot.ini to allow more than 4
> GB Memory ?
Does your hardware support /AWE? If so, yes.

> or should i use the /3 GB switch as well ?
Yes!

> Maybe somebody can give me a hint.
I would love to know your business factors that requir 6 instances of SQL.

> Best regards,
> Walter
|||There might be some dev/test cases where eveyrone wants to have the sysadmin
access to the SQL instance. It then may make sense to give each a separate
instance with the sysadmin rights to keep them isolated from each other. But
I agree you really need to think hard whether there is sufficient rationale
for having six SQL instances in a two-node cluster with 4-way servers.
Linchi
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:usaAppQ5EHA.3472@.TK2MSFTNGP09.phx.gbl...
> Answers inline...
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://www.msmvps.com/clustering - Blog
> "Walter" <2oznet@.gmx.de> wrote in message
> news:58bb24fd.0412172354.505a3c4a@.posting.google.c om...
> Which instances need the most RAM? That is a lot of instance for only two
> machines.
>
> Again, what are the database/instance requirements.
>
> You will then failover and have one heck of busy server!!! All 6 instances
> will run, but I bet a lot slower.
>
> Can your applications handle that config? That is not a lot of memory for
> 3 copies of SQL to run under. Not a lot by any stretch.
>
> Does your hardware support /AWE? If so, yes.
>
> Yes!
>
> I would love to know your business factors that requir 6 instances of SQL.
>
>

memory prob w/SQL 2000

We just purchased a new server - Dell 6550, quad 2G
processors, 6G RAM running Windows 2000 Advanced Server.
I installed SQL 2000 Standard Edition and moved my
databases to this new system. My problem is that now the
sql service will continually use memory until it gets to
about 1.7G and then it locks up the service. No one can
login to the application that uses the db's and you can't
access the db's via Enterprise Manager or sql Query.
Stopping and restarting the service does not help. I have
to actually reboot the server. I tried using the memory
setting in the sql server properties but it doesn't help.
Any ideas or solutions?
Thanks for your help!
CathyYou need to set the /3GB and /PAE switches in the boot.ini file and enable
the AWE option in SQL Server to use the full 6GB. Since AWE will use all
the memory in a fixed manner you should then set the max memory setting in
Sql Server to something less than 6GB. See here for more details:
http://www.sql-server-performance.com/awe_memory.asp Using AWE Memory
http://www.support.microsoft.com/?id=321363 SQL Server 7 & 2000 memory
usage
http://www.support.microsoft.com/?id=274750 Memory config
http://www.support.microsoft.com/?id=283037 Large Memory Support Is
Available in Windows 2000 (AWE)
http://www.support.microsoft.com/?id=811891 Can not use more than 2GB of
memory
Andrew J. Kelly
SQL Server MVP
"Cathy Tumlinson" <cathyt@.tcmhmrs.org> wrote in message
news:00b301c34497$8bb9b5a0$a101280a@.phx.gbl...
> We just purchased a new server - Dell 6550, quad 2G
> processors, 6G RAM running Windows 2000 Advanced Server.
> I installed SQL 2000 Standard Edition and moved my
> databases to this new system. My problem is that now the
> sql service will continually use memory until it gets to
> about 1.7G and then it locks up the service. No one can
> login to the application that uses the db's and you can't
> access the db's via Enterprise Manager or sql Query.
> Stopping and restarting the service does not help. I have
> to actually reboot the server. I tried using the memory
> setting in the sql server properties but it doesn't help.
> Any ideas or solutions?
> Thanks for your help!
> Cathy|||I didn't catch the std edition in the original post. Std can only support
2GB of ram and you will only get 1.7GB in reality. Having 6GB on that
machine is pretty much a waste if you only have 1 instance of sql server
running. I am not convinced this is a sql server issue. Stopping and
restarting the sql server service should certainly free up any memory it had
previously taken and everything should run as normal. Not that using all
the ram should kill it in the first place. If you have to reboot then I
would suspect a server issue more than a sql one. Does the rest of the OS
behave normally when this happens? What are the cpu's and disks like when
this occurs? To get to the bottom as fast as possible you might want to
call ms pss so they can walk through this with you and they can then get a
much better feel for how everything is acting and set up.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly
SQL Server MVP
"Cathy Tumlinson" <cathyt@.tcmhmrs.org> wrote in message
news:0cc101c344a8$f0ab0480$a501280a@.phx.gbl...
> I'm running MS SQL 2000 Standard Edition. I don't have an
> AWE option.
> Cathy
> >--Original Message--
> >Do you have AWE memory setup on you server? Sometimes I
> found that AWE
> >settings cause this
> >
> >DRC
> >Alphabet collector (MCP,MCSD,MCSA,NECD ECT.)
> >
> >*** Sent via Developersdex http://www.developersdex.com
> ***
> >Don't just participate in USENET...get rewarded for it!
> >.
> >|||you might try the startup parameter -g100 (or higher)
this tells SQL Server to reserve a certain amount of
address space for memory allocations excluding the buffer
pool.
What might be happening is that the buffer pool starting
allocation memory (because so much is available) to the
point where an insufficient amount of address space is
left for other functions
the setting is in the SQL Server properties
page, "General" tab, "Startup Parameters" button
depending on the allocation needs of your particular app,
you may need a higher setting, or you could get by with a
lower setting,
>--Original Message--
>We just purchased a new server - Dell 6550, quad 2G
>processors, 6G RAM running Windows 2000 Advanced
Server.
>I installed SQL 2000 Standard Edition and moved my
>databases to this new system. My problem is that now
the
>sql service will continually use memory until it gets to
>about 1.7G and then it locks up the service. No one can
>login to the application that uses the db's and you
can't
>access the db's via Enterprise Manager or sql Query.
>Stopping and restarting the service does not help. I
have
>to actually reboot the server. I tried using the memory
>setting in the sql server properties but it doesn't help.
>Any ideas or solutions?
>Thanks for your help!
>Cathy
>.
>

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]

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

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]