Showing posts with label advanced. Show all posts
Showing posts with label advanced. Show all posts

Monday, March 12, 2012

Memory usage

Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, 3.7
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %
It has been a while since I have worked on a server that has had memory =
config set to 2GB, but if I remember correctly the servers that I worked =
on that were limited to 2GB of usage showed less (somewhere between 1.6 =
and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =
sp_configure to enable AWE. You will also want to set min and max =
server memory (MB). Try setting min/max server memory to 3GB. =20
To be honest, I don't know that you will see a large performance =
increase in going from 2GB to 3GB of RAM on a server with an 80GB =
database. Then again, it depends on how the database is used.
--=20
Keith
"Dean" <deann@.dtn.com> wrote in message =
news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =
3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =
is not
> enabled nor is the /3GB switch. The server's memory setting is =
'Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =
expect the
> memory usage to be closer to 2 GB.
>=20
> Why is it not maxing out memory up to 2 GB?
>=20
> I eventually want to enable memory greater than 2 GB. I believe all I =
need
> to do is enable AWE using sp_configure and restart the instance. Do I =
need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
>=20
> Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
>=20
>

Memory usage

Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, 3.7
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %It has been a while since I have worked on a server that has had memory =
config set to 2GB, but if I remember correctly the servers that I worked =
on that were limited to 2GB of usage showed less (somewhere between 1.6 =
and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =
sp_configure to enable AWE. You will also want to set min and max =
server memory (MB). Try setting min/max server memory to 3GB. =20
To be honest, I don't know that you will see a large performance =
increase in going from 2GB to 3GB of RAM on a server with an 80GB =
database. Then again, it depends on how the database is used.
--=20
Keith
"Dean" <deann@.dtn.com> wrote in message =
news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =
3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =
is not
> enabled nor is the /3GB switch. The server's memory setting is =
'Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =
expect the
> memory usage to be closer to 2 GB.
>=20
> Why is it not maxing out memory up to 2 GB?
>=20
> I eventually want to enable memory greater than 2 GB. I believe all I =
need
> to do is enable AWE using sp_configure and restart the instance. Do I =
need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
>=20
> Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
>=20
>

Friday, March 9, 2012

Memory usage

Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, 3.7
GB RAM. Cluster Service is running but currently there is no failover
server. Currently the Perfmon counters Target Server Memeory and Total
Server Memory are about 1682534 KB with only slight flucuations. AWE is not
enabled nor is the /3GB switch. The server's memory setting is 'Dynamically
configure SQL Server memory'. Since this is a fairly active db I expect the
memory usage to be closer to 2 GB.
Why is it not maxing out memory up to 2 GB?
I eventually want to enable memory greater than 2 GB. I believe all I need
to do is enable AWE using sp_configure and restart the instance. Do I need
the /3GB switch also? Should I set the max memory setting or leave it
dynamic? If I set the max memory setting what should I set it to?
Buffer Cache Hit Ratio - 98%+
Average Page Life 20 - 1000 secs.
CPU - 20% - 50 %It has been a while since I have worked on a server that has had memory =config set to 2GB, but if I remember correctly the servers that I worked =on that were limited to 2GB of usage showed less (somewhere between 1.6 =and 1.8GB). I think what you are seeing is normal.
You will want to add /3GB to the boot.ini. Yes, you would need to use =sp_configure to enable AWE. You will also want to set min and max =server memory (MB). Try setting min/max server memory to 3GB.
To be honest, I don't know that you will see a large performance =increase in going from 2GB to 3GB of RAM on a server with an 80GB =database. Then again, it depends on how the database is used.
-- Keith
"Dean" <deann@.dtn.com> wrote in message =news:eDKK2CGNEHA.640@.TK2MSFTNGP12.phx.gbl...
> Win2K Advanced Server , SQL2K Enterprise Edition(SP3). 80 GB database, =3.7
> GB RAM. Cluster Service is running but currently there is no failover
> server. Currently the Perfmon counters Target Server Memeory and Total
> Server Memory are about 1682534 KB with only slight flucuations. AWE =is not
> enabled nor is the /3GB switch. The server's memory setting is ='Dynamically
> configure SQL Server memory'. Since this is a fairly active db I =expect the
> memory usage to be closer to 2 GB.
> > Why is it not maxing out memory up to 2 GB?
> > I eventually want to enable memory greater than 2 GB. I believe all I =need
> to do is enable AWE using sp_configure and restart the instance. Do I =need
> the /3GB switch also? Should I set the max memory setting or leave it
> dynamic? If I set the max memory setting what should I set it to?
> > Buffer Cache Hit Ratio - 98%+
> Average Page Life 20 - 1000 secs.
> CPU - 20% - 50 %
> >

Wednesday, March 7, 2012

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
>.
>

Monday, February 20, 2012

Memory Management on cluster

I have an active/active two node cluster, each node runs Windows 2000
Advanced Server and SQL 2000 Enterprise Edition. Each node has 3.7 GB
of memory. The 3GB switch is enabled on both nodes.
When SQL Server on nodeA fails over to nodeB, will this instance only
have .7 GB of memory to use? Or can the two SQL instances share the 3
GB?<emnova@.gmail.com> wrote in message
news:1149780738.792282.241150@.j55g2000cwa.googlegroups.com...
>I have an active/active two node cluster, each node runs Windows 2000
> Advanced Server and SQL 2000 Enterprise Edition. Each node has 3.7 GB
> of memory. The 3GB switch is enabled on both nodes.
> When SQL Server on nodeA fails over to nodeB, will this instance only
> have .7 GB of memory to use? Or can the two SQL instances share the 3
> GB?
>
SQL Server will yield memory when the system is under memory pressrure.
However the process is slow, and will be painful in case of a failover. If
you really want to guarantee good performance on failover, you should add
memory or trim the max memory size of each virtual server.
David|||<emnova@.gmail.com> wrote in message
news:1149780738.792282.241150@.j55g2000cwa.googlegroups.com...
> I have an active/active two node cluster, each node runs Windows 2000
> Advanced Server and SQL 2000 Enterprise Edition. Each node has 3.7 GB
> of memory. The 3GB switch is enabled on both nodes.
> When SQL Server on nodeA fails over to nodeB, will this instance only
> have .7 GB of memory to use? Or can the two SQL instances share the 3
> GB?
They're share it (I'm assuming you don't have PAE enabled also, which you
shouldn't in this case.)
I'd probably test this though and see if I could limit say nodeB to 1.5 gig
and see what that does to performance.
Ideally, if you can, upgrade the RAM in both machines.
>

Memory management

Hi,
I have a MS Sql server 7.0 running on Windows 2000 advanced server with 6GB
ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
ram. But the sql server memory management tab shows false values (16MB and
0 values), and the sliders are disabled. Why is it? How can I check memory
usage for the sql server?
Thank you,
Chris
Message posted via http://www.sqlmonster.com
Hi
Run sp_configure 'max server memory' to see what is configured.
If you use SQL Server Standard Edition, all what it can use is 2GB as that
is an Edition limitation.
SQL Server Enterprise edition, IIRC is 8GB.
Regards
Mike
"Mary Poppins via SQLMonster.com" wrote:

> Hi,
> I have a MS Sql server 7.0 running on Windows 2000 advanced server with 6GB
> ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
> ram. But the sql server memory management tab shows false values (16MB and
> 0 values), and the sliders are disabled. Why is it? How can I check memory
> usage for the sql server?
> Thank you,
> Chris
> --
> Message posted via http://www.sqlmonster.com
>
|||Do you have AWE enabled? If so then sql server does not dynamically manage
memory. It will grab all of what if there unless you set the max memory
setting to something less than the total available. In your case I recommend
around 5GB. You can use the Sql Memory counters in perfmon to see how much
it is actually using. Total memory and Target memory should be the same and
what ever you set your max memory setting to. Make sure you don't have the
Use Fixed Amount checked as that will disable the sliders.
Andrew J. Kelly SQL MVP
"Mary Poppins via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:6ea9fff4366143f8b44320e5b0092e94@.SQLMonster.c om...
> Hi,
> I have a MS Sql server 7.0 running on Windows 2000 advanced server with
> 6GB
> ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
> ram. But the sql server memory management tab shows false values (16MB and
> 0 values), and the sliders are disabled. Why is it? How can I check memory
> usage for the sql server?
> Thank you,
> Chris
> --
> Message posted via http://www.sqlmonster.com
|||AWE not enabled . (The extended memory option in SQL Server 7.0 is not
available on Windows 2000 Advanced Server). Sp_configure shows that the
min, max and the run server memories are 2147483647. In the server
properties memory tab the "Use fixed memory size" are checked, and I can
not change it, and it shows only min 16MB and max 0MB. However the in the
performance monitor the Target server memory shows 2082896KB, and the Total
server memory 144150 KB.
Can I ignore the memory panel, or could you advise something to correct the
wrong values?
Thank you,
Chris
Message posted via http://www.sqlmonster.com
|||Ignore the memory panel. The important thing is the sp_configure setting. The memory dialog is
probably just some kind of UI bug.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mary Poppins via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:0b5fc3940c614ef79498116929c69874@.SQLMonster.c om...
> AWE not enabled . (The extended memory option in SQL Server 7.0 is not
> available on Windows 2000 Advanced Server). Sp_configure shows that the
> min, max and the run server memories are 2147483647. In the server
> properties memory tab the "Use fixed memory size" are checked, and I can
> not change it, and it shows only min 16MB and max 0MB. However the in the
> performance monitor the Target server memory shows 2082896KB, and the Total
> server memory 144150 KB.
> Can I ignore the memory panel, or could you advise something to correct the
> wrong values?
> Thank you,
> Chris
> --
> Message posted via http://www.sqlmonster.com
|||OK. Thank you.
Bye
Message posted via http://www.sqlmonster.com

Memory management

Hi,
I have a MS Sql server 7.0 running on Windows 2000 advanced server with 6GB
ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
ram. But the sql server memory management tab shows false values (16MB and
0 values), and the sliders are disabled. Why is it? How can I check memory
usage for the sql server?
Thank you,
Chris
Message posted via http://www.droptable.comHi
Run sp_configure 'max server memory' to see what is configured.
If you use SQL Server Standard Edition, all what it can use is 2GB as that
is an Edition limitation.
SQL Server Enterprise edition, IIRC is 8GB.
Regards
Mike
"Mary Poppins via droptable.com" wrote:

> Hi,
> I have a MS Sql server 7.0 running on Windows 2000 advanced server with 6G
B
> ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
> ram. But the sql server memory management tab shows false values (16MB and
> 0 values), and the sliders are disabled. Why is it? How can I check memory
> usage for the sql server?
> Thank you,
> Chris
> --
> Message posted via http://www.droptable.com
>|||Do you have AWE enabled? If so then sql server does not dynamically manage
memory. It will grab all of what if there unless you set the max memory
setting to something less than the total available. In your case I recommend
around 5GB. You can use the Sql Memory counters in perfmon to see how much
it is actually using. Total memory and Target memory should be the same and
what ever you set your max memory setting to. Make sure you don't have the
Use Fixed Amount checked as that will disable the sliders.
Andrew J. Kelly SQL MVP
"Mary Poppins via droptable.com" <forum@.droptable.com> wrote in message
news:6ea9fff4366143f8b44320e5b0092e94@.SQ
droptable.com...
> Hi,
> I have a MS Sql server 7.0 running on Windows 2000 advanced server with
> 6GB
> ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
> ram. But the sql server memory management tab shows false values (16MB and
> 0 values), and the sliders are disabled. Why is it? How can I check memory
> usage for the sql server?
> Thank you,
> Chris
> --
> Message posted via http://www.droptable.com|||AWE not enabled . (The extended memory option in SQL Server 7.0 is not
available on Windows 2000 Advanced Server). Sp_configure shows that the
min, max and the run server memories are 2147483647. In the server
properties memory tab the "Use fixed memory size" are checked, and I can
not change it, and it shows only min 16MB and max 0MB. However the in the
performance monitor the Target server memory shows 2082896KB, and the Total
server memory 144150 KB.
Can I ignore the memory panel, or could you advise something to correct the
wrong values?
Thank you,
Chris
Message posted via http://www.droptable.com|||Ignore the memory panel. The important thing is the sp_configure setting. Th
e memory dialog is
probably just some kind of UI bug.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mary Poppins via droptable.com" <forum@.droptable.com> wrote in message
news:0b5fc3940c614ef79498116929c69874@.SQ
droptable.com...
> AWE not enabled . (The extended memory option in SQL Server 7.0 is not
> available on Windows 2000 Advanced Server). Sp_configure shows that the
> min, max and the run server memories are 2147483647. In the server
> properties memory tab the "Use fixed memory size" are checked, and I can
> not change it, and it shows only min 16MB and max 0MB. However the in the
> performance monitor the Target server memory shows 2082896KB, and the Tota
l
> server memory 144150 KB.
> Can I ignore the memory panel, or could you advise something to correct th
e
> wrong values?
> Thank you,
> Chris
> --
> Message posted via http://www.droptable.com|||OK. Thank you.
Bye
Message posted via http://www.droptable.com

Memory management

Hi,
I have a MS Sql server 7.0 running on Windows 2000 advanced server with 6GB
ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
ram. But the sql server memory management tab shows false values (16MB and
0 values), and the sliders are disabled. Why is it? How can I check memory
usage for the sql server?
Thank you,
Chris
--
Message posted via http://www.sqlmonster.comHi
Run sp_configure 'max server memory' to see what is configured.
If you use SQL Server Standard Edition, all what it can use is 2GB as that
is an Edition limitation.
SQL Server Enterprise edition, IIRC is 8GB.
Regards
Mike
"Mary Poppins via SQLMonster.com" wrote:
> Hi,
> I have a MS Sql server 7.0 running on Windows 2000 advanced server with 6GB
> ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
> ram. But the sql server memory management tab shows false values (16MB and
> 0 values), and the sliders are disabled. Why is it? How can I check memory
> usage for the sql server?
> Thank you,
> Chris
> --
> Message posted via http://www.sqlmonster.com
>|||Do you have AWE enabled? If so then sql server does not dynamically manage
memory. It will grab all of what if there unless you set the max memory
setting to something less than the total available. In your case I recommend
around 5GB. You can use the Sql Memory counters in perfmon to see how much
it is actually using. Total memory and Target memory should be the same and
what ever you set your max memory setting to. Make sure you don't have the
Use Fixed Amount checked as that will disable the sliders.
--
Andrew J. Kelly SQL MVP
"Mary Poppins via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:6ea9fff4366143f8b44320e5b0092e94@.SQLMonster.com...
> Hi,
> I have a MS Sql server 7.0 running on Windows 2000 advanced server with
> 6GB
> ram. The boot.ini contains the /3gb /pae options. The OS sees all of the
> ram. But the sql server memory management tab shows false values (16MB and
> 0 values), and the sliders are disabled. Why is it? How can I check memory
> usage for the sql server?
> Thank you,
> Chris
> --
> Message posted via http://www.sqlmonster.com|||AWE not enabled . (The extended memory option in SQL Server 7.0 is not
available on Windows 2000 Advanced Server). Sp_configure shows that the
min, max and the run server memories are 2147483647. In the server
properties memory tab the "Use fixed memory size" are checked, and I can
not change it, and it shows only min 16MB and max 0MB. However the in the
performance monitor the Target server memory shows 2082896KB, and the Total
server memory 144150 KB.
Can I ignore the memory panel, or could you advise something to correct the
wrong values?
Thank you,
Chris
--
Message posted via http://www.sqlmonster.com|||Ignore the memory panel. The important thing is the sp_configure setting. The memory dialog is
probably just some kind of UI bug.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mary Poppins via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:0b5fc3940c614ef79498116929c69874@.SQLMonster.com...
> AWE not enabled . (The extended memory option in SQL Server 7.0 is not
> available on Windows 2000 Advanced Server). Sp_configure shows that the
> min, max and the run server memories are 2147483647. In the server
> properties memory tab the "Use fixed memory size" are checked, and I can
> not change it, and it shows only min 16MB and max 0MB. However the in the
> performance monitor the Target server memory shows 2082896KB, and the Total
> server memory 144150 KB.
> Can I ignore the memory panel, or could you advise something to correct the
> wrong values?
> Thank you,
> Chris
> --
> Message posted via http://www.sqlmonster.com|||OK. Thank you.
Bye
--
Message posted via http://www.sqlmonster.com