Re: SQL-08S01 error in FreeTDS/Azure when executing stored proc for a few minutes from Linux (but not from Windows)
Frediano Ziglio <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <CAHt6W4dGdBCDmjUDnHazKFDf1MdGc8=zHMc1mbuuAc26ZFnJ2A@mail.gmail.com> |
2012/11/21 James K. Lowden <[email protected]>: > On Wed, 21 Nov 2012 14:50:05 -0600 > Cade Roux <[email protected]> wrote: > >> Now that the flat->star transform is basically instant, and there >> should be constant client traffic from the truncate, the inserts, the >> row count and the transform, I need to break down the log from a >> reproduced case adding some timings to make it easier to post here. > > Yes. I would time each call to SQLExecute. You may find that "long" > running queries end in 20004 errors, and may be able to guesstimate the > value of "long". > > FWIW, FreeTDS does call setsockopt(2) with SO_KEEPALIVE if the host > system supports it, cf. net.c around line 217. You might want to check > your build log carefully to make sure it's enabled in case it matters. > Yes, however MS requirements are more strictly that Unix. By default many systems starts sending keepalive after 2 hours idle, much more that 1 minute! I send a patch (was not on ML? strange!) that lower the limit. Linux, AIX, FreeBSD and HP-UX should support these options. Frediano