SQL server autogrowth failureSQL Server 2005: There is insufficient system memory to run this queryCan I change a live SQL Database from Autogrow safely?Restoring from backup with little disk space on SQL Server 2005What prevents a MS SQL Server database from shrinking?SQL Server database filled the hard drive and freeing up space isn't possibleSQL Express 2008 R2 on Amazon EC2 instance: tons of free memory, poor performanceSQL Server Issue: Could not allocate space for object … primary filegroup is fullTable Space and Data Sized increased multiple times after power failureSuitability of DL380p-Gen8 + D2700 for SQL 2012 Standard EditionIIS and SQL Server Performance Issues when not on same machine

How to deal with an excess of white-space in a CRM UI?

Do Veracrypt encrypted volumes have any kind of brute force protection?

Print "N NE E SE S SW W NW"

Placement of positioning lights on A320 winglets

Fully extended TQFT and lattice models

What game uses six-sided dice with symbols as well as numbers on the 5 and 6 faces?

How (un)safe is it to ride barefoot?

usage of mir gefallen

Can an open source licence be revoked if it violates employer's IP?

Is the first of the 10 Commandments considered a mitzvah?

Why are backslashes included in this shell script?

Must I use my personal social media account for work?

What is Gilligan's full name?

How can religions without a hell discourage evil-doing?

Is Jesus the last Prophet?

Nth term of Van Eck Sequence

What class is best to play when a level behind the rest of the party?

ISP is not hashing the password I log in with online. Should I take any action?

Someone who is granted access to information but not expected to read it

In American Politics, why is the Justice Department under the President?

How can powerful telekinesis avoid violating Newton's 3rd Law?

What publication claimed that Michael Jackson died in a nuclear holocaust?

Can I use 220 V outlets on a 15 ampere breaker and wire it up as 110 V?

Idiom for 'person who gets violent when drunk"



SQL server autogrowth failure


