ACCELERATED_DATABASE_RECOVERY and increase in database size

Question

Post reply

ACCELERATED_DATABASE_RECOVERY and increase in database size

abdalah.mehdoini

Ten Centuries

Points: 1012
More actions
September 4, 2022 at 11:02 am

#4083756

Hello ,
I am looking please for your feedback on the activation of "ACCELERATED_DATABASE_RECOVERY" In SQL server 2019
Especially on the size of the database
because I'm worried if I see this
https://www.sqlservercentral.com/forums/topic/sql-server-2019-bug-databases-auto-growing-out-of-control
Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80330 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 2

Current for SQL2019 is CU17 ! Make sure you're keeping up with these cumulative updates ! They fix a lot, but you'll have to test !

Also: check "Manage Accelerated Database Recovery"

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Jeff Moden SSC Guru Points: 1004340 More actions · Answer 3

Johan Bijnens wrote:

Make sure you're keeping up with these cumulative updates ! They fix a lot, but you'll have to test !

It's almost humorous as to the amount of irony in those statements. I appreciate fixes but if MS spent more time on testing, there wouldn't be such a need to create and test so many fixes and neither would we.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 4

Jeff Moden wrote:

Johan Bijnens wrote:
Make sure you're keeping up with these cumulative updates ! They fix a lot, but you'll have to test !
It's almost humorous as to the amount of irony in those statements. I appreciate fixes but if MS spent more time on testing, there wouldn't be such a need to create and test so many fixes and neither would we.

Totally with you, Jeff.