Home > Archive > MS SQL Server > February 2006 > System-wide 'min memory per query' error









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author System-wide 'min memory per query' error
matt139

2006-02-11, 11:23 am

Hi everyone, I'm posting a server-wide issue I'm getting on a Windows
SQL 7 server and a Windows SQL 2000 server. Each server has several
databases (the SQL 2000 box has alot more than the older 7.0 server),
and alot of database queries are returning the following error to the
web browser when run against just about any database:

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not perform the
requested operation because the minimum query memory is not available.
Decrease the configured value for the 'min memory per query' server
configuration option.

It happens with just about any db on either server, they appear to come
close to running out of RAM. I figure sqlservr.exe would just start
using space on the paging file, but that's apparantly not the case.
I've already changed the 'min memory per query' value from the default
'1024' to the lowest setting, '512' KB. The 7.0 server has 512MB of
physical ram, and the SQL 2000 server has 2GB. I can get the errors to
go away for a few hours by stopping and re-starting the SQL service,
but that isn't a real fix of course.

I honestly have no clue on how to trace down if there is a particular
user that could be running bad queries and using up memory, or what. If
anyone can provide any further info, I would appreciate the assistance
(SQL administration isn't my normal job duty, I inherited it ;) ). If
anyone can include troubleshooting steps, please only provide
information on using tools that come with Windows Server, I can't use
any 3rd-party software, the company I work for won't provide the funds
to pay for it. Thank you to anyone in advance for the assistance.

John Bell

2006-02-11, 11:23 am

Hi

You don't say what servicepacks the machines are at? It is also not clear if
the databases are copies of the same database (or same application).

You may want to make sure that you have run maintenance on these databases
and that the statistics are up to date?

You may want to check out the query being run that give you this message,
but using SQL Profilers, then pasting that query into Query Analyser and
looking to see if you get the error and what the Query Plan is.

John


"matt139" <matt139@sbcglobal.net> wrote in message
news:1139670897.460030.161060@g14g2000cwa.googlegroups.com...
> Hi everyone, I'm posting a server-wide issue I'm getting on a Windows
> SQL 7 server and a Windows SQL 2000 server. Each server has several
> databases (the SQL 2000 box has alot more than the older 7.0 server),
> and alot of database queries are returning the following error to the
> web browser when run against just about any database:
>
> Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not perform the
> requested operation because the minimum query memory is not available.
> Decrease the configured value for the 'min memory per query' server
> configuration option.
>
> It happens with just about any db on either server, they appear to come
> close to running out of RAM. I figure sqlservr.exe would just start
> using space on the paging file, but that's apparantly not the case.
> I've already changed the 'min memory per query' value from the default
> '1024' to the lowest setting, '512' KB. The 7.0 server has 512MB of
> physical ram, and the SQL 2000 server has 2GB. I can get the errors to
> go away for a few hours by stopping and re-starting the SQL service,
> but that isn't a real fix of course.
>
> I honestly have no clue on how to trace down if there is a particular
> user that could be running bad queries and using up memory, or what. If
> anyone can provide any further info, I would appreciate the assistance
> (SQL administration isn't my normal job duty, I inherited it ;) ). If
> anyone can include troubleshooting steps, please only provide
> information on using tools that come with Windows Server, I can't use
> any 3rd-party software, the company I work for won't provide the funds
> to pay for it. Thank you to anyone in advance for the assistance.
>



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com