Error-Not enough storage is available to complete this operation.

• Paul White

  SSC Guru

  Points: 150467

  More actions

  March 17, 2010 at 10:34 am

  #1135397

  CirquedeSQLeil (3/17/2010)

  ---

  Is the OP still out there?

  Is this still an issue?

  I've given up...

  Paul White
  SQLPerformance.com
  SQLkiwi blog
  @SQL_Kiwi

• SQLRNNR

  SSC Guru

  Points: 281334

  More actions

  March 17, 2010 at 10:36 am

  #1135399

  Paul White (3/17/2010)

  ---

  CirquedeSQLeil (3/17/2010)

  ---

  Is the OP still out there?

  Is this still an issue?

  I've given up...

  I'll check back if I see another response - but really kinda in the same opinion.

  Jason...AKA CirqueDeSQLeil
  _______________________________________________
  I have given a name to my pain...MCM SQL Server, MVP
  SQL RNNR
  Posting Performance Based Questions - Gail Shaw[/url]
  Learn Extended Events

• GoGreen

  Mr or Mrs. 500

  Points: 510

  More actions

  March 17, 2010 at 9:05 pm

  #1135681

  Thanks for reply to all..

  I found the issue it was due to how SQL string is created in my program....

  Which uses much of resources...

• SQLRNNR

  SSC Guru

  Points: 281334

  More actions

  March 17, 2010 at 9:12 pm

  #1135683

  GoGreen (3/17/2010)

  ---

  Thanks for reply to all..

  I found the issue it was due to how SQL string is created in my program....

  Which uses much of resources...

  thanks for letting us know.

  Jason...AKA CirqueDeSQLeil
  _______________________________________________
  I have given a name to my pain...MCM SQL Server, MVP
  SQL RNNR
  Posting Performance Based Questions - Gail Shaw[/url]
  Learn Extended Events

• jwinston

  Valued Member

  Points: 74

  More actions

  August 31, 2010 at 7:32 am

  #1214274

  I just recently found this thread when faced with a similar problem. Thanks to everyone that posted suggestions, solutions, and advice. It helped me discover I was facing a resource constraint from another source. Apparently SSMS has been unable to handle large files for over three years. Suggestion #269566

  The error "Not enough storage...." can be generate from SSMS-related bug. To reproduce this error create a 30MB XML file, load it into SSMS, edit the file, attempt to save.

  I hope my contribution will help the next weary DBA that crosses this error.

  IMO, releasing a UI for a "production-grade" server system incapable of handling moderately sized data sets is unconscionable. Allowing a bug that hamstrings DBAs working on production servers deployed world-wide to go unpatched for over three years borders on willfully malicious. Am I working on the "wrong" MS technology? What software is getting the updates, patches, and attention?