• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2302
  • Last Modified:

"Not enough storage is available to complete this operation" When Inserting Into SQL BLOB

Yesterday, I had an issue with one of our programs when it was trying to insert a file into the Image field of our SQL Server 2000 database.  The file itself was just under 400MB and the error returned by my program was "Not enough storage is available to complete this operation."  The hard drives and database/logs both had plenty of free space to accommodate this file.  I know that the maximum size of an Image field is 2G, but does that equate to me actually being able to store up to a 2G file?  If not, what is the size of the largest file that will fit into this field?

Thank you!
0
rtedi222
Asked:
rtedi222
  • 3
1 Solution
 
dbaSQLCommented:
I have seen this before, but it's been specific to the application running -- there was a memory leak.  If your hard drives all have ample storage space, I would check the program for a memory leak.

maybe the connection that is inserting this file isn't closing properly
hence, the memory leak?

this is a big maybe, but i have seen that as the cause of this error before.  
0
 
dbaSQLCommented:
Oh, also, you didn't specify exactly how you were inserting the file.  
If it's DTS or pre-sp3, it may be this:    http://support.microsoft.com/?kbid=889170
0
 
rtedi222Author Commented:
We are running SP4 and the INSERT is through a query in my VB application.
0
 
dbaSQLCommented:
still, this could be the memory leak.   is this something you could use?
http://msdn2.microsoft.com/en-us/library/aa293901(VS.60).aspx

i suppose if it is ram deficiency, it could be specific to sql, too.  first, check tempdb --- if the program is caching heavy in the tempdb and it's not able to grow enough, we could have problems here.
also, how much ram does sql have, and is it allowed to allocate its own memory dynamically?

other than that, i am not too sure.  this is not xml, is it?   per BOL:

Note  A parsed document is stored in the internal cache of SQL Server 2000. The MSXML parser uses one-eighth the total memory available for SQL Server. To avoid running out of memory, run sp_xml_removedocument to free up the memory.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now