I noticed recently that while waiting for a long-running stored procedure my
network light flashed A LOT. I snooped it and discovered the server (12.5.1)
was sending my waiting DBLib client 10 512-byte (data portion) messages/second.

Does anyone know why this happens and if I can turn it off or slow it down?

"Thomas Gagne" <tgagne (AT) wide-open-west (DOT) com> wrote


Assuming these weren't packets for sending the result set to the client, my
guess is that these were so-called 'done-in-proc' packets (one is sent to
the client after each DML statement). It may be possible to suppress most of
these packets with dbcc tune (doneinproc, 0); in 12.5.1, use the config
parameter 'send doneinproc tokens' instead. Be careful about also enabling
traceflag 292: this will suppress all doneinproc packets, but may also cause
some clients to stop working correctly (i.e the connection will break with
an error message).

HTH,

Rob
-------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 12.5/12.0/11.5/11.0
and Replication Server 12.5

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE"
"The Complete Sybase Replication Server Quick Reference Guide"
"The Complete Sybase ASE Quick Reference Guide"

mailto:rob (AT) YOUR (DOT) SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., P.O.Box 10695, 2501HR Den Haag, The Netherlands
-------------------------------------------------------------

That may be it. The procedure was using a cursor to flog the database. We're
running 12.5.1 so I'll look into the option. Thanks for the info!

Rob Verschoor wrote: