Application has a stored procedure that executes a massive delete (millions of records) all at one time which causes a huge transaction log. CANNOT modify stored proc (to break up delete into batches) - vendor restrictions.
SQL Server 2019 / Simple Recovery Model
Does anyone have an alternate approach to manage the transaction log growth when this stored proc runs?
tablock
, then re-enable them after.