From what I've heard, there's no "official" connection upper limit, but it's more of a "play nice with others" scenario - if you start consuming all of the server's resources, you're throttled. Sounds like a fun exercise to try... :)
Marked as answer bystombiztalkerTuesday, September 7, 2010 1:19 PM
SQL Azure doesn't have a connection limit per se... You should try to pool your connections and close them when not in use (connections time out after, I think, 30 minutes anyway). However, if you start opening a ton of connections, you'll likely be throttled
at some point. I can't recall the specific error related to this, but as long as you're reusing / pooling connections, chances are, you won't experience throttling.
From what I've heard, there's no "official" connection upper limit, but it's more of a "play nice with others" scenario - if you start consuming all of the server's resources, you're throttled. Sounds like a fun exercise to try... :)
Marked as answer bystombiztalkerTuesday, September 7, 2010 1:19 PM