Hi Craig, All my tests connect to the SQL Azure DB. I'm using EF5 in a vanilla way, so that should keep me above sight of the differences in the real and Azure DBs.
I am hitting some environmental difference in the production Azure environment, but WCF is hiding the error and reporting the generic failure exception, which it does by default. I remember years ago spending hours trying to get details errors back from WCF, but it never worked properly. I found it easier to run the server in the debugger and break on the problem, but I can't do that with the service in Azure. When I get home tonight I'll just keep web searching for advice on how to tackle this problem. Maybe there is Azure-side logging as well. Greg P.S. It will interesting to see how the Azure DB performs when I load it up with 150,000 rows in 20 tables. It's currently only got a dozen test rows.
