09.07.2012 18:41, Vlad Khorsun wrote: >> I think these ideas should not mix concepts of trace with debug and >> profile. So for what it will be useful? > > Trace *is* very useful for both debugging and profiling.
No objections here. Especially at the absence of better tools ;-) > Ask google for "SQL Server Profiler", btw. Ask people what they need... People do need debugging and profiling. But it does not automatically mean they need it via tracing, even if they would say it this way (just because they cannot think of anything else). > I don't say that we don't need true debugger\profiler, no. But don't limit > trace > functionality artificially. Personally, I agree that custom (user generated) trace events could be a useful addition, as they extend the application specific auditing tasks. But I'm quite skeptic about the gain the PSQL statement level tracing introduces, unless you plan to have future debugging/profiling tools being based on (and extending) user trace sessions -- but this is what surely deserves a public discussion. Dmitry ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
