Malcolm Smith

My feedback

  1. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Additional Services  ·  Flag idea as inappropriate…  ·  Admin →
    Malcolm Smith supported this idea  · 
  2. 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…

    Malcolm Smith commented  · 

    For me the I believe the root cause was an unexpected reboot as SSMS installed and had not completed.
    With Linux SQL Container I am prone to Hyper-V stop error (blue screen) reboots as well.

    It seams the install hadn't updated the registry before the reboot, maybe if this is an initial check the values could be added sooner, e.g. at point of check if missing only.

    The only registry entries i can see in path you suggest to delete is
    .\18\SSMSInstallRoot
    Not under the local user for 18.0 but entries for older 'sql specific' versions up to 14

    Malcolm Smith supported this idea  · 
  3. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Malcolm Smith commented  · 

    There is alos a use case for tSQLt CI deployments.
    Having a test DB project referncing the DB under test and tSQLt command needs to create the Test Class aka Schema that the Test Cases aka Procedure are created in.
    I tried to add the creation of the Schema into the Pre-Deploy script but the docker build publish still tries to CREATE SCHEMA [mySchema] create in the Pre-Deploy script.

    Malcolm Smith supported this idea  · 

Feedback and Knowledge Base