A stored procedure on an Azure SQL Database has been running quickly for months, but after a recent statistics update it intermittently runs 20x slower depending on which parameter value is passed first. Using Query Store, you confirm the procedure has two execution plans: an older plan that performs well for all parameter values and a newer plan that only performs well for a narrow range. You need an immediate mitigation that keeps the good plan in use while you investigate a permanent fix, without changing application code. What should you do?