| Breck Carter [TeamSybase] 2005-07-14, 9:23 am |
| First of all, that link shows that you *did* get a response.
If you were looking for a response like this: "We will provide this
new feature with release XXX on date YYY" then I have this suggestion
for you:
The secret to true happiness is to lower your expectations.
NO commercial vendor is going to tell you in exact detail what their
plans for future enhancements are unless you sign a non-disclosure
agreement with them... and maybe not even then.
Most of the postings in this forum do not have any replies at all, and
*very* few replies from iAnywhere Solutions personnel.
The current request level log was clearly never intended for real-time
monitoring or heavy-duty statistical analysis; it has a number of
flaws which prevent that.
IMO the missing year is not a showstopper since there is a simple
workaround (unless, of course, you have accumulated a single request
level log file that spans two year ends). The date/time is missing
altogether from satmp_request_time... that's *really* irritating,
again IMO.
The current request level log IS very helpful for performance tuning
and for debugging.
Sadly, I am under NDA, but I *can* say that I have complained loudly
and often about the request level log file :)
Breck
On 14 Jul 2005 02:32:52 -0700, máca wrote:
>There is a <a
>href="http://forums.sybase.com/cgi-bin/webnews.cgi?cmd=item-2820&group=sybase.public.sqlanywhere. product_futures_disc
ussion">thread</a>
>on this forum about datetime format (losing year
>information) in log files but without response. :-( Is there
>any reason for formating datetime in this manner?
>
>I. 05/13 19:35:16. 0000000000
>
>instead of
>
>2005-05-13T19:35:16 0000000000Z
>
>Thanks for reply.
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
|