3:10 "Just switch to log shipping" I realise the question mentions the purpose of having the replicas is for DR, so as you mentioned log shipping would probably be a better approach. If they wish to also use the replicas for read-only purposes, wouldn't using read-scale AG become the better option? With log shipping your data will always be behind in accordance to the log backup schedule, and when log restores happen, users reading the db would get kicked out.
ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-g6fqxTPnDd0.html: I have seen this happen when the proc contains a for loop that does a bunch of stuff for each row returned in a previous query. The painting of the execution plan takes forever and in some instances can blow out memory in SSMS. Imagine a loop that runs 5 queries and has to do this for 200 rows.
