RE: server problems
- From: v-natliu@xxxxxxxxxxxxxxxxxxxx ("Nathan Liu [MSFT]")
- Date: Wed, 14 Dec 2005 09:38:57 GMT
Hi Nigel,
Thank you for your kind update.
I appreciate your time and cooperation. Please do not hesitate to let me
know if you have any further concerns, I am looking forward to hearing from
you.
Have a nice day!
Best regards,
Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: server problems
>thread-index: AcYABj2ELzbYogo/SwGpwbkfs7hZSg==
>X-WBNR-Posting-Host: 24.191.237.174
>From: "=?Utf-8?B?bmlnZWxjb3VydG5leQ==?="
<nigelcourtney@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <543E5E26-99C9-41C9-9D20-D72AEAA57C6F@xxxxxxxxxxxxx>
<doLe7K6$FHA.3764@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: server problems
>Date: Tue, 13 Dec 2005 08:57:02 -0800
>Lines: 170
>Message-ID: <AC6A1601-B2A7-4524-A8D5-E452A0A19A67@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:229842
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>ok, thank you so getting that email like I did last night, 10 times I
should
>not worry about the same email about the first post.
>
>""Nathan Liu [MSFT]"" wrote:
>
>> Hello Nigel,
>>
>> Thank you for posting in the SBS newsgroup.
>>
>> In most cases, this is a normal behavior. Since SBS 2003 server is an
>> integrated product, some services such as Exchange Information store,
ISA
>> web proxy service or SQL Server will normally use large memory.
>>
>> SQL Server is designed to use memory. It caches data and query plans to
>> memory so that it will be able to quickly access data. All relational
>> database management systems do this. Unless you are experiencing
problems
>> because of the high memory usage from SQL Server, I would not worry.
>>
>> When you start SQL Server, SQL Server memory usage may continue to
steadily
>> increase and not decrease, even when activity on the server is low.
>> Additionally, the Task Manager and Performance Monitor may show that the
>> physical memory available on the computer is steadily decreasing until
the
>> available memory is between 4 to 10 MB.
>>
>> This behavior alone does not indicate a memory leak. This behavior is
>> normal and is an intended behavior of the SQL Server buffer pool.
>>
>> By default, SQL Server dynamically grows and shrinks the size of its
buffer
>> pool (cache) depending on the physical memory load reported by the
>> operating system. As long as enough memory is available to prevent
paging
>> (between 4 - 10 MB), the SQL Server buffer pool will continue to grow.
As
>> other processes on the same computer as SQL Server allocate memory, the
SQL
>> Server buffer manager will release memory as needed. SQL Server can free
>> and acquire several megabytes of memory each second, allowing it to
quickly
>> adjust to memory allocation changes.
>>
>> For more information, please see the article below:
>>
>> 321363 INF: SQL Server Memory Usage
>> http://support.microsoft.com/?id=321363
>>
>> Generally speaking, if you can confirm that everything is working as
>> expected, that there are no problems/errors with the system, then you
can
>> actually check the average count and change it to match that system.
>>
>> The Health monitor is running on the SBS server. The alert feature is
>> provided by Health monitor component. Open Health Monitor console in
>> Administrative Tools, navigate to All Monitored
Computers\ServerName\Small
>> Business Server Alerts\Core Server Alerts\, you will find an object
named
>> 'Allocated Memory'. This predefined object monitors the committed bytes
of
>> the SBS server and sends the alert when the value reaches the threshold.
>> The value is approximate to the "Total Commit Charge" value in Task
>> Manager.
>>
>> A memory allocation threshold is configured on the particular monitored
>> object. When the average value of the object (for example, the committed
>> memory size) reaches the threshold, the server will send an alert e-mail
to
>> the admin. For the memory allocation size, the default threshold is
>> 2147483648.
>>
>> This memory allocation value is depending on the current server load,
>> physical memory size and page file size on the SBS server. For a SBS
server
>> with large physical memory (for example 2GB), it's expected that the
>> committed bytes is high. The committed bytes counter indicates the
Memory
>> allocated to programs and the operating system. Technically speaking,
some
>> processes such as Exchange store process and SQL database engine could
use
>> as much memory as they can. This causes high memory usage behavior on a
SBS
>> server.
>>
>> The counter that is being triggered in Health Monitor is for Allocated
>> Memory > 2,147,483,648 bytes; this number is static and is configured
>> similarly on all SBS 2003 server installations, this might mean that
that
>> number may not be representing the true baseline for that particular
server
>> installation. If you can confirm that everything is working as expected,
>> that there are no problems/errors with the system, then you can actually
>> check the average count and change it to match that system.
>>
>> You can do it from the Monitoring and Reporting snap-in in Server
>> Management (under Change Alert Notifications, then select Performance
>> Counters, and then check the Counter Average for Allocated Memory. You
can
>> then Edit that entry and replace the default threshold with the average
for
>> that system (plus some padding)).
>>
>> The best way to identify the memory threshold on a particular SBS server
is
>> to use the performance monitor utility. We can use the utility to
capture a
>> long term memory and process status (5 to 10 days) and then analyze the
>> performance log to get the average memory usage of the SBS server. Then,
we
>> can define the memory allocation threshold of the SBS server. Generally
>> speaking, we can use the 130%~ 140% average values as the threshold.
>>
>> If you have any questions or concerns related to this issue, please let
me
>> know.
>>
>> I appreciate your time and look forward to hearing from you.
>>
>> Best regards,
>>
>> Nathan Liu (MSFT)
>> Microsoft CSS Online Newsgroup Support
>>
>> Get Secure! - www.microsoft.com/security
>> ======================================================
>> This newsgroup only focuses on SBS technical issues. If you have issues
>> regarding other Microsoft products, you'd better post in the
corresponding
>> newsgroups so that they can be resolved in an efficient and timely
manner.
>> You can locate the newsgroup here:
>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>
>> When opening a new thread via the web interface, we recommend you check
the
>> "Notify me of replies" box to receive e-mail notifications when there
are
>> any updates in your thread. When responding to posts via your
newsreader,
>> please "Reply to Group" so that others may learn and benefit from your
>> issue.
>>
>> Microsoft engineers can only focus on one issue per thread. Although we
>> provide other information for your reference, we recommend you post
>> different incidents in different threads to keep the thread clean. In
doing
>> so, it will ensure your issues are resolved in a timely manner.
>>
>> For urgent issues, you may want to contact Microsoft CSS directly.
Please
>> check http://support.microsoft.com for regional support phone numbers.
>>
>> Any input or comments in this thread are highly appreciated.
>> ======================================================
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>>
>> --------------------
>> >Thread-Topic: server problems
>> >thread-index: AcX/bbBBqdmnWj2VRsik7U977vhykA==
>> >X-WBNR-Posting-Host: 24.191.237.174
>> >From: "=?Utf-8?B?bmlnZWxjb3VydG5leQ==?="
>> <nigelcourtney@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >Subject: server problems
>> >Date: Mon, 12 Dec 2005 14:45:02 -0800
>> >Lines: 14
>> >Message-ID: <543E5E26-99C9-41C9-9D20-D72AEAA57C6F@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.sbs
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:229628
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >I have sbs prem edt 03 and in the monitor and reports that the server
>> emails
>> >to me I have been getting this msg lately.
>> >
>> >"The processor is experiencing a low level of idle time. Consistently
low
>> >levels of idle time can cause performance problems.
>> >Use Task Manager to view the top processes by CPU. If a service or
less
>> >important process appears to be unusual, try stopping and then
restarting
>> >it."
>> >
>> >The only thing that has using it the most is the sqlservr..
>> >
>> >How can this problem be fixed?
>> >
>> >thanks in advance
>> >
>>
>>
>
.
- References:
- RE: server problems
- From: "Nathan Liu [MSFT]"
- RE: server problems
- From: nigelcourtney
- RE: server problems
- Prev by Date: RE: MSDE, Access, SharePoint... I am not sure where to ask this qu
- Next by Date: Re: sysvol gone! DCGPOFIX?
- Previous by thread: RE: server problems
- Next by thread: RE: MSDE, Access, SharePoint... I am not sure where to ask this questi
- Index(es):
Relevant Pages
|
