Configure SQL to timeout requests rather than rejecting if no connections available

Arran Cudbard-Bell a.cudbardb at
Sun Jan 18 04:39:43 CET 2015

> On 17 Jan 2015, at 08:13, Noah Engelberth <nengelberth at> wrote:
>>> Is there a setting change I can make to get the server to just
>>> ignore/drop the request if there are no SQL connections available,
>> sql {
>> 	fail = 1
>> }
>> if (fail) {
>> 	do_not_respond
>> }
> Thanks, I appreciate the syntax help.
>> Why are you using the Unix ODBC driver? There's the FreeTDS driver written
>> specifically for communicating with Microsoft servers...
> Using the FreeTDS driver won't work for us because our SQL cluster requires the MultiSubnetFailover parameter to be set by connecting clients (it's a geo-redundant Always On Availability Group), which requires the Microsoft Native Client ODBC driver -- FreeTDS doesn't support that parameter as far as any documentation I could find suggests.  With just FreeTDS, we'd be in a situation where our RADIUS servers would have a 50/50 chance of actually connecting when they tried to open a new SQL connection, which is kind of sub-optimal.

Ah, ok, fair enough :)

FreeTDS is generally the better tested module, the UnixODBC module really needs updating to use the newer ODBC API. But if it works for you, great!


Arran Cudbard-Bell <a.cudbardb at>
FreeRADIUS development team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

More information about the Freeradius-Users mailing list