In SQL Server 2017, automatic plan correction was added, which allows for the database engine to automatically use the "last known good plan" for a query that has suddenly regressed in performance.

Using T-SQL, there's an extended stored procedure called xp_instance_regread. To try it out, paste the following code into Query Analyser: DECLARE @retvalue int, @data_dir varchar (500) ...