Skip to main content

Entity Framework: Timeout when initializing a database on SQL Azure

A colleague came to me with the following problem:

“I’m using Entity Framework and a DropCreateDatabaseIfModelChanges DB Initializer to setup the database. This works perfect locally on my system but when I try to use a database in SQL Azure, I always get a SqlException with the following message:  Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding." How can I fix this?

My first reaction was, don’t do this. I’m not a big fan of the DB Initializers and prefer to generate the DDL and do the rollout using my release pipeline. But during development this could save us some time. So let’s see how we can fix this…

The reason we have this issue is because the creation of a database on SQL Azure can take some time(at least more time than the default timeout(60 seconds)), explaining the Timeout expired message. So the question becomes how can we change the default timeout?

There are multiple timeout values that can play a role:

  • We have the connection timeout. This can be configured in the connection string:
<connectionStrings>
     <add name="MyContext" connectionString="Server=tcp:azure_server_name.database.windows.net,1433;Database=azure_database_name;User ID=azure_user_account@azure_server_name;Password=azure_password;Trusted_Connection=False;Encrypt=True;Connection Timeout=180"
          providerName="System.Data.SqlClient" />
</connectionStrings>
  • We have the command timeout. This can be configured inside our DBContext instance:
public MyContext() : base("name=MyContext")
{
    // three minute command timeout
    this.Database.CommandTimeout = 180;
}

DbMigrationsConfiguration.CommandTimeout=180;//Seconds

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...