We used to have cases where our customer faced the following error message: "A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)" in this video below we are going to give some insights about it.
Why this issue happens?
- Connection dropped from SQL Server or network issue during execution of a query.
How to fix the issue?
- Reopen the connection and Retry the TSQL operation.
- Look for network issues.
- Check performance on application server.
- Check performance on database server.
- Tune and optimize your queries as this will help with request limit issues in future. Review this article Lesson Learned #119: What is the query that my stored procedure is running now? - Microsoft Tech Com...
- Review the indexes rebuild and update statistics using How to maintain Azure SQL Indexes and Statistics - Microsoft Tech Community
- You can apply recommendations from portal to improve query performance or review the missing indexes. Review this link to obtain all the best practices - Lesson Learned #195: Performance Best Practices for Azure SQL Database and Managed Instance. - Micro...
- If you need to test your worload review this link: Lesson Learned #196: Latency and execution time in Azure SQL Database and Azure SQL Managed Instance...
Enjoy!
Updated Jun 28, 2022
Version 2.0Jose_Manuel_Jurado
Microsoft
Joined November 29, 2018
Azure Database Support Blog
Follow this blog board to get notified when there's new activity