Re: Another SQL Memory Issue

It's just how SQL is designed. See http://support.microsoft.com/kb/321363

I was mistaken in saying that SQL defaults to half the memory installed in
the server. It defaults to 2 GB.
http://technet.microsoft.com/en-us/library/ms178067.aspx

It seems to me that some people with SBS throttle the maximum memory
settings for instances such as WSUS and ISA logging, to prevent the
allocated memory alerts. I've done that myself with no ill effects, as has
Susan. Other people just raise the alert threshold to 110% or more of the
30-day average, and others still will ignore or disable the allocated memory
alert. My SBS has 4 GB of RAM, and it was bugging me to have WSUS using a
GB, but I probably wouldn't recommend messing with the memory setting unless
you really feel a need to do so for some reason. I have not had any
negative effects, but to me this falls in the category of "if it aint'
broke, don't fix it." Also, apparently PSS has declined to give
recommendations for these settings, because there are too many different
scenarios for them to be comfortable making blanket recommendations.


"James" <James@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:728611EA-CD77-4353-A7DE-83FBF58ADE44@xxxxxxxxxxxxxxxx
I don't understand why SQL/CRM would use 1 gig of ram, when the application
isn't even being used. It is installed and configured, I have created the
adminstrator acocount, and one test user account to make sure everything
was
working (email via exchange, report server, etc.), but it still loads up
memory.

Also note, we are strictly using the server to host web applications (CRM,
SharePoint, Cognos, etc.). There are no desktops or other client
computers
that connect to it in a traditional sense.

"Dave Nickason [SBS MVP]" wrote:

IMO the problem is that you have multiple SQL instances on an SBS, and
all
of them by default are probably configured to use a maximum of half the
ram
on the box. There are situations where an application may not
technically
"need" more ram to do its job, but I might rather have more ram available
to
that app, than to give a gig or two to WSUS, which runs all the time but
only works for 5 minutes a month. I'd rather have the ram going to
Exchange, SharePoint, etc. than to have those user applications competing
with things like WSUS, monitoring, and ISA logging, which don't benefit
from
the ton of ram they want, and which don't matter to the users.


"Tony Su" <TonySu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5E2B729F-CE8E-4360-8108-C1504FC03FD9@xxxxxxxxxxxxxxxx
James,
Although the other posts have offered some interesting advice, IMO they
only
attempt to address the symptom (excessive SQL memory allocation without
returning resources to the pool) and don't address the source of your
problem.

Using Process Manager or even Task Manager, you can probably identify
in a
general sense which SQL instance is acquiring and not releasing
resources.

That application should be closely inspected, because no application
written
properly to Microsoft's "Best Practices" should ever cause this kind of
problem, SQL is usually very good about returning unused resources
within
approx 5 minutes if other processes require those resources.

--
Tony Su
www.su-networking.com
angry.su-networking.com (Corporate Torrent Transfer Networks on
Windows)
ISA
SBS
Enterprise Mobile Solutions Architect


"James" wrote:

I am running SBS 03' SP2 with Exchange, CRM 3.0, SQL 2005, and WSS 3.0
side
by side with 2.0.

I had a problem with sqlservr (NETWORK SERVICE) hogging lots of memory
and I
corrected that problem by using
\\.\pipe\mssql$microsoft##ssee\sql\query
and
then setting a limit on the memory SharePoint uses.

Everything works fine with the embed version of SQL, however now I am
running into the same problem with sqlservr.exe (SYSTEM), some times
using as
much as 1 GIG of RAM. I am pretty sure that this is the DB that CRM
uses,
and since we havent implemented it yet, I just stop te mssqlservr
service
and
everything goes back to normal. I am definitly a beginer with SQL and
I
dont
know how to query the database to regulate the memory.

Any thoughts?

Thanks





.

Relevant Pages

  • Re: Alocated Memory Error (SQLSERVR)
    ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... specifically the SQL Server 2000 Standard Edition on that server. ... His point is that applications can only use up to 2 GB or RAM on ... a process running under Windows 2000 or Windows Server 2003 can ... used) with some of the memory being physical memory and some being virtual ...
    (microsoft.public.win2000.general)
  • Re: Alocated Memory Error (SQLSERVR)
    ... FWIW I am not using sbs 2003 premium, ... non ever going about 200mb of memory usage. ... on what you should throttle the RAM to. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Alocated Memory Error (SQLSERVR)
    ... what you should throttle the RAM to. ... Server 2000 SP4, ... The memory problem on my ... shared exchange server address book or anything exchange related). ...
    (microsoft.public.windows.server.sbs)
  • Re: Performance problems -- need guidance on scaling
    ... Thanks for the update on the FT Catalog corruption, ... will use, up to a max of 512Mb, if this memory is available. ... a server with 512 MB of RAM and a resource_usage value of 5 ... the data, you could, detach your SQL 2000 mdf & ldf files ...
    (microsoft.public.sqlserver.fulltext)
Loading