SQL Server 2019 CU2 and the breaking of the SQL Server Agent
Hi Guys,
Welcome back!
Today a little post, only few minutes to stay updated.
Then following the CU philosophy, the same day Microsoft made the first cumulative update CU1 available.
In these days the second cumulative update CU2 for SQL Server 2019 is released.
I always recommend updating to the latest CU but this time an exception is around then corner.
Microsoft infact officialy comunicated that installing this CU2 on some system may cause the breaking of the SQL Server Agent. Precisely then SSMS version 18.4 fails to show SQLAgent jobs via object browser.
So what we can do?
There are two possible solutions!
Have an happy sunday!
Seen you soon
Luca
Luca Biondi @ SQLServerPerformance blog 2020!
Previoous post: The XACT_ABORT option: What it is and what it is used for, all explained in a simple way!
Welcome back!
Today a little post, only few minutes to stay updated.
SQL Server 2019 CU2
It was the beginning of november 2019 when Microsoft released the new SQL Server 2019 and we made this title: NEWS! Edizione Speciale! SQL Server 2019 è arrivato tra di noi!Then following the CU philosophy, the same day Microsoft made the first cumulative update CU1 available.
In these days the second cumulative update CU2 for SQL Server 2019 is released.
I always recommend updating to the latest CU but this time an exception is around then corner.
Microsoft infact officialy comunicated that installing this CU2 on some system may cause the breaking of the SQL Server Agent. Precisely then SSMS version 18.4 fails to show SQLAgent jobs via object browser.
So what we can do?
There are two possible solutions!
- Disinstall the CU2 update and revert to the CU1
- Wait for the next CU, the CU3
Have an happy sunday!
Seen you soon
Luca
Luca Biondi @ SQLServerPerformance blog 2020!
Previoous post: The XACT_ABORT option: What it is and what it is used for, all explained in a simple way!
Comments
Post a Comment