SQL Server Management Studio CPU and RAM usage keeps increasing for no reasonHow are SQL server management...

Existence of Riemann surface, holomorphic maps

What makes papers publishable in top-tier journals?

I have trouble understanding this fallacy: "If A, then B. Therefore if not-B, then not-A."

What is the wife of a henpecked husband called?

Why avoid shared user accounts?

Translation needed for 130 years old church document

Does Skippy chunky peanut butter contain trans fat?

How is it possible that the folder is there yet isnt in the same time?

Why does magnet wire need to be insulated?

Am I correct in stating that the study of topology is purely theoretical?

Not a Long-Winded Riddle

Which RAF squadrons and aircraft types took part in the bombing of Berlin on the 25th of August 1940?

Does diversity provide anything that meritocracy does not?

Does the US government have any planning in place to ensure there's no shortages of food, fuel, steel and other commodities?

How do you funnel food off a cutting board?

Why is it that Bernie Sanders is always called a "socialist"?

Book where a space ship journeys to the center of the galaxy to find all the stars had gone supernova

Count repetitions of an array

Why do neural networks need so many training examples to perform?

Cat is tipping over bed-side lamps during the night

Website seeing my Facebook data?

"Starve to death" Vs. "Starve to the point of death"

How to not let the Identify spell spoil everything?

How much mayhem could I cause as a fish?



SQL Server Management Studio CPU and RAM usage keeps increasing for no reason


How are SQL server management studio passwords saved?SQL Server Management Studio: Database Attachment FailedSql Server Management Studio: Change Prefix or Suffix charactersFloating or vertical results pane in SQL Server Management StudioSQL Server Management Studio print in colorSQL Server Management Studio 2005 SQL dumpClean reinstall SQL Server Management StudioResults view does not change with zoom feature in SQL Server Management StudioSQL Server Management Studio graphical glitchesopen SQL Server Management Studio from another machine













1















I have a weird problem with SQL Server Management Studio, version 11.0.2100.60. When I was writing some query, sometimes the CPU gets hogged, and RAM usage keeps increasing.
Usually closing and reopening SSMS will solve the problem, but it is quite annoying if I have to do this multiple times.



How to solve this issue?



enter image description here



[UPDATE]: I ran the PerfView to analyze the CPU usage. But I'm not quite sure how to troubleshoot from there:



PerfView CPU Stacks, showing ssms using a lot of CPU resource:
enter image description here



Drilling down Ssms. Looks like this ntdll is taking the most resource:
enter image description here



GC Heap Net Mem (Coarse Sampling):
enter image description here










share|improve this question

























  • its not really unusual for monolithic tools like Visual Studio or SMSS to take up a GB or more of ram, especially if you leave them open for days or weeks at a time as I do. for the CPU, are you typing SQL code, or do you have designer windows open? have you used the "edit top 200" or anything like that which keeps connections open for long periods?

    – Frank Thomas
    Apr 5 '17 at 4:01











  • I'm not opening SSMS for days, I open only like few hours. I was editing a stored procedure, no other windows open.

    – rcs
    Apr 5 '17 at 5:34











  • Even when I close all the query tabs, the problem still persists. Needs to close the entire SSMS and reopen.

    – rcs
    Apr 5 '17 at 5:47











  • use ETW to trace CPU and memory usage

    – magicandre1981
    Apr 5 '17 at 15:13











  • have you analyzed the CPU/memory usage with xperf/WPR/WPA?

    – magicandre1981
    Apr 11 '17 at 14:40
















1















I have a weird problem with SQL Server Management Studio, version 11.0.2100.60. When I was writing some query, sometimes the CPU gets hogged, and RAM usage keeps increasing.
Usually closing and reopening SSMS will solve the problem, but it is quite annoying if I have to do this multiple times.



How to solve this issue?



enter image description here



[UPDATE]: I ran the PerfView to analyze the CPU usage. But I'm not quite sure how to troubleshoot from there:



PerfView CPU Stacks, showing ssms using a lot of CPU resource:
enter image description here



Drilling down Ssms. Looks like this ntdll is taking the most resource:
enter image description here



GC Heap Net Mem (Coarse Sampling):
enter image description here










share|improve this question

























  • its not really unusual for monolithic tools like Visual Studio or SMSS to take up a GB or more of ram, especially if you leave them open for days or weeks at a time as I do. for the CPU, are you typing SQL code, or do you have designer windows open? have you used the "edit top 200" or anything like that which keeps connections open for long periods?

    – Frank Thomas
    Apr 5 '17 at 4:01











  • I'm not opening SSMS for days, I open only like few hours. I was editing a stored procedure, no other windows open.

    – rcs
    Apr 5 '17 at 5:34











  • Even when I close all the query tabs, the problem still persists. Needs to close the entire SSMS and reopen.

    – rcs
    Apr 5 '17 at 5:47











  • use ETW to trace CPU and memory usage

    – magicandre1981
    Apr 5 '17 at 15:13











  • have you analyzed the CPU/memory usage with xperf/WPR/WPA?

    – magicandre1981
    Apr 11 '17 at 14:40














1












1








1








I have a weird problem with SQL Server Management Studio, version 11.0.2100.60. When I was writing some query, sometimes the CPU gets hogged, and RAM usage keeps increasing.
Usually closing and reopening SSMS will solve the problem, but it is quite annoying if I have to do this multiple times.



How to solve this issue?



enter image description here



[UPDATE]: I ran the PerfView to analyze the CPU usage. But I'm not quite sure how to troubleshoot from there:



PerfView CPU Stacks, showing ssms using a lot of CPU resource:
enter image description here



Drilling down Ssms. Looks like this ntdll is taking the most resource:
enter image description here



GC Heap Net Mem (Coarse Sampling):
enter image description here










share|improve this question
















I have a weird problem with SQL Server Management Studio, version 11.0.2100.60. When I was writing some query, sometimes the CPU gets hogged, and RAM usage keeps increasing.
Usually closing and reopening SSMS will solve the problem, but it is quite annoying if I have to do this multiple times.



How to solve this issue?



enter image description here



[UPDATE]: I ran the PerfView to analyze the CPU usage. But I'm not quite sure how to troubleshoot from there:



PerfView CPU Stacks, showing ssms using a lot of CPU resource:
enter image description here



Drilling down Ssms. Looks like this ntdll is taking the most resource:
enter image description here



GC Heap Net Mem (Coarse Sampling):
enter image description here







memory cpu ssms sql-server-2012






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 19 '17 at 2:02







rcs

















asked Apr 5 '17 at 3:26









rcsrcs

4003822




4003822













  • its not really unusual for monolithic tools like Visual Studio or SMSS to take up a GB or more of ram, especially if you leave them open for days or weeks at a time as I do. for the CPU, are you typing SQL code, or do you have designer windows open? have you used the "edit top 200" or anything like that which keeps connections open for long periods?

    – Frank Thomas
    Apr 5 '17 at 4:01











  • I'm not opening SSMS for days, I open only like few hours. I was editing a stored procedure, no other windows open.

    – rcs
    Apr 5 '17 at 5:34











  • Even when I close all the query tabs, the problem still persists. Needs to close the entire SSMS and reopen.

    – rcs
    Apr 5 '17 at 5:47











  • use ETW to trace CPU and memory usage

    – magicandre1981
    Apr 5 '17 at 15:13











  • have you analyzed the CPU/memory usage with xperf/WPR/WPA?

    – magicandre1981
    Apr 11 '17 at 14:40



















  • its not really unusual for monolithic tools like Visual Studio or SMSS to take up a GB or more of ram, especially if you leave them open for days or weeks at a time as I do. for the CPU, are you typing SQL code, or do you have designer windows open? have you used the "edit top 200" or anything like that which keeps connections open for long periods?

    – Frank Thomas
    Apr 5 '17 at 4:01











  • I'm not opening SSMS for days, I open only like few hours. I was editing a stored procedure, no other windows open.

    – rcs
    Apr 5 '17 at 5:34











  • Even when I close all the query tabs, the problem still persists. Needs to close the entire SSMS and reopen.

    – rcs
    Apr 5 '17 at 5:47











  • use ETW to trace CPU and memory usage

    – magicandre1981
    Apr 5 '17 at 15:13











  • have you analyzed the CPU/memory usage with xperf/WPR/WPA?

    – magicandre1981
    Apr 11 '17 at 14:40

















its not really unusual for monolithic tools like Visual Studio or SMSS to take up a GB or more of ram, especially if you leave them open for days or weeks at a time as I do. for the CPU, are you typing SQL code, or do you have designer windows open? have you used the "edit top 200" or anything like that which keeps connections open for long periods?

– Frank Thomas
Apr 5 '17 at 4:01





its not really unusual for monolithic tools like Visual Studio or SMSS to take up a GB or more of ram, especially if you leave them open for days or weeks at a time as I do. for the CPU, are you typing SQL code, or do you have designer windows open? have you used the "edit top 200" or anything like that which keeps connections open for long periods?

– Frank Thomas
Apr 5 '17 at 4:01













I'm not opening SSMS for days, I open only like few hours. I was editing a stored procedure, no other windows open.

– rcs
Apr 5 '17 at 5:34





I'm not opening SSMS for days, I open only like few hours. I was editing a stored procedure, no other windows open.

– rcs
Apr 5 '17 at 5:34













Even when I close all the query tabs, the problem still persists. Needs to close the entire SSMS and reopen.

– rcs
Apr 5 '17 at 5:47





Even when I close all the query tabs, the problem still persists. Needs to close the entire SSMS and reopen.

– rcs
Apr 5 '17 at 5:47













use ETW to trace CPU and memory usage

– magicandre1981
Apr 5 '17 at 15:13





use ETW to trace CPU and memory usage

– magicandre1981
Apr 5 '17 at 15:13













have you analyzed the CPU/memory usage with xperf/WPR/WPA?

– magicandre1981
Apr 11 '17 at 14:40





have you analyzed the CPU/memory usage with xperf/WPR/WPA?

– magicandre1981
Apr 11 '17 at 14:40










3 Answers
3






active

oldest

votes


















1














The problem is here with Intelligence. I had a same problem today. After opening a 60kb of SQL file in SSMS, it is taking nearly 2GB of my RAM.



Anyway I figured it out. This is because the incomplete code or Joins written in that query window. If I comment out that incomplete code snippet it became normal. Check for the joins which are not closed ON condition etc or comment it out until you finish writing it.




You can see that in below pictures, memory observations before and
after commenting incomplete code. It came to 128MB from 1.2GB




With Incomplete code



enter image description here



After commenting code
enter image description here






share|improve this answer
























  • For my case, after I wait for some time, the memory usage will come back to normal. But this is frustrating as I have to waste my time. So I decided to turn off the Intellisense instead.

    – rcs
    Nov 30 '17 at 8:44











  • Working without intelligence is so pathetic.. its ok

    – Shakeer Mirza
    Nov 30 '17 at 9:34






  • 1





    Smaller, more modular files will also help.

    – jerrylagrou
    Feb 14 '18 at 21:21



















0














I managed to bring it down from 2.5 GB to 150KB by disabling Auto Recover.



Auto-Recover Setting



Before
Before



After
After






share|improve this answer

































    0














    I can confirm that intellisense can cause memory leaks. close all query windows, and if the memory is still increasing, go to options to turn off Intellisense.
    You can put it back on once the memory has settled.
    options screenshot
    This issue can be avoided by never leaving an error untouched for long periods of time in a query window, especially with large queries. Comment out pieces of code that are incomplete when you are working elsewhere.





    share








    New contributor




    jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      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%2fsuperuser.com%2fquestions%2f1195570%2fsql-server-management-studio-cpu-and-ram-usage-keeps-increasing-for-no-reason%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      The problem is here with Intelligence. I had a same problem today. After opening a 60kb of SQL file in SSMS, it is taking nearly 2GB of my RAM.



      Anyway I figured it out. This is because the incomplete code or Joins written in that query window. If I comment out that incomplete code snippet it became normal. Check for the joins which are not closed ON condition etc or comment it out until you finish writing it.




      You can see that in below pictures, memory observations before and
      after commenting incomplete code. It came to 128MB from 1.2GB




      With Incomplete code



      enter image description here



      After commenting code
      enter image description here






      share|improve this answer
























      • For my case, after I wait for some time, the memory usage will come back to normal. But this is frustrating as I have to waste my time. So I decided to turn off the Intellisense instead.

        – rcs
        Nov 30 '17 at 8:44











      • Working without intelligence is so pathetic.. its ok

        – Shakeer Mirza
        Nov 30 '17 at 9:34






      • 1





        Smaller, more modular files will also help.

        – jerrylagrou
        Feb 14 '18 at 21:21
















      1














      The problem is here with Intelligence. I had a same problem today. After opening a 60kb of SQL file in SSMS, it is taking nearly 2GB of my RAM.



      Anyway I figured it out. This is because the incomplete code or Joins written in that query window. If I comment out that incomplete code snippet it became normal. Check for the joins which are not closed ON condition etc or comment it out until you finish writing it.




      You can see that in below pictures, memory observations before and
      after commenting incomplete code. It came to 128MB from 1.2GB




      With Incomplete code



      enter image description here



      After commenting code
      enter image description here






      share|improve this answer
























      • For my case, after I wait for some time, the memory usage will come back to normal. But this is frustrating as I have to waste my time. So I decided to turn off the Intellisense instead.

        – rcs
        Nov 30 '17 at 8:44











      • Working without intelligence is so pathetic.. its ok

        – Shakeer Mirza
        Nov 30 '17 at 9:34






      • 1





        Smaller, more modular files will also help.

        – jerrylagrou
        Feb 14 '18 at 21:21














      1












      1








      1







      The problem is here with Intelligence. I had a same problem today. After opening a 60kb of SQL file in SSMS, it is taking nearly 2GB of my RAM.



      Anyway I figured it out. This is because the incomplete code or Joins written in that query window. If I comment out that incomplete code snippet it became normal. Check for the joins which are not closed ON condition etc or comment it out until you finish writing it.




      You can see that in below pictures, memory observations before and
      after commenting incomplete code. It came to 128MB from 1.2GB




      With Incomplete code



      enter image description here



      After commenting code
      enter image description here






      share|improve this answer













      The problem is here with Intelligence. I had a same problem today. After opening a 60kb of SQL file in SSMS, it is taking nearly 2GB of my RAM.



      Anyway I figured it out. This is because the incomplete code or Joins written in that query window. If I comment out that incomplete code snippet it became normal. Check for the joins which are not closed ON condition etc or comment it out until you finish writing it.




      You can see that in below pictures, memory observations before and
      after commenting incomplete code. It came to 128MB from 1.2GB




      With Incomplete code



      enter image description here



      After commenting code
      enter image description here







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Nov 30 '17 at 8:21









      Shakeer MirzaShakeer Mirza

      1113




      1113













      • For my case, after I wait for some time, the memory usage will come back to normal. But this is frustrating as I have to waste my time. So I decided to turn off the Intellisense instead.

        – rcs
        Nov 30 '17 at 8:44











      • Working without intelligence is so pathetic.. its ok

        – Shakeer Mirza
        Nov 30 '17 at 9:34






      • 1





        Smaller, more modular files will also help.

        – jerrylagrou
        Feb 14 '18 at 21:21



















      • For my case, after I wait for some time, the memory usage will come back to normal. But this is frustrating as I have to waste my time. So I decided to turn off the Intellisense instead.

        – rcs
        Nov 30 '17 at 8:44











      • Working without intelligence is so pathetic.. its ok

        – Shakeer Mirza
        Nov 30 '17 at 9:34






      • 1





        Smaller, more modular files will also help.

        – jerrylagrou
        Feb 14 '18 at 21:21

















      For my case, after I wait for some time, the memory usage will come back to normal. But this is frustrating as I have to waste my time. So I decided to turn off the Intellisense instead.

      – rcs
      Nov 30 '17 at 8:44





      For my case, after I wait for some time, the memory usage will come back to normal. But this is frustrating as I have to waste my time. So I decided to turn off the Intellisense instead.

      – rcs
      Nov 30 '17 at 8:44













      Working without intelligence is so pathetic.. its ok

      – Shakeer Mirza
      Nov 30 '17 at 9:34





      Working without intelligence is so pathetic.. its ok

      – Shakeer Mirza
      Nov 30 '17 at 9:34




      1




      1





      Smaller, more modular files will also help.

      – jerrylagrou
      Feb 14 '18 at 21:21





      Smaller, more modular files will also help.

      – jerrylagrou
      Feb 14 '18 at 21:21













      0














      I managed to bring it down from 2.5 GB to 150KB by disabling Auto Recover.



      Auto-Recover Setting



      Before
      Before



      After
      After






      share|improve this answer






























        0














        I managed to bring it down from 2.5 GB to 150KB by disabling Auto Recover.



        Auto-Recover Setting



        Before
        Before



        After
        After






        share|improve this answer




























          0












          0








          0







          I managed to bring it down from 2.5 GB to 150KB by disabling Auto Recover.



          Auto-Recover Setting



          Before
          Before



          After
          After






          share|improve this answer















          I managed to bring it down from 2.5 GB to 150KB by disabling Auto Recover.



          Auto-Recover Setting



          Before
          Before



          After
          After







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 23 '18 at 10:45









          Toto

          3,857101226




          3,857101226










          answered Jun 23 '18 at 10:18









          Prashant GuptaPrashant Gupta

          11




          11























              0














              I can confirm that intellisense can cause memory leaks. close all query windows, and if the memory is still increasing, go to options to turn off Intellisense.
              You can put it back on once the memory has settled.
              options screenshot
              This issue can be avoided by never leaving an error untouched for long periods of time in a query window, especially with large queries. Comment out pieces of code that are incomplete when you are working elsewhere.





              share








              New contributor




              jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                0














                I can confirm that intellisense can cause memory leaks. close all query windows, and if the memory is still increasing, go to options to turn off Intellisense.
                You can put it back on once the memory has settled.
                options screenshot
                This issue can be avoided by never leaving an error untouched for long periods of time in a query window, especially with large queries. Comment out pieces of code that are incomplete when you are working elsewhere.





                share








                New contributor




                jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  0












                  0








                  0







                  I can confirm that intellisense can cause memory leaks. close all query windows, and if the memory is still increasing, go to options to turn off Intellisense.
                  You can put it back on once the memory has settled.
                  options screenshot
                  This issue can be avoided by never leaving an error untouched for long periods of time in a query window, especially with large queries. Comment out pieces of code that are incomplete when you are working elsewhere.





                  share








                  New contributor




                  jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  I can confirm that intellisense can cause memory leaks. close all query windows, and if the memory is still increasing, go to options to turn off Intellisense.
                  You can put it back on once the memory has settled.
                  options screenshot
                  This issue can be avoided by never leaving an error untouched for long periods of time in a query window, especially with large queries. Comment out pieces of code that are incomplete when you are working elsewhere.






                  share








                  New contributor




                  jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share


                  share






                  New contributor




                  jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 8 mins ago









                  jeroenymojeroenymo

                  1




                  1




                  New contributor




                  jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  jeroenymo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • 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%2fsuperuser.com%2fquestions%2f1195570%2fsql-server-management-studio-cpu-and-ram-usage-keeps-increasing-for-no-reason%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

                      VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                      Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

                      looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...