Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Depending on how much compute you have in front of your database I would put in a limit on the connection pools that can be created with connection string.</p> <p>Trying setting if for example you have 2 compute in front of the database. </p> <p>Max Pool Size=70; </p> <p>SQL Database can only handle 180 connections this is a hard limit. You can find for example when you are hitting the connection limit a retry framework will make the matter worse as it will try to connecting for a period of time leading to further downtime. This might be the reason you see several minutes as the compute retry frameworks give up.</p> <p><a href="http://msdn.microsoft.com/en-us/library/windowsazure/ff394114.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/windowsazure/ff394114.aspx</a></p> <p>Have a look with the following: </p> <pre> -- monitor connections SELECT e.connection_id, s.session_id, s.login_name, s.last_request_end_time, s.cpu_time FROM sys.dm_exec_sessions s INNER JOIN sys.dm_exec_connections e ON s.session_id = e.session_id GO </pre> <p>You should try to add cache to you application design, this can greatly reduce you application over head on the database and is recommend practice with SQL Azure. Especially as you can have connection issues. I have seen this type of issue before and it was connection limits so maybe worth investigating a bit of time in that direction to see if that causes. If not I would open a ticket to MS Support. </p> <p>hths, Goodluck. </p> <p>EDIT: Premium Database obviously raise the limits on connections so worth of investigation also as quick fix to this issue and potentially a long run one. </p> <p><a href="http://blogs.technet.com/b/dataplatforminsider/archive/2013/07/23/premium-preview-for-windows-azure-sql-database-now-live.aspx" rel="nofollow">http://blogs.technet.com/b/dataplatforminsider/archive/2013/07/23/premium-preview-for-windows-azure-sql-database-now-live.aspx</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload