Hi,
Seems from other user's experience , this error should be fixed with SQL Server 2019 CU2 - 15.0.34.1 . (The lasted post in the thread you post.)
Further more, since you have the SQL Server RTM version, I would suggest to your to upgrade to latest CU, that is Cumulative Update 8 for SQL Server 2019 . These updates contain several updates and fixes, I highly recommend to upgrade it.
Regards,
Lukas
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
What can I do if my transaction log is full?--- Hot issues November
How to convert Profiler trace into a SQL Server table -- Hot issues November