We noticed RedGate isn't showing CU10 for SQL Server 2022, which was released on 11/16 (13 days ago). I noticed it's not listed in assets.red-gate.com/products/dba/sql-monitor/assets/files/SqlServerVersions.json . I know there's usually a little delay, but this one seems longer than usual? Anyone have insight on it?
Comments
6 comments
-
Hi,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 on the server SQL Monitor Web is installed. SQL Monitor will read the updated file within 6 hours. However, if necessary, you can force an update by restarting the SQL Monitor Web Service or the site in IIS.Please let us know if this helps.Best Regards,Sujay
-
Thanks Sujay. Appreciate the info. I suppose I can download and manually add this record to the file? Any insight as to why it's not in the file yet? It was released 18 days ago.{"Edition": "2022","ProductLevel": "RTM CU10","Version": "16.0.4095.4","ReleaseDate": "2023-11-16","EndOfSupportDate": "2028-01-11","EndOfExtendedSupportDate": "2033-01-11","DownloadUrl": "https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate10"}
-
Thanks Andy.I see what you are saying now. The file itself does not contain the latest update.I will get this checked with my colleagues and let you know once the file is updated.This should then reflect in SQL Monitor.Best Regards,Sujay
-
Thanks Sujay,
Just curious if there's a rhyme or reason for the delay and/or based on the process of how the file gets updated, what kind of delay is "typical?"
Thanks again,
Andy -
Hi Andy,The file is now updated and you should be able to see the CU10 for SQL Server 2022 at https://www.red-gate.com/products/dba/sql-monitor/assets/sql-server-versions.jsonUsually any new updates get reflected in a couple of days. This was somehow missed for the CU10.Going forward though, this is unlikely to take longer than a couple of days to reflect new updates.Please let me know if this change is reflected in your environment.(Auto-update usually takes about 6 hours. Restarting the services might reflect the change immediately.)
-
Thanks Sujay. Change is reflected in our environment. We had already patched our 2022 SQL Servers and they now show RTM CU10 as opposed to >RTM CU9. Appreciate the attention and the info.
Add comment
Please sign in to leave a comment.