Error: 17803, Severity: 20, State: 14 Insufficient Memory 
Author Message
 Error: 17803, Severity: 20, State: 14 Insufficient Memory

I have a SQL 2000 Cluster that has started to act up.  I am getting this
error message in the Application Log.  Earlier the server froze up so nobody
could connect.  I failed it over to the standby node and we can now connect,
but I am still getting this message.

We are currently testing SP2 but have not installed either SP1 or SP2 on
production.  I saw a KB article that stated that there is a memory leak with
the SQLPutData API, but our developers have told me that they are not using
this API in our application.

Any ideas would be greatly appreciated.



Wed, 26 May 2004 06:40:36 GMT
 Error: 17803, Severity: 20, State: 14 Insufficient Memory

Hi,
The error  17803 "Insufficient memory available." is a generic "out of memory" condition. There are many sources of this
error since there are many different consumers of memory in the SQL Server process space. These can probably fall into 2
main categories : a memory leak or high memory use by both SQL Server and non-SQL Server consumers (e.g. xprocs,
oledb providers, odbc drivers,etc.)

Analysis of  17803 problem normally requires the following information captured:

- Performance Monitor data : all memory counters, including SQL.
- Periodic VMStat snapshot to see how VM is used
- Periodic SQL snapshot information : sysprocesses, DBCC MEMORYSTATUS

As you can see, it's not a trivial undertaking. If this a production showstopper, I would recommend opening a support
incident with MS Tech Support.

Check the SQL errorlogs for other symptons. Make sure your index statistics are updated. Use Profiler  to help find what
kind of execution plans the long running queries are using. Then use Index Tuning Wizard to help analyze indexing. Goal is
identify queries that are memory intensive and requires lots of locks. Also watch for blocking as blocked processes will not
release resources until they are completed and thereby reducing available memory for other

HTH!
Keith
=================================================
*  This posting is provided "AS IS" with no warranties, and confers no rights.
*  Please do not send email directly to this alias.Respond to newsgroup

--------------------

|>Subject: Error: 17803, Severity: 20, State: 14 Insufficient Memory
|>Date: Fri, 7 Dec 2001 16:40:36 -0600
|>
|>I have a SQL 2000 Cluster that has started to act up.  I am getting this
|>error message in the Application Log.  Earlier the server froze up so nobody
|>could connect.  I failed it over to the standby node and we can now connect,
|>but I am still getting this message.
|>
|>We are currently testing SP2 but have not installed either SP1 or SP2 on
|>production.  I saw a KB article that stated that there is a memory leak with
|>the SQLPutData API, but our developers have told me that they are not using
|>this API in our application.
|>
|>Any ideas would be greatly appreciated.
|>
|>
|>



Mon, 31 May 2004 16:14:25 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. SQL2000 - Error: 17803 (Insufficient memory available) Severity: 20

2. Problem with SQL 7.0 Error: 17803, Severity: 17, State: 3

3. 17803 Insufficient memory error

4. 17803 - insufficient memory error

5. error - 17803 Insufficient memory available

6. SQL 7 ODS Error: 17803 Insufficient memory available

7. Error 17803 Insufficient Memory Available

8. error : 17803 Insufficient Memory Available

9. Error: 702, Severity: 20, State: 1

10. Error 17805 Severity 20 State 3

11. Error 17805 Severity 20 State 3

12. Error: 1534 Severity: 20, State: 1 Extent:15480 not found in shared extent directory


 
Powered by phpBB® Forum Software