RE: Set up SQL sbsmonitoring process and services stopped
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Thu, 15 Sep 2005 07:43:22 GMT
Hi,
Thanks for posting here!
For your description, I understand that your concern is that if there is a
memory leak issue when the MSSQL$SBSMONITORING service run. If I am off
base, please don't hesitate to let me know.
Based on my research most cases, this may not be a memory leak issue. 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.
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 your 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
your system (plus some padding)).
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
I am afraid that that set max server memory as 100 MB is too low, I suggest
that you try to increase the value to see if the issue be fixed. And not
only we can use max server memory to prevent SQL Server from using more
that the specified amount of memory (but also we can use min server memory
to guarantee a minimum amount of memory to an instance of SQL Server). To
do so, open a command prompt and run the following command:
osql -E -S sbsserver\<instance name>
You will enter the osql command prompt. Run the commends below (replace
<xxx> with the amount of memory):
1> EXEC sp_configure 'show advanced options', 1
2> reconfigure
3> go
1> EXEC sp_configure 'min server memory', <xxx>
2> reconfigure
3> go
1> EXEC sp_configure 'max server memory', <xxx>
2> reconfigure
3> go
After doing the above steps, you may run the commands to check the
configured memory usage:
1> EXEC sp_configure
2> go
Hope this helps. If you have any further concern or question on the issue,
please feel free to let me know. I am looking forward to your reply!
Have a nice day!
Best Regards,
Jenny Wu
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: Set up SQL sbsmonitoring process and services stopped
>thread-index: AcW5SClKYbeYe3a4RwG3VQMdmUodCg==
>X-WBNR-Posting-Host: 64.60.5.162
>From: "=?Utf-8?B?c2JERg==?=" <sbDF@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: Set up SQL sbsmonitoring process and services stopped
>Date: Wed, 14 Sep 2005 09:20:03 -0700
>Lines: 23
>Message-ID: <F6862B45-B334-42E6-9C2A-D58B48375C65@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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:153329
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi,
>
>I had a memory leak problem on the process sql$sbsmonitoring.He was
growing
>and growing... I accessed the sp_configure and I modified the max server
>memory to 100 Mo. But After 1 days, some processes stopped automatically.
>example: In the client machine no more access to the share folders, no
access
>to internet, on the server no more monitoring,
>back up reports, RWW,....
>I saw a critical alert of processor activity (process was staying in idle
>time too long....)! Why does the server start to stop services? Do I need
to
>change a value in the alert
>threshold? Is the value 100 Mo too low for my server?
>
>So i increase the value to 600... But how could i go back to the automatic
>settings?
>Or why does he start to stop these services after the modification (maybe
>the value was too low?)?
>
>Thank you
>
>sebastien
>
>
>
.
- Prev by Date: RE: Lost files on desktop after using Group Policy to set Wallpaper
- Next by Date: RE: Exchange ActiveSync HTTP/1.1 100 continue error
- Previous by thread: RE: Lost files on desktop after using Group Policy to set Wallpaper
- Next by thread: RE: Exchange ActiveSync HTTP/1.1 100 continue error
- Index(es):
Relevant Pages
|
