I'm using Golang with FreeTDS using the ODBC driver from brainman (http://code.google.com/p/odbc)
Everything works great, until I stress test the box.
Then I get the following error:
{01000} [unixODBC][FreeTDS][SQL Server]Unable to open socket SQLDriverConnect: {08001} [unixODBC][FreeTDS][SQL Server]Unable to connect to data source
It seems that when I try to launch multiple concurrent requests against the FreeTDS / unixODBC drivers, it fails. Is this something that is workable, or is unixODBC and FreeTDS not useable in production environments?
This sounds similar to an issue that I ran into. FreeTDS/ODBC on CentOS7 connecting to an SQLServer2005 database. I ended up creating 6 separate FreeTDS/ODBC DNS entries to have 6 discreet database connections available to use in order to resolve this issue (they were all just numbered duplicates of each other--$db, $db2, $db3, etc). It's not a great solution, but it does work (I was migrating a really old system, so my options were limited). I'd be very interested if there is a better solution than mine.