Re: Another SQL Memory Issue

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: Large Amount of Memory Message
    ... But wasn't really sure how to match each instance of SQL with a specific ... physical RAM - in other words, if it's using the page file. ... Memory Properties) means so I don't want to necessarily change the alert: ...
    (microsoft.public.windows.server.sbs)
  • Re: Low on Virual Memory in SBS 2003
    ... Am I supposed to be putting a cap on the maximum amount of RAM that Exchange ... I don't think a memory leak is the only explanation for this. ... Although the SQL Server has been running since the first day, ... The SQL server logs seem to be clean and I am not sure what to look ...
    (microsoft.public.windows.server.sbs)
  • Re: Low on Virual Memory in SBS 2003
    ... With a commit charge at around half of the available RAM, ... Exchange or SQL further. ... System low on virtual memory is a system leak somewhere. ...
    (microsoft.public.windows.server.sbs)
  • Re: Critique of Robert C. Martins "Agile Principles, Patterns, and Practices"
    ... comeback one day when RAM storage becomes cheaper than disk. ... However, databases tend to get bigger also as they can, so ... I've seen a lot of "business rules" being handled by SQL. ...
    (comp.object)
  • Re: Isolating Biztalk databases
    ... You can allocate system resources to each instance of SQL. ... problem is CPU or memory related then separate instances will help. ...
    (microsoft.public.biztalk.general)
Loading