The next morning, the team asked how I fixed it. I said, "SQL Studio 2014 – same tool you've been ignoring." They laughed.
But the server hummed a little quieter that day. And somewhere in the logs, a 2014 query plan smiled. Tools age, but fundamentals don't. Execution plans, indexing, statistics, and parameter sniffing – SSMS 2014 forced you to know them. And knowing them still saves the day.
CREATE NONCLUSTERED INDEX IX_FactSales_OrderDate_Include ON Sales.FactSales (OrderDate) INCLUDE (CustomerID, ProductID, Revenue); sql studio 2014
I opened (right-click server instance in Object Explorer). Saw the batch requests/sec spike, then settle. No blocking. No heavy waits. Perfect.
But the data was reborn.
While waiting for a backup restore, I right-clicked the database in Object Explorer. . Changed it to 120 (SQL Server 2014). Then I right-clicked a particularly slow view – "Show Estimated Execution Plan".
I closed SSMS 2014. The splash screen flashed for a second – the classic blue SQL Server logo. I saved my session (Session > Save as .sql) into a folder called Phoenix_Fixes . No Git. No CI/CD. Just a network drive and a prayer. The next morning, the team asked how I fixed it
Suddenly, the query ran again – 40 seconds. What? I checked the execution plan. Same indexes. Then I remembered: parameter sniffing. SQL Server 2014 didn't have the automatic plan forcing of later versions. I added OPTION (RECOMPILE) to the stored procedure and added WITH RECOMPILE to a frequently called function.