Monday, March 12, 2012
Memory Usage Exceeded Maximum Memory Configuration
I'm running SQL Server 2000 on an NT Workstation with 1GB
of memory. I've configured the maximum memory of the SQL
Server to be 512MB, but when I check Task Manager it shows
the Memory Usage of sqlservr.exe to be more than 512MB.
(Currently at 560MB). Is it normal that sqlservr.exe will
use more than the maximum allowed?
Thanks in advance,
Alice
SQL Server Version I'm running:
Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
Nov 19 2001 13:23:50
Copyright (c) 1988-2000 Microsoft Corporation
Personal Edition on Windows NT 4.0 (Build 1381:
Service Pack 6)
Maximum memory is for Physical Memory.
Task manager shows all, physical and virtual memory.
"Alice" wrote:
> Hi,
> I'm running SQL Server 2000 on an NT Workstation with 1GB
> of memory. I've configured the maximum memory of the SQL
> Server to be 512MB, but when I check Task Manager it shows
> the Memory Usage of sqlservr.exe to be more than 512MB.
> (Currently at 560MB). Is it normal that sqlservr.exe will
> use more than the maximum allowed?
> Thanks in advance,
> Alice
> SQL Server Version I'm running:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> Copyright (c) 1988-2000 Microsoft Corporation
> Personal Edition on Windows NT 4.0 (Build 1381:
> Service Pack 6)
>
>
>
>
|||The Max setting is for the memory pool only. There is an area called
MemtoLeave (by default up to 256MB) that is not part of that setting so it
is possible for SQL Server to use more than the Max under certain
conditions.
Andrew J. Kelly SQL MVP
"Alice" <achan@.icescape.com> wrote in message
news:278f601c46392$73dd3b30$a401280a@.phx.gbl...
> Hi,
> I'm running SQL Server 2000 on an NT Workstation with 1GB
> of memory. I've configured the maximum memory of the SQL
> Server to be 512MB, but when I check Task Manager it shows
> the Memory Usage of sqlservr.exe to be more than 512MB.
> (Currently at 560MB). Is it normal that sqlservr.exe will
> use more than the maximum allowed?
> Thanks in advance,
> Alice
> SQL Server Version I'm running:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> Copyright (c) 1988-2000 Microsoft Corporation
> Personal Edition on Windows NT 4.0 (Build 1381:
> Service Pack 6)
>
>
>
>
Memory Usage Exceeded Maximum Memory Configuration
I'm running SQL Server 2000 on an NT Workstation with 1GB
of memory. I've configured the maximum memory of the SQL
Server to be 512MB, but when I check Task Manager it shows
the Memory Usage of sqlservr.exe to be more than 512MB.
(Currently at 560MB). Is it normal that sqlservr.exe will
use more than the maximum allowed?
Thanks in advance,
Alice
SQL Server Version I'm running:
Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
Nov 19 2001 13:23:50
Copyright (c) 1988-2000 Microsoft Corporation
Personal Edition on Windows NT 4.0 (Build 1381:
Service Pack 6)Maximum memory is for Physical Memory.
Task manager shows all, physical and virtual memory.
"Alice" wrote:
> Hi,
> I'm running SQL Server 2000 on an NT Workstation with 1GB
> of memory. I've configured the maximum memory of the SQL
> Server to be 512MB, but when I check Task Manager it shows
> the Memory Usage of sqlservr.exe to be more than 512MB.
> (Currently at 560MB). Is it normal that sqlservr.exe will
> use more than the maximum allowed?
> Thanks in advance,
> Alice
> SQL Server Version I'm running:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> Copyright (c) 1988-2000 Microsoft Corporation
> Personal Edition on Windows NT 4.0 (Build 1381:
> Service Pack 6)
>
>
>
>|||The Max setting is for the memory pool only. There is an area called
MemtoLeave (by default up to 256MB) that is not part of that setting so it
is possible for SQL Server to use more than the Max under certain
conditions.
Andrew J. Kelly SQL MVP
"Alice" <achan@.icescape.com> wrote in message
news:278f601c46392$73dd3b30$a401280a@.phx
.gbl...
> Hi,
> I'm running SQL Server 2000 on an NT Workstation with 1GB
> of memory. I've configured the maximum memory of the SQL
> Server to be 512MB, but when I check Task Manager it shows
> the Memory Usage of sqlservr.exe to be more than 512MB.
> (Currently at 560MB). Is it normal that sqlservr.exe will
> use more than the maximum allowed?
> Thanks in advance,
> Alice
> SQL Server Version I'm running:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> Copyright (c) 1988-2000 Microsoft Corporation
> Personal Edition on Windows NT 4.0 (Build 1381:
> Service Pack 6)
>
>
>
>
Memory Usage Exceeded Maximum Memory Configuration
I'm running SQL Server 2000 on an NT Workstation with 1GB
of memory. I've configured the maximum memory of the SQL
Server to be 512MB, but when I check Task Manager it shows
the Memory Usage of sqlservr.exe to be more than 512MB.
(Currently at 560MB). Is it normal that sqlservr.exe will
use more than the maximum allowed?
Thanks in advance,
Alice
SQL Server Version I'm running:
Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
Nov 19 2001 13:23:50
Copyright (c) 1988-2000 Microsoft Corporation
Personal Edition on Windows NT 4.0 (Build 1381:
Service Pack 6)Maximum memory is for Physical Memory.
Task manager shows all, physical and virtual memory.
"Alice" wrote:
> Hi,
> I'm running SQL Server 2000 on an NT Workstation with 1GB
> of memory. I've configured the maximum memory of the SQL
> Server to be 512MB, but when I check Task Manager it shows
> the Memory Usage of sqlservr.exe to be more than 512MB.
> (Currently at 560MB). Is it normal that sqlservr.exe will
> use more than the maximum allowed?
> Thanks in advance,
> Alice
> SQL Server Version I'm running:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> Copyright (c) 1988-2000 Microsoft Corporation
> Personal Edition on Windows NT 4.0 (Build 1381:
> Service Pack 6)
>
>
>
>|||The Max setting is for the memory pool only. There is an area called
MemtoLeave (by default up to 256MB) that is not part of that setting so it
is possible for SQL Server to use more than the Max under certain
conditions.
--
Andrew J. Kelly SQL MVP
"Alice" <achan@.icescape.com> wrote in message
news:278f601c46392$73dd3b30$a401280a@.phx.gbl...
> Hi,
> I'm running SQL Server 2000 on an NT Workstation with 1GB
> of memory. I've configured the maximum memory of the SQL
> Server to be 512MB, but when I check Task Manager it shows
> the Memory Usage of sqlservr.exe to be more than 512MB.
> (Currently at 560MB). Is it normal that sqlservr.exe will
> use more than the maximum allowed?
> Thanks in advance,
> Alice
> SQL Server Version I'm running:
> Microsoft SQL Server 2000 - 8.00.534 (Intel X86)
> Nov 19 2001 13:23:50
> Copyright (c) 1988-2000 Microsoft Corporation
> Personal Edition on Windows NT 4.0 (Build 1381:
> Service Pack 6)
>
>
>
>
Friday, March 9, 2012
Memory Usage
maximum of 2GM of memory because of the limitation
imposed by Win2K Server. If I have 4GB of memory in my
Win2K Server, does this mean that only 2GB is actually
being used or is the 4GB used?
Thanks
EmmaIn article <b12801c3ecc7$89fb2310$a101280a@.phx.gbl>, eeemore@.hotmail.com
said...
> I read somewhere that SQL Server, SE only supports a
> maximum of 2GM of memory because of the limitation
> imposed by Win2K Server. If I have 4GB of memory in my
> Win2K Server, does this mean that only 2GB is actually
> being used or is the 4GB used?
I have 4GB in my server and it only actually uses 1.7GB and believe me, on
my server it would be using more if it could.
Friday, February 24, 2012
memory on 2005
maximum set in the Management Studio. DOes it ever release and free up
the memory. For example, thought the day SQL needs more memory and at
the end of the day has 1 gig RAM used - if everyone logs out of our
application so nothing is hitting SQL, will the memory be released? If
not, why not?
Darin
*** Sent via Developersdex http://www.developersdex.com ***> For example, thought the day SQL needs more memory and at
> the end of the day has 1 gig RAM used - if everyone logs out of our
> application so nothing is hitting SQL, will the memory be released? If
> not, why not?
No, not because people "logs out". Because reading pages from disk and creating execution plans are
expensive operations. This is why SQL Server caches plans and pages. How would SQL Server know when
to release something? SQL Server will release memory when the OS becomes pressured for memory, but
not until then. You can set a cap on memory, of course (sp_configure and max server memory).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Darin" <darin_nospam@.nospamever> wrote in message news:u7f%23mEmiHHA.1624@.TK2MSFTNGP06.phx.gbl...
> Running SQL 2005 SP2, the memory (RAM) that SQL is using can have a
> maximum set in the Management Studio. DOes it ever release and free up
> the memory. For example, thought the day SQL needs more memory and at
> the end of the day has 1 gig RAM used - if everyone logs out of our
> application so nothing is hitting SQL, will the memory be released? If
> not, why not?
> Darin
> *** Sent via Developersdex http://www.developersdex.com ***|||SQL Server won't release memory unless it detects memory pressure. The bulk
of SQL memory is used for buffer cache, which is needed to reduce I/O and
improve performance. Even if everyone logs out now, cached data is still
valid and can be used again later for subsequent requests.
If you have other memory-intensive applications running on a box with
limited memory resources, you can set SQL Server max memory to prevent
thrashing.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Darin" <darin_nospam@.nospamever> wrote in message
news:u7f%23mEmiHHA.1624@.TK2MSFTNGP06.phx.gbl...
> Running SQL 2005 SP2, the memory (RAM) that SQL is using can have a
> maximum set in the Management Studio. DOes it ever release and free up
> the memory. For example, thought the day SQL needs more memory and at
> the end of the day has 1 gig RAM used - if everyone logs out of our
> application so nothing is hitting SQL, will the memory be released? If
> not, why not?
> Darin
> *** Sent via Developersdex http://www.developersdex.com ***|||If the OS doesn't signal that it needs more memory for some other process or
sql server doesn't interally determine that some other sql server
functionality needs more memory, whatever RAM is acquired for the various
buffers will simply stay there indefinitely.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OLJOsWmiHHA.688@.TK2MSFTNGP03.phx.gbl...
>> For example, thought the day SQL needs more memory and at
>> the end of the day has 1 gig RAM used - if everyone logs out of our
>> application so nothing is hitting SQL, will the memory be released? If
>> not, why not?
> No, not because people "logs out". Because reading pages from disk and
> creating execution plans are expensive operations. This is why SQL Server
> caches plans and pages. How would SQL Server know when to release
> something? SQL Server will release memory when the OS becomes pressured
> for memory, but not until then. You can set a cap on memory, of course
> (sp_configure and max server memory).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Darin" <darin_nospam@.nospamever> wrote in message
> news:u7f%23mEmiHHA.1624@.TK2MSFTNGP06.phx.gbl...
>> Running SQL 2005 SP2, the memory (RAM) that SQL is using can have a
>> maximum set in the Management Studio. DOes it ever release and free up
>> the memory. For example, thought the day SQL needs more memory and at
>> the end of the day has 1 gig RAM used - if everyone logs out of our
>> application so nothing is hitting SQL, will the memory be released? If
>> not, why not?
>> Darin
>> *** Sent via Developersdex http://www.developersdex.com ***
>
Monday, February 20, 2012
memory management
Hi all,
I'm probably missing something here but I need to know why AS2005 is not using the maximum memory available on our production server.
I have a 3.5 GB cube on our server and the process msmdsrv.exe is only using around 100 mb currently. When multiple users are hitting the server at the same time, msmdsrv.exe goes up to around 650 mb but will eventually return to 100mb.
There is actually 4 GB of memory available on the server, is there any way to maximize the memory used by AS2005 on this box and cach almost the whole cube ? AS2005 is the only thing running on this server.
Currently, we see a lot of disk access when users are querying the cubes.
Thanks,
By default Analysis Server allowed to use 80% of the physical memory avaliable on your machine. This controlled by TotalMemoryLimit server property ( set to 80).
For your users to see improved query performance you need to try and define aggregations. See this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348980&SiteID=1 for discussion about cube performance.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
This is the reason why I'm asking this question...
If I have 3 GB of memory and AS2005 is allowed to use 80% of it... I would expect AS to be using around 2.4 GB of memory.
In our environment it is using 100 mb when idle and 650 mb when multiple users are querying the cubes...
This is what I need to understand.
BTW i really think that our aggregations are defined properly
Thanks,
Eric
|||Analysis Server will go to the disk and will try to retrieve results if it cannot find any answers in a cache already. Analysis Server will always cache results from queries. But whether new query can be answered from the cache very much depends on several facts:
1. Queries are similar to the previous queries.
2. Calculation involved in a queries do not require going to the lowest level of granularity.
3. Attribute relationships defined correctly and new query can benefit from not exactly matching cache. ( for example you get answers from Months cache if you asked for Years )
You ultimate goal is not increase Analysis Server's memory footprint, but make your caches more effcient.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm having the same problem. When querying the OLAP by using ProClarity or SSMS (Management Studio), the response time is very low the CPU Utilization is below 10% and Memory Usage not more than 50%. When I check in the performance monitor, the I/O access is very high continuously 100% utilization when I are running query from ProClarity Analytics Server. Is there anything I can do to reduce I/O disk time ?
Thanks in advance.
memory management
Hi all,
I'm probably missing something here but I need to know why AS2005 is not using the maximum memory available on our production server.
I have a 3.5 GB cube on our server and the process msmdsrv.exe is only using around 100 mb currently. When multiple users are hitting the server at the same time, msmdsrv.exe goes up to around 650 mb but will eventually return to 100mb.
There is actually 4 GB of memory available on the server, is there any way to maximize the memory used by AS2005 on this box and cach almost the whole cube ? AS2005 is the only thing running on this server.
Currently, we see a lot of disk access when users are querying the cubes.
Thanks,
By default Analysis Server allowed to use 80% of the physical memory avaliable on your machine. This controlled by TotalMemoryLimit server property ( set to 80).
For your users to see improved query performance you need to try and define aggregations. See this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348980&SiteID=1 for discussion about cube performance.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
|||
This is the reason why I'm asking this question...
If I have 3 GB of memory and AS2005 is allowed to use 80% of it... I would expect AS to be using around 2.4 GB of memory.
In our environment it is using 100 mb when idle and 650 mb when multiple users are querying the cubes...
This is what I need to understand.
BTW i really think that our aggregations are defined properly
Thanks,
Eric
|||Analysis Server will go to the disk and will try to retrieve results if it cannot find any answers in a cache already. Analysis Server will always cache results from queries. But whether new query can be answered from the cache very much depends on several facts:
1. Queries are similar to the previous queries.
2. Calculation involved in a queries do not require going to the lowest level of granularity.
3. Attribute relationships defined correctly and new query can benefit from not exactly matching cache. ( for example you get answers from Months cache if you asked for Years )
You ultimate goal is not increase Analysis Server's memory footprint, but make your caches more effcient.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Dear All,
I'm having the same problem. When querying the OLAP by using ProClarity or SSMS (Management Studio), the response time is very low the CPU Utilization is below 10% and Memory Usage not more than 50%. When I check in the performance monitor, the I/O access is very high continuously 100% utilization when I are running query from ProClarity Analytics Server. Is there anything I can do to reduce I/O disk time ?
Thanks in advance.