How do you use cloud databases? Take the survey.
Options

Estate\Installed Versions\Instances

Our estate screen is not showing the latest updates. So for example it is showing that the latest available update for SQL 2019 is CU9 15.0.4102.2 which was released in February. There have been several more updates since then which are not showing. In fact the current version is CU13 which was released this month.
Tagged:

Best Answer

  • Options
    judy_palmerjudy_palmer Posts: 5 New member
    edited February 1, 2022 8:44AM Answer ✓
    When we moved to IIS so that we could use HTTPS I disabled the Redgate monitor web service. Seems that this needs to be running to update the estate. I worked that out because it is running on our Azure Redgate server and that didn't have the same problem.

Answers

  • Options
    judy_palmerjudy_palmer Posts: 5 New member
    I have updated the jso as per these instructions:

    Versions data

    The versions data used by this page is obtained from the Redgate website and automatically updated each day. We aim to keep this up to date with the latest releases of SQL Server (for all versions that SQL Monitor supports).

    If SQL Monitor cannot download updates to this data automatically, it can be performed manually. To do this, download the latest version of the data from https://www.red-gate.com/products/dba/sql-monitor/assets/sql-server-versions.json and save it to a file at C:\ProgramData\Red Gate\SQL Monitor\SqlServerVersions.json. SQL Monitor will then pick up the updated data from this file within 6 hours.

    https://documentation.red-gate.com/sm9/estate/versioning-and-patching

     SQL monitor has not updated yet. What would stop the monitor from receiving the file automatically? It hadn't been updated for several months…
  • Options
    Hi judy_palmer

    Can the server hosting the base monitor reach https://www.red-gate.com/products/dba/sql-monitor/assets/sql-server-versions.json ? This is where SQL monitor pulls the information from. Can see in there that SQL 2019 CU13 is indeed in there. 
    The update normally occurs after 6 hours, after waiting this period did it not change? If so could you try restarting the " SQL Monitor Base Monitor" service?
    Could you also confirm which version it is you are running?
  • Options
    ATurner said:
    Hi judy_palmer

    Can the server hosting the base monitor reach https://www.red-gate.com/products/dba/sql-monitor/assets/sql-server-versions.json ? This is where SQL monitor pulls the information from. Can see in there that SQL 2019 CU13 is indeed in there. 
    The update normally occurs after 6 hours, after waiting this period did it not change? If so could you try restarting the " SQL Monitor Base Monitor" service?
    Could you also confirm which version it is you are running?
     hi Andy sorry for the late reply I have been off sick for some time. Yes the server can access that so I don't know what's going on. We are currently running quite an old version  9.2.4.24230 but are planning (when I can find time) to upgrade to the latest version. How often should it update? It is currently showing the last update date when I manually downloaded the file. When should I expect it to have updated again? I'd like to know this before I restart the base monitor service.
Sign In or Register to comment.