How can we help you today? How can we help you today?

Setting up frequent updates if all you have is SSMS 2017?

Just built a new machine, and installed SSMS 2017 as default. It works a treat :)

Naturally I now want to run SQL source control, but can't - I've installed the latest version in the bundle (5.4?), though that doesn't work in SSMS 2017. I can see that 5.5 fixes this, though I can't get into SQL source control to switch on frequent updates in order to get the update?

Please tell me I don't have to install a lower version of SSMS just to switch on frequent updates?

Yours in hope! lol
Terry
terry_brown
0

Comments

10 comments

Sort by
  • terry_brown
    Ignore me - found the link to the FTP site: ftp://support.red-gate.com/patches/SQLSourceControl/

    will try a version from there.
    terry_brown
    0
  • mmelvin
    I also am having this problem. Even the 5.5.7 installer from the FTP site refuses to install because it can't find an old version of SSMS.
    mmelvin
    0
  • Andrew P
    Hey mmelvin,

    Thanks for contacting us!
    It does not support SSMS 2005 and older - what version(s) of SSMS are you on currently?
    Do you have SQL Source Control installed already?

    Warm Regards,
    Andrew P
    0
  • mmelvin
    I, like the original poster, am using SSMS 2017 (final, not RC). I do not currently have SQL Source Control installed because I can't. Neither the SQL Toolbelt installer nor the SQL Source Control 5.5.7 installer from FTP will recognize that I have SSMS installed.

    Edit: But other products, like SQL Prompt, are functioning just fine with SSMS 2017.
    mmelvin
    0
  • Jessica R
    Hi mmelvin,

    Hm that's an odd one - when the installer fails, can you please right-click on the title bar of the installer, choose Log File, and send us the content? That will hopefully have more detail on what's going wrong.
    Jessica R
    0
  • mmelvin
    I have submitted a support request with the log attached.
    mmelvin
    0
  • Jessica R
    Thanks mmelvin!

    We have this logged internally as SOC-8801 - it will happen when you have SSMS 17 on a system that never had another version of SSMS installed before.

    This should be resolved in the next release--please bear with us and I'll post here once it's available!
    Jessica R
    0
  • mmelvin
    Thank you.
    mmelvin
    0
  • Mike U
    This bug is now fixed in version 5.6.1, and you can download it directly from the updates server here
    Mike U
    0
  • mmelvin
    Looks good. Thanks!
    mmelvin
    0

Add comment

Please sign in to leave a comment.