SQL Server 2005: There is insufficient system memory to run this queryCan I change a live SQL Database from Autogrow safely?Restoring from backup with little disk space on SQL Server 2005What prevents a MS SQL Server database from shrinking?SQL Server database filled the hard drive and freeing up space isn't possibleSQL Express 2008 R2 on Amazon EC2 instance: tons of free memory, poor performanceSQL Server Issue: Could not allocate space for object … primary filegroup is fullTable Space and Data Sized increased multiple times after power failureSuitability of DL380p-Gen8 + D2700 for SQL 2012 Standard EditionIIS and SQL Server Performance Issues when not on same machine






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I just ran into an SQL Server database (2005 or 2008, I'm not sure) which had autogrowth set to "By 10 percent, unrestricted growth" on the primary data file. It had no free space, and inserts were failing because of lack of free space.



The drive had over 100 GB free, and the data file was about 15 GB. I wish I had kept the error message, but it was something about "insufficient free space on PRIMARY". It was not a timeout exception like I've seen on a few occasions with 2000, where it could take long periods of time to resize.



I increased the "Initial Size" setting by about 5 GB, and it completed instantly, and everything started working again after that.



Why does SQL Server sometimes not autogrow when it should?










share|improve this question




























    0















    I just ran into an SQL Server database (2005 or 2008, I'm not sure) which had autogrowth set to "By 10 percent, unrestricted growth" on the primary data file. It had no free space, and inserts were failing because of lack of free space.



    The drive had over 100 GB free, and the data file was about 15 GB. I wish I had kept the error message, but it was something about "insufficient free space on PRIMARY". It was not a timeout exception like I've seen on a few occasions with 2000, where it could take long periods of time to resize.



    I increased the "Initial Size" setting by about 5 GB, and it completed instantly, and everything started working again after that.



    Why does SQL Server sometimes not autogrow when it should?










    share|improve this question
























      0












      0








      0








      I just ran into an SQL Server database (2005 or 2008, I'm not sure) which had autogrowth set to "By 10 percent, unrestricted growth" on the primary data file. It had no free space, and inserts were failing because of lack of free space.



      The drive had over 100 GB free, and the data file was about 15 GB. I wish I had kept the error message, but it was something about "insufficient free space on PRIMARY". It was not a timeout exception like I've seen on a few occasions with 2000, where it could take long periods of time to resize.



      I increased the "Initial Size" setting by about 5 GB, and it completed instantly, and everything started working again after that.



      Why does SQL Server sometimes not autogrow when it should?










      share|improve this question














      I just ran into an SQL Server database (2005 or 2008, I'm not sure) which had autogrowth set to "By 10 percent, unrestricted growth" on the primary data file. It had no free space, and inserts were failing because of lack of free space.



      The drive had over 100 GB free, and the data file was about 15 GB. I wish I had kept the error message, but it was something about "insufficient free space on PRIMARY". It was not a timeout exception like I've seen on a few occasions with 2000, where it could take long periods of time to resize.



      I increased the "Initial Size" setting by about 5 GB, and it completed instantly, and everything started working again after that.



      Why does SQL Server sometimes not autogrow when it should?







      sql-server






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 8 '10 at 22:07







      user59599



























          2 Answers
          2






          active

          oldest

          votes


















          0














          How did you verify and change the file size and auto-growth? Via T-SQL, or via the Management Studio? SSMS had a number of bugs on which it displayed and set erroneous auto-growth rates on data files, see Attaching a database increases autogrowth % to 12800.






          share|improve this answer























          • It's the value displayed in management studio. I'm trying to get results from sp_helpdb, and see if they're different.

            – user59599
            Nov 10 '10 at 14:45











          • BTW, You see immediate failure and immediate growth because the system has Instant File Initialization enabled, see msdn.microsoft.com/en-us/library/ms175935.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:07












          • To view current size and growth, check sys.database_files: technet.microsoft.com/en-us/library/ms174397.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:09











          • I finally got the results, and they match what's shown in Management Studio. Max size -1, growth 10, is_percent_growth 1.

            – user59599
            Nov 11 '10 at 14:46


















          0














          Try setting the auto grow option to a smaller value: 300 - 500 MB. Allocation of 1,5 GB (10% out of 15 GB data file) could have caused the insert queries to timeout waiting for the space to be allocated. What was the timeout set for? The default value in SQL is 600 sec but if the queries where run from a third-party application the timeout can be a lot smaller.






          share|improve this answer























          • I specifically pointed out that it's not a timeout. I've seen situations where it times out on the resize, and in those situations, doing a resize manually takes 5-10 minutes, and all inserts result in a timeout. In this situation, the commands fail instantly with no free space, the manual resize completes instantly, and the inserts immediately start working after the resize.

            – user59599
            Nov 10 '10 at 14:44











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f199607%2fsql-server-autogrowth-failure%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown
























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          How did you verify and change the file size and auto-growth? Via T-SQL, or via the Management Studio? SSMS had a number of bugs on which it displayed and set erroneous auto-growth rates on data files, see Attaching a database increases autogrowth % to 12800.






          share|improve this answer























          • It's the value displayed in management studio. I'm trying to get results from sp_helpdb, and see if they're different.

            – user59599
            Nov 10 '10 at 14:45











          • BTW, You see immediate failure and immediate growth because the system has Instant File Initialization enabled, see msdn.microsoft.com/en-us/library/ms175935.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:07












          • To view current size and growth, check sys.database_files: technet.microsoft.com/en-us/library/ms174397.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:09











          • I finally got the results, and they match what's shown in Management Studio. Max size -1, growth 10, is_percent_growth 1.

            – user59599
            Nov 11 '10 at 14:46















          0














          How did you verify and change the file size and auto-growth? Via T-SQL, or via the Management Studio? SSMS had a number of bugs on which it displayed and set erroneous auto-growth rates on data files, see Attaching a database increases autogrowth % to 12800.






          share|improve this answer























          • It's the value displayed in management studio. I'm trying to get results from sp_helpdb, and see if they're different.

            – user59599
            Nov 10 '10 at 14:45











          • BTW, You see immediate failure and immediate growth because the system has Instant File Initialization enabled, see msdn.microsoft.com/en-us/library/ms175935.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:07












          • To view current size and growth, check sys.database_files: technet.microsoft.com/en-us/library/ms174397.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:09











          • I finally got the results, and they match what's shown in Management Studio. Max size -1, growth 10, is_percent_growth 1.

            – user59599
            Nov 11 '10 at 14:46













          0












          0








          0







          How did you verify and change the file size and auto-growth? Via T-SQL, or via the Management Studio? SSMS had a number of bugs on which it displayed and set erroneous auto-growth rates on data files, see Attaching a database increases autogrowth % to 12800.






          share|improve this answer













          How did you verify and change the file size and auto-growth? Via T-SQL, or via the Management Studio? SSMS had a number of bugs on which it displayed and set erroneous auto-growth rates on data files, see Attaching a database increases autogrowth % to 12800.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 9 '10 at 5:25









          Remus RusanuRemus Rusanu

          7,9381522




          7,9381522












          • It's the value displayed in management studio. I'm trying to get results from sp_helpdb, and see if they're different.

            – user59599
            Nov 10 '10 at 14:45











          • BTW, You see immediate failure and immediate growth because the system has Instant File Initialization enabled, see msdn.microsoft.com/en-us/library/ms175935.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:07












          • To view current size and growth, check sys.database_files: technet.microsoft.com/en-us/library/ms174397.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:09











          • I finally got the results, and they match what's shown in Management Studio. Max size -1, growth 10, is_percent_growth 1.

            – user59599
            Nov 11 '10 at 14:46

















          • It's the value displayed in management studio. I'm trying to get results from sp_helpdb, and see if they're different.

            – user59599
            Nov 10 '10 at 14:45











          • BTW, You see immediate failure and immediate growth because the system has Instant File Initialization enabled, see msdn.microsoft.com/en-us/library/ms175935.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:07












          • To view current size and growth, check sys.database_files: technet.microsoft.com/en-us/library/ms174397.aspx

            – Remus Rusanu
            Nov 10 '10 at 15:09











          • I finally got the results, and they match what's shown in Management Studio. Max size -1, growth 10, is_percent_growth 1.

            – user59599
            Nov 11 '10 at 14:46
















          It's the value displayed in management studio. I'm trying to get results from sp_helpdb, and see if they're different.

          – user59599
          Nov 10 '10 at 14:45





          It's the value displayed in management studio. I'm trying to get results from sp_helpdb, and see if they're different.

          – user59599
          Nov 10 '10 at 14:45













          BTW, You see immediate failure and immediate growth because the system has Instant File Initialization enabled, see msdn.microsoft.com/en-us/library/ms175935.aspx

          – Remus Rusanu
          Nov 10 '10 at 15:07






          BTW, You see immediate failure and immediate growth because the system has Instant File Initialization enabled, see msdn.microsoft.com/en-us/library/ms175935.aspx

          – Remus Rusanu
          Nov 10 '10 at 15:07














          To view current size and growth, check sys.database_files: technet.microsoft.com/en-us/library/ms174397.aspx

          – Remus Rusanu
          Nov 10 '10 at 15:09





          To view current size and growth, check sys.database_files: technet.microsoft.com/en-us/library/ms174397.aspx

          – Remus Rusanu
          Nov 10 '10 at 15:09













          I finally got the results, and they match what's shown in Management Studio. Max size -1, growth 10, is_percent_growth 1.

          – user59599
          Nov 11 '10 at 14:46





          I finally got the results, and they match what's shown in Management Studio. Max size -1, growth 10, is_percent_growth 1.

          – user59599
          Nov 11 '10 at 14:46













          0














          Try setting the auto grow option to a smaller value: 300 - 500 MB. Allocation of 1,5 GB (10% out of 15 GB data file) could have caused the insert queries to timeout waiting for the space to be allocated. What was the timeout set for? The default value in SQL is 600 sec but if the queries where run from a third-party application the timeout can be a lot smaller.






          share|improve this answer























          • I specifically pointed out that it's not a timeout. I've seen situations where it times out on the resize, and in those situations, doing a resize manually takes 5-10 minutes, and all inserts result in a timeout. In this situation, the commands fail instantly with no free space, the manual resize completes instantly, and the inserts immediately start working after the resize.

            – user59599
            Nov 10 '10 at 14:44















          0














          Try setting the auto grow option to a smaller value: 300 - 500 MB. Allocation of 1,5 GB (10% out of 15 GB data file) could have caused the insert queries to timeout waiting for the space to be allocated. What was the timeout set for? The default value in SQL is 600 sec but if the queries where run from a third-party application the timeout can be a lot smaller.






          share|improve this answer























          • I specifically pointed out that it's not a timeout. I've seen situations where it times out on the resize, and in those situations, doing a resize manually takes 5-10 minutes, and all inserts result in a timeout. In this situation, the commands fail instantly with no free space, the manual resize completes instantly, and the inserts immediately start working after the resize.

            – user59599
            Nov 10 '10 at 14:44













          0












          0








          0







          Try setting the auto grow option to a smaller value: 300 - 500 MB. Allocation of 1,5 GB (10% out of 15 GB data file) could have caused the insert queries to timeout waiting for the space to be allocated. What was the timeout set for? The default value in SQL is 600 sec but if the queries where run from a third-party application the timeout can be a lot smaller.






          share|improve this answer













          Try setting the auto grow option to a smaller value: 300 - 500 MB. Allocation of 1,5 GB (10% out of 15 GB data file) could have caused the insert queries to timeout waiting for the space to be allocated. What was the timeout set for? The default value in SQL is 600 sec but if the queries where run from a third-party application the timeout can be a lot smaller.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 10 '10 at 10:37









          yrushkayrushka

          58529




          58529












          • I specifically pointed out that it's not a timeout. I've seen situations where it times out on the resize, and in those situations, doing a resize manually takes 5-10 minutes, and all inserts result in a timeout. In this situation, the commands fail instantly with no free space, the manual resize completes instantly, and the inserts immediately start working after the resize.

            – user59599
            Nov 10 '10 at 14:44

















          • I specifically pointed out that it's not a timeout. I've seen situations where it times out on the resize, and in those situations, doing a resize manually takes 5-10 minutes, and all inserts result in a timeout. In this situation, the commands fail instantly with no free space, the manual resize completes instantly, and the inserts immediately start working after the resize.

            – user59599
            Nov 10 '10 at 14:44
















          I specifically pointed out that it's not a timeout. I've seen situations where it times out on the resize, and in those situations, doing a resize manually takes 5-10 minutes, and all inserts result in a timeout. In this situation, the commands fail instantly with no free space, the manual resize completes instantly, and the inserts immediately start working after the resize.

          – user59599
          Nov 10 '10 at 14:44





          I specifically pointed out that it's not a timeout. I've seen situations where it times out on the resize, and in those situations, doing a resize manually takes 5-10 minutes, and all inserts result in a timeout. In this situation, the commands fail instantly with no free space, the manual resize completes instantly, and the inserts immediately start working after the resize.

          – user59599
          Nov 10 '10 at 14:44

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f199607%2fsql-server-autogrowth-failure%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          RemoteApp sporadic failureWindows 2008 RemoteAPP client disconnects within a matter of minutesWhat is the minimum version of RDP supported by Server 2012 RDS?How to configure a Remoteapp server to increase stabilityMicrosoft RemoteApp Active SessionRDWeb TS connection broken for some users post RemoteApp certificate changeRemote Desktop Licensing, RemoteAPPRDS 2012 R2 some users are not able to logon after changed date and time on Connection BrokersWhat happens during Remote Desktop logon, and is there any logging?After installing RDS on WinServer 2016 I still can only connect with two users?RD Connection via RDGW to Session host is not connecting

          How to write a 12-bar blues melodyI-IV-V blues progressionHow to play the bridges in a standard blues progressionHow does Gdim7 fit in C# minor?question on a certain chord progressionMusicology of Melody12 bar blues, spread rhythm: alternative to 6th chord to avoid finger stretchChord progressions/ Root key/ MelodiesHow to put chords (POP-EDM) under a given lead vocal melody (starting from a good knowledge in music theory)Are there “rules” for improvising with the minor pentatonic scale over 12-bar shuffle?Confusion about blues scale and chords

          Esgonzo ibérico Índice Descrición Distribución Hábitat Ameazas Notas Véxase tamén "Acerca dos nomes dos anfibios e réptiles galegos""Chalcides bedriagai"Chalcides bedriagai en Carrascal, L. M. Salvador, A. (Eds). Enciclopedia virtual de los vertebrados españoles. Museo Nacional de Ciencias Naturales, Madrid. España.Fotos