Eugene

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Eugene commented  · 

    UPDATE. I have moved same rows in SQL Server 2017. Result: memory taken: ≈100MB. Memory released: NO!

    Eugene shared this idea  · 
  2. 111 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    56 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Eugene commented  · 

    SSMS usage becomes more irritating

    Eugene supported this idea  · 
  3. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Could you try to capture a dump of the process when it dies?

    1. Download ProcDump (https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx)
    2. Unzip the download into a folder of your choosing
    3. Open a cmd prompt (Win+R, type cmd, hit enter)
    4. Run the following command:

    \procdump.exe -e -h -ma -w ssms.exe

    (It should prompt you to accept a license agreement, click Agree)

    5. Start SSMS if not started already
    6. Repro issue
    7. Text should appear in the cmd prompt about writing the dump file, wait for that to finish
    8. Create a new folder and copy the *.dmp file that is written out to that folder
    9. Copy the following files into the same folder
    “C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll”
    “C:\Windows\Microsoft.NET\Framework\v4.0.30319\SOS.dll”
    “C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll”
    Zip up the folder and share it (OneDrive, etc…)

    Thanks,
    -Matteo

    Eugene commented  · 
    Eugene supported this idea  · 
  4. 42 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    28 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    I’m looking into this issue.

    In the meanwhile, could you take a look at the SSMS setup logs (%TEMP%\SSMSSetup\SSMS-Setup-ENU_20190430231104.log). I’m interested in the lines in the range 133-216. Could you share those (tip: have a look at the lines and sanitize them, if you think they may contain sensible information?

    Also, if you could share the output of:
    reg query “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32 /s

    And, finally, to unblock yourself:
    1) Make sure you don’t have any previous version (RC, Preview) of SSMS 18.0 installed (check Add/Remove programs; if you do, uninstall it)
    2) Make sure “C:\Program Files (x86)\Microsoft SQL Server Management Studio 18” does not exist (if it does, the delete it)
    3) Delete the mentioned registry key (e.g. by running from an elevated cmd prompt:
    reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32)
    4) Retry setup
    Please, let…

    Eugene commented  · 

    I had reinstall OS in order to install it since I couldn't wait for such long time for the response. After reinstalling OS everything went fine. The thread can be closed.

    Eugene supported this idea  · 
    Eugene shared this idea  · 
  5. 229 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Eugene supported this idea  · 

Feedback and Knowledge Base