Feeds:
Posts
Comments

Posts Tagged ‘ado-net’

When my ADO.NET Data Services web service started throwing SqlCommand timeout messages I hit up Google and finally found a post in German(?) that pointed me in the right direction. The problem seems to be the Entity Framework Connection CommandTimeout, which can be easily modified overloading the OnStartProcessingRequest event.

When working with the ADO.NET Data Services (aka Astoria) we eventually get to the point that the tasks become more complicated and increases the load on the server. In solchen Situationen ist man mit potentiellen Timeouts in allen Ebenen konfrontiert. In such situations one is confronted with potential time-outs at all levels. In diesem Post zeige ich welche Timeouts es gibt, aber speziell will ich zeigen wie ich das Timeout des Entity Frameworks (SQL) in Kombination mit der MS REST Schicht ADO.NET Data Services anpassen kann. In this post I will show that there is a timeout, but specifically I want to show how the timeout of the Entity Framework (SQL) in combination with the MS REST can adjust layer ADO.NET Data Services.

ADO.NET Data Services, Entity Framework, and SQL / HTTP Timeouts

Read Full Post »

ADO.NET Data Services provides filtering options for free.

What can go in a $filter? The most basic thing to do is to test properties of the resources we’re returning, which you can access simply by name, like we have done above. Literals for things like strings and numbers use the same syntax as in the key portion (see my last post and the original URL post for more details).

via Marcelo’s WebLog : $filter Query Option in ADO.NET Data Services.

Read Full Post »

Need to debug an ADO.NET Data Service?

Another interesting point has to do with error handling. The option for error handling is set during InitializeService. If an exception is thrown while InitializeService is being called, we don’t trust whatever was set on the configuration, and instead of the ADO.NET Data Service error handling kicking in, we’ll let the exception bubble out. Typically the service will be running as a WCF service, which means you’ll get the error page with the blue band on top (when viewed in a browser). To get detailed errors in this case, you can do something like this.

[System.ServiceModel.ServiceBehavior(IncludeExceptionDetailInFaults = true)]

public class YourService : DataService

{ … }

via Marcelo’s WebLog : So Special – InitializeService in ADO.NET Data Services.

Read Full Post »