title: Azure Functions static SqlConnection - right way to scale?
body: <p>I'm using Azure Functions with queue triggers for part of our workload. The specific function queries the database and this creates problems with scaling since the large concurrent number of function instances pinging the db results in maximum allowed number of Azrue DB connections being hit constantly. </p>
  
  <p>This article <a href="https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections" rel="noreferrer">https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections</a> lists HttpClient as one of those resources that should be made static.
  Should database access also be made static with static SqlConnection to resolve this issue, or would that cause some other problems by keeping the constant connection object?</p>