How to add CommandTimeout to connection string in web.config

Question

How to add CommandTimeout to connection string in web.config?

I tried:

<add name="ConnectionString" connectionString="Data Source=;Initial Catalog=;Persist Security Info=True;User ID=sa;Password=sa@123;Connect Timeout=200" providerName="System.Data.SqlClient"/>

</connectionStrings>

and this:

<add name="MyProject.ConnectionString"  
         connectionString="Data Source=127.0.0.1;Initial Catalog=MyDB;Persist Security Info=True;CommandTimeout=60;User ID=sa;Password=saPassw0rd"
         providerName="System.Data.SqlClient" />

but it didnt' work for me.

Thanks

Possible duplicate of how to set the query timeout from SQL connection string — Michael Freidgeim
– Michael Freidgeim, Commented Dec 19, 2018 at 5:04

Frederik Struck-Schøning · Accepted Answer · 2020-01-07 10:19:27Z

12

I made it like this:

private readonly MyDbContext _context;

    public LinqToSql() : this(new MyDbContext())
    {
    }

    private LinqToSql(MyDbContext context)
    {
        _context = context;
        _context.CommandTimeout = 500; 

    }

edited Jan 7, 2020 at 10:19

Frederik Struck-Schøning

13.3k9 gold badges63 silver badges70 bronze badges

answered Jan 6, 2014 at 13:00

user833102

Sign up to request clarification or add additional context in comments.

Comments

Manish Singh · Accepted Answer · 2013-12-19 14:12:01Z

9

As far as I know there is no global way of setting Command timeout property, you have to set CommandTimeout property individually for each command object you create.

answered Dec 19, 2013 at 14:12

Manish Singh

1461 bronze badge

Comments

Frederik Struck-Schøning · Accepted Answer · 2020-01-07 10:19:44Z

2

You can set the timeout in a setting and refer to that value when the command timeout is set.
In config under appSettings add a key for CommandTimeout:

<add key="ContextCommandTimeout" value="500" />

Then in your code:

int cmdTimeout = -1;
string timeoutSettings = ConfigurationManager.AppSettings["ContextCommandTimeout"];

if(!string.IsNullOrEmpty(timeoutSettings)) 
{
    int.TryParse(timeoutSettings, out cmdTimeout);
}

if(cmdTimeout >=0)
    _context.CommandTimeout = cmdTimeout;

edited Jan 7, 2020 at 10:19

Frederik Struck-Schøning

13.3k9 gold badges63 silver badges70 bronze badges

answered Oct 31, 2016 at 13:10

Charles Byrne

8342 gold badges11 silver badges22 bronze badges

Comments

Michael12345 · Accepted Answer · 2022-08-08 20:28:00Z

For those still interested, as of about October 2020 it looks like this might be possible with .NET EF Core.

With the latest 2.1.0 preview 2 release of the open source .NET client driver for Microsoft SQL Server and Azure SQL Database, Microsoft.Data.SqlClient, it is now possible to set the default command timeout via the connection string.

Now you can work around timeout issues simply by changing the connection string, where this previously required changes to code, and maybe changes to code you did not have the ability to change.

This could be an issue when you were using third party tools like Entity Framework Core migrations or EF Core database reverse engineering (scaffolding).

Refer: https://erikej.github.io/sqlclient/2020/10/26/sqlclient-commandtimeout-preview.html

Frederik Struck-Schøning · Accepted Answer · 2020-01-07 10:20:23Z

0

Going to assume this is a .NET web-app, since it looks like one & it wasn't specified in the description / tags. This works for an app I've been developing, sets the DB command timeout to be 15 seconds:

<connectionStrings>
  <add name="ConnectionString" 
       connectionString="Server=localhost; Port=3306; Database=<DB>;
                         uid=<usr>; pwd=<pw>; default command timeout=15;" 
       providerName="MySql.Data.MySqlClient" />
</connectionStrings>

The default command timeout is applied app-wide to each individual DB request. As far as I'm aware, the default is 30 seconds if this isn't specified. For a web-app, individual DB commands that take longer than 30 seconds is a bit extreme though; you may be better served having a rethink of how you architected the solution.

edited Jan 7, 2020 at 10:20

Frederik Struck-Schøning

13.3k9 gold badges63 silver badges70 bronze badges

answered Oct 25, 2019 at 6:06

Lovethenakedgun

88710 silver badges27 bronze badges

2 Comments

Jordan Over a year ago

It should be noted that this only works because the MySql ConnectionStrings element allows that property. Its not available for MSSQL for instance (so not supported using System.Data.SqlClient)

Roman M Over a year ago

It doesn't work for SQL Azure

Cody Gray · Accepted Answer · 2017-08-09 17:49:21Z

-6

If you want to put it into your web.config, you need to add a space. Try:

Command Timeout=60;

instead of:

CommandTimeout=60;

edited Aug 9, 2017 at 17:49

Cody Gray♦

246k53 gold badges512 silver badges591 bronze badges

answered Aug 9, 2017 at 17:36

user8441312

71 bronze badge

2 Comments

Michael Freidgeim Over a year ago

It doesn't work when adding to SqlClient provider connection string, I am getting: ArgumentException: Keyword not supported: 'command timeout'

T. Zack Crawford Over a year ago

SQLConnection objects appear to have a command timeout, but not for the ConnectionString: learn.microsoft.com/en-us/dotnet/api/… learn.microsoft.com/en-us/dotnet/api/…

Collectives™ on Stack Overflow

How to add CommandTimeout to connection string in web.config

6 Answers 6

Comments

Comments

Comments

Comments

2 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

Comments

Comments

Comments

Comments

2 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related