Skip to main content
Matrix42 Self-Service Help Center

EgoSecure and usage of Microsoft Azure SQL

  1. Last updated
  2. Save as PDF

EgoSecure and usage of Microsoft Azure SQL

When the EgoSecure server is connecting to an Azure SQL database, the connection parameters might have an impact on EgoSecure performance. If the server is connecting to the Azure SQL DB using a Private Endpoint link, we strongly recommend to set the connection policy to "Redirect", and not "Proxy".

Azure SQL Databases are deployed in multi-tenant clusters. To keep the resource consumption low, idle session are killed by the Azure gateway to clean-up the connections which have been idle for 30 minutes. This connection reset occurs when the client is using proxy connection policy instead of redirect. Redirect connections bypass the gateway and its proxy, and the gateway is not managing the connection lifetime then. To avoid idle connection connection resets you need to switch the connection policy from "Proxy" or "Default" to “Redirect”.

More information is available here Microsoft Azure Private Link

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    1. Architecture
    2. Communication
    3. Database
    4. Environment
    5. Microsoft