Timeout Expired on SQL Azure; cannot be reproduced on-premise SQL Server [closed]
If you need to do SQL intensive work (for instance, a lot of INSERT statements in a normalized OLTP database) you need to have fail-over logic in your code.
On-premise SQL server will not suffer from this, so take this into consideration before switching to SQL Azure.
These two articles inspired me (special thanks to Joachim Isaksson for guidance):
http://blogs.msdn.com/b/sqlazure/archive/2010/05/11/10011247.aspx
To sum of the result, I have provided the two results which is now identical in result (where before some records where not added do to missing fail-over logic in regards to the original question: Timeout Expired):
On-premise SQL Server: 179.285 records in 427 seconds
SQL Azure w. fail-over logic: 179.285 records in 2.247 seconds - a whooping 5.2 times slower!
I hope this can help others struggling with SQL Azure. On a positive note; you learn (the hard way) that you have been lucky and privileged on your native in-house applications :-)
Note: i would still like an explanation how this can happen .. seems to easy to blame on latency, no?