The place where the command timeout is set is no longer the same as earlier versions.
However, I cannot find anywhere that says how to change this.
What I am doing is uploading very large files which takes longer than the default 30 seconds to save.
Note that I ask about command timeout, not migration timeout as in another question.
If you're using the DI container to manage the DbContext (i.e. you're adding the DbContext to the service collection), the command timeout can be specified in the options.
In Startup.ConfigureServices:
services.AddDbContext<YourDbContext>(options => options.UseSqlServer(
this.Configuration.GetConnectionString("YourConnectionString"),
sqlServerOptions => sqlServerOptions.CommandTimeout(60))
);
you can change it through your context
public class ApplicationDbContext : DbContext
{
public ApplicationDbContext()
{
Database.SetCommandTimeout(150000);
}
}
Database property of an injected context make sure you add using Microsoft.EntityFrameworkCore; since SetCommandTimeout is an extension method.If you would like a temporary increase timeout only for one Context instance.
Let's say for 1 request (default Scoped context lifetime)
Change this before long running query:
Context.Database.SetCommandTimeout(TimeSpan.FromMinutes(20))
With scoped lifetime you can specify timeout only once and you do not have to specify it in any subsequent services constructors injections.
SetCommandTimeout is scoped only to the one context provided via DI and not to every instance of the context? Do you have a reference to documentation to support this?
DbContext.Database specifically say Creates a Database instance **for this context** that allows for creation/deletion/existence checks for the underlying database., so yes it is just for one context. learn.microsoft.com/en-us/dotnet/api/…In EF Core 3 and above, you can now configure this via connection string. But you need to migrate from 'System.Data.SqlClient' to 'Microsoft.Data.SqlClient'.
Replace System.Data.SqlClient with Microsoft.Data.SqlClient version 2.1.0 or greater.
Then in your connection string simply append the command timeout like so:
"Data Source=SqlExpress;Initial Catalog=YourDatabase;Integrated Security=true;Command Timeout=300"
This will only work with Microsoft.Data.SqlClient 2.1.0 or above, you will get exception if you try this with System.Data.SqlClient.
The better option is to use CommandTimeout during your context setup like:
public class DbConnect: IConnnectDb
{
private dbentitient _context;
// inject this to a db entity from constructor.
//inside each method now use the follow before u actually run the query to db.
_context.Database.SetCommandTimeout(400);
}
Note: EF Core will only execute the query with less than 100 seconds time. If it's more than that it keeps retrying and you never get to see the result.
That's my experience as of now, so let me know if you are able to fix it EF Core 1.0 does timeout even more fast than EF Core 2.0.
Database.SetCommandTimeout