The stored procedure ran fine in SSMS — under 1 second, every time. But through the .NET API? 30–120 seconds. Timeouts. Errors.

📰 Dev.to · ahmedmohamedhussein

Optimize SQL stored procedures for .NET API calls to prevent timeouts and errors

intermediate Published 27 Apr 2026

Action Steps

Analyze the execution plan of the stored procedure in SSMS using the Query Store
Compare the execution plan with the one generated by the .NET API call
Identify potential parameter sniffing issues and optimize the stored procedure accordingly
Use the Database Engine Tuning Advisor to recommend indexing and statistics updates
Test the optimized stored procedure with the .NET API to ensure improved performance

Who Needs to Know This

Database administrators and .NET developers can benefit from understanding the differences in execution plans between SSMS and .NET API calls to optimize their database queries

Key Insight

💡 Parameter sniffing can cause differences in execution plans between SSMS and .NET API calls, leading to performance issues