MEM usage continue to increase

When start SQL Server the MEM usage continue to increase
even when activity is low. How do I solve this problem?
The physical memory is 2 GB and after a few hours the
usage goes to 1.8 GB causing not able the connect with
ODBC error in the front end MSACCESS db.If you wish to limit the amount of memory that SQL Server uses, run SQL
Enterprise Manager , right click your server and go to the memory tab...
There will be a slider where you can set the maximum memory SQL will use..
Be aware that SQL will NOT release the memory unless there is memory
pressure. This is the way SQL is designed to work. It prevents SQL Server
from wasting resources releasing memory when there is no need to do so.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"norbert" <anonymous@.discussions.microsoft.com> wrote in message
news:269b401c4635a$93ffae30$a601280a@.phx
.gbl...
> When start SQL Server the MEM usage continue to increase
> even when activity is low. How do I solve this problem?
> The physical memory is 2 GB and after a few hours the
> usage goes to 1.8 GB causing not able the connect with
> ODBC error in the front end MSACCESS db.
>|||Have a look at
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"norbert" <anonymous@.discussions.microsoft.com> wrote in message
news:269b401c4635a$93ffae30$a601280a@.phx
.gbl...
> When start SQL Server the MEM usage continue to increase
> even when activity is low. How do I solve this problem?
> The physical memory is 2 GB and after a few hours the
> usage goes to 1.8 GB causing not able the connect with
> ODBC error in the front end MSACCESS db.
>

MEM usage continue to increase

When start SQL Server the MEM usage continue to increase
even when activity is low. How do I solve this problem?
The physical memory is 2 GB and after a few hours the
usage goes to 1.8 GB causing not able the connect with
ODBC error in the front end MSACCESS db.
If you wish to limit the amount of memory that SQL Server uses, run SQL
Enterprise Manager , right click your server and go to the memory tab...
There will be a slider where you can set the maximum memory SQL will use..
Be aware that SQL will NOT release the memory unless there is memory
pressure. This is the way SQL is designed to work. It prevents SQL Server
from wasting resources releasing memory when there is no need to do so.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"norbert" <anonymous@.discussions.microsoft.com> wrote in message
news:269b401c4635a$93ffae30$a601280a@.phx.gbl...
> When start SQL Server the MEM usage continue to increase
> even when activity is low. How do I solve this problem?
> The physical memory is 2 GB and after a few hours the
> usage goes to 1.8 GB causing not able the connect with
> ODBC error in the front end MSACCESS db.
>
|||Have a look at
INF: SQL Server Memory Usage
http://support.microsoft.com/default...;en-us;q321363
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"norbert" <anonymous@.discussions.microsoft.com> wrote in message
news:269b401c4635a$93ffae30$a601280a@.phx.gbl...
> When start SQL Server the MEM usage continue to increase
> even when activity is low. How do I solve this problem?
> The physical memory is 2 GB and after a few hours the
> usage goes to 1.8 GB causing not able the connect with
> ODBC error in the front end MSACCESS db.
>

MEM usage continue to increase

When start SQL Server the MEM usage continue to increase
even when activity is low. How do I solve this problem?
The physical memory is 2 GB and after a few hours the
usage goes to 1.8 GB causing not able the connect with
ODBC error in the front end MSACCESS db.If you wish to limit the amount of memory that SQL Server uses, run SQL
Enterprise Manager , right click your server and go to the memory tab...
There will be a slider where you can set the maximum memory SQL will use..
Be aware that SQL will NOT release the memory unless there is memory
pressure. This is the way SQL is designed to work. It prevents SQL Server
from wasting resources releasing memory when there is no need to do so.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"norbert" <anonymous@.discussions.microsoft.com> wrote in message
news:269b401c4635a$93ffae30$a601280a@.phx.gbl...
> When start SQL Server the MEM usage continue to increase
> even when activity is low. How do I solve this problem?
> The physical memory is 2 GB and after a few hours the
> usage goes to 1.8 GB causing not able the connect with
> ODBC error in the front end MSACCESS db.
>|||Have a look at
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"norbert" <anonymous@.discussions.microsoft.com> wrote in message
news:269b401c4635a$93ffae30$a601280a@.phx.gbl...
> When start SQL Server the MEM usage continue to increase
> even when activity is low. How do I solve this problem?
> The physical memory is 2 GB and after a few hours the
> usage goes to 1.8 GB causing not able the connect with
> ODBC error in the front end MSACCESS db.
>

Mem to Leave...

Are there any tools or documentation available anywhere that describes how
one can monitor the usage/fragmentation of the mem to leave area used by SQL
Server? (SQL2K on W2K3 2 Node Cluster)One tool is VMStat. You can download it with the psslabs2004
download. You can download it from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=aec18337-887f-4ec6-a858-81f84de8082f&DisplayLang=en
-Sue
On Mon, 23 Jan 2006 12:25:02 -0800, "Cyberstorme"
<Cyberstorme@.discussions.microsoft.com> wrote:
>Are there any tools or documentation available anywhere that describes how
>one can monitor the usage/fragmentation of the mem to leave area used by SQL
>Server? (SQL2K on W2K3 2 Node Cluster)sql

Mem to Leave...

Are there any tools or documentation available anywhere that describes how
one can monitor the usage/fragmentation of the mem to leave area used by SQL
Server? (SQL2K on W2K3 2 Node Cluster)
One tool is VMStat. You can download it with the psslabs2004
download. You can download it from:
http://www.microsoft.com/downloads/d...DisplayLang=en
-Sue
On Mon, 23 Jan 2006 12:25:02 -0800, "Cyberstorme"
<Cyberstorme@.discussions.microsoft.com> wrote:

>Are there any tools or documentation available anywhere that describes how
>one can monitor the usage/fragmentation of the mem to leave area used by SQL
>Server? (SQL2K on W2K3 2 Node Cluster)

Mem to Leave...

Are there any tools or documentation available anywhere that describes how
one can monitor the usage/fragmentation of the mem to leave area used by SQL
Server? (SQL2K on W2K3 2 Node Cluster)One tool is VMStat. You can download it with the psslabs2004
download. You can download it from:
1f84de8082f&DisplayLang=en" target="_blank">http://www.microsoft.com/downloads/...&DisplayLang=en
-Sue
On Mon, 23 Jan 2006 12:25:02 -0800, "Cyberstorme"
<Cyberstorme@.discussions.microsoft.com> wrote:

>Are there any tools or documentation available anywhere that describes how
>one can monitor the usage/fragmentation of the mem to leave area used by SQ
L
>Server? (SQL2K on W2K3 2 Node Cluster)

Mem configuration dilema

Hi
Our main server has 1280 MB of mem and is a SBS2003 DC , a file server and a
SQL server ( and also will be Exchange2003 server very soon).
I have configured SQL server with the option of "Dynamically configure SQL
Server memory" with minimum=0 and maximum=800 MB of RAM.
With this setting SQL is taking 700MB of mem and all of the other processes
a total of more then 400 MB and for available mem it remains only 100MB.
I would want to limit SQL to only 400-500MB but I'm afraid I'm gonna hit in
the SQL performance - and the heavy work is on the databases.
How would you configure the usage of mem on this server is the question. (
also : which is best - to dynamically configure SQL mem with a limit or use
a fixed mem size ? , and what does running values ?)
In the future a mem upgrade will happen, but for now I will have to manage
with this situation
Thanks to any ideasSo you have 1 server acting 4 roles
SQL
File Server
DC
Exchange Server
1 Server may not be enough depending on load which is the deciding factor
here.
5 Users using a server such as this will probably work fine but probably not
100. You have not enlightened us with the load expected upon it so it will
be difficult to answer.
You may also run into other bottlenecks as follows.
Network Bandwidth
Disk IO
CPU
Have you consider these other factors?
Nik Marshall-Blank MCSD/MCDBA
"Fatboyslimro" <fatboyslimro@.hotmail.com> wrote in message
news:u5tIanduFHA.992@.TK2MSFTNGP12.phx.gbl...
> Hi
> Our main server has 1280 MB of mem and is a SBS2003 DC , a file server and
> a
> SQL server ( and also will be Exchange2003 server very soon).
> I have configured SQL server with the option of "Dynamically configure SQL
> Server memory" with minimum=0 and maximum=800 MB of RAM.
> With this setting SQL is taking 700MB of mem and all of the other
> processes
> a total of more then 400 MB and for available mem it remains only 100MB.
> I would want to limit SQL to only 400-500MB but I'm afraid I'm gonna hit
> in
> the SQL performance - and the heavy work is on the databases.
> How would you configure the usage of mem on this server is the question. (
> also : which is best - to dynamically configure SQL mem with a limit or
> use
> a fixed mem size ? , and what does running values ?)
>
> In the future a mem upgrade will happen, but for now I will have to manage
> with this situation
> Thanks to any ideas
>|||You can try adjusting "max server memory" up-and-down while the server is
running, and note the effect on your performance. You don't have to restarat
the server.

Mem configuration dilema

Hi
Our main server has 1280 MB of mem and is a SBS2003 DC , a file server and a
SQL server ( and also will be Exchange2003 server very soon).
I have configured SQL server with the option of "Dynamically configure SQL
Server memory" with minimum=0 and maximum=800 MB of RAM.
With this setting SQL is taking 700MB of mem and all of the other processes
a total of more then 400 MB and for available mem it remains only 100MB.
I would want to limit SQL to only 400-500MB but I'm afraid I'm gonna hit in
the SQL performance - and the heavy work is on the databases.
How would you configure the usage of mem on this server is the question. (
also : which is best - to dynamically configure SQL mem with a limit or use
a fixed mem size ? , and what does running values ?)
In the future a mem upgrade will happen, but for now I will have to manage
with this situation
Thanks to any ideasSo you have 1 server acting 4 roles
SQL
File Server
DC
Exchange Server
1 Server may not be enough depending on load which is the deciding factor
here.
5 Users using a server such as this will probably work fine but probably not
100. You have not enlightened us with the load expected upon it so it will
be difficult to answer.
You may also run into other bottlenecks as follows.
Network Bandwidth
Disk IO
CPU
Have you consider these other factors?
--
Nik Marshall-Blank MCSD/MCDBA
"Fatboyslimro" <fatboyslimro@.hotmail.com> wrote in message
news:u5tIanduFHA.992@.TK2MSFTNGP12.phx.gbl...
> Hi
> Our main server has 1280 MB of mem and is a SBS2003 DC , a file server and
> a
> SQL server ( and also will be Exchange2003 server very soon).
> I have configured SQL server with the option of "Dynamically configure SQL
> Server memory" with minimum=0 and maximum=800 MB of RAM.
> With this setting SQL is taking 700MB of mem and all of the other
> processes
> a total of more then 400 MB and for available mem it remains only 100MB.
> I would want to limit SQL to only 400-500MB but I'm afraid I'm gonna hit
> in
> the SQL performance - and the heavy work is on the databases.
> How would you configure the usage of mem on this server is the question. (
> also : which is best - to dynamically configure SQL mem with a limit or
> use
> a fixed mem size ? , and what does running values ?)
>
> In the future a mem upgrade will happen, but for now I will have to manage
> with this situation
> Thanks to any ideas
>|||You can try adjusting "max server memory" up-and-down while the server is
running, and note the effect on your performance. You don't have to restarat
the server.

Mem configuration dilema

Hi
Our main server has 1280 MB of mem and is a SBS2003 DC , a file server and a
SQL server ( and also will be Exchange2003 server very soon).
I have configured SQL server with the option of "Dynamically configure SQL
Server memory" with minimum=0 and maximum=800 MB of RAM.
With this setting SQL is taking 700MB of mem and all of the other processes
a total of more then 400 MB and for available mem it remains only 100MB.
I would want to limit SQL to only 400-500MB but I'm afraid I'm gonna hit in
the SQL performance - and the heavy work is on the databases.
How would you configure the usage of mem on this server is the question. (
also : which is best - to dynamically configure SQL mem with a limit or use
a fixed mem size ? , and what does running values ?)
In the future a mem upgrade will happen, but for now I will have to manage
with this situation
Thanks to any ideas
So you have 1 server acting 4 roles
SQL
File Server
DC
Exchange Server
1 Server may not be enough depending on load which is the deciding factor
here.
5 Users using a server such as this will probably work fine but probably not
100. You have not enlightened us with the load expected upon it so it will
be difficult to answer.
You may also run into other bottlenecks as follows.
Network Bandwidth
Disk IO
CPU
Have you consider these other factors?
Nik Marshall-Blank MCSD/MCDBA
"Fatboyslimro" <fatboyslimro@.hotmail.com> wrote in message
news:u5tIanduFHA.992@.TK2MSFTNGP12.phx.gbl...
> Hi
> Our main server has 1280 MB of mem and is a SBS2003 DC , a file server and
> a
> SQL server ( and also will be Exchange2003 server very soon).
> I have configured SQL server with the option of "Dynamically configure SQL
> Server memory" with minimum=0 and maximum=800 MB of RAM.
> With this setting SQL is taking 700MB of mem and all of the other
> processes
> a total of more then 400 MB and for available mem it remains only 100MB.
> I would want to limit SQL to only 400-500MB but I'm afraid I'm gonna hit
> in
> the SQL performance - and the heavy work is on the databases.
> How would you configure the usage of mem on this server is the question. (
> also : which is best - to dynamically configure SQL mem with a limit or
> use
> a fixed mem size ? , and what does running values ?)
>
> In the future a mem upgrade will happen, but for now I will have to manage
> with this situation
> Thanks to any ideas
>
|||You can try adjusting "max server memory" up-and-down while the server is
running, and note the effect on your performance. You don't have to restarat
the server.
sql