Not sure if this helps...
>From AR System Log Analyzer (arwklga) User Guide version 2.15: Q. Some of the longest running SQL statements are reported as running longer than the enclosing API call or for a length of time that is just absurd. Why? A. As of AR System 5.1, the COMMIT TRANSACTION statements were no longer issued to finalize most transactions in MS SQL Server and Sybase SQL Server. This was done in order to speed processing. Unfortunately, this left the Log Analyzer with no way to determine the time at which the results of the SQL statement were returned to the AR System. No convenient workaround has been established except to drill down into the log to make a best logical determination as to which timings are realistic and which are not. -- Jarl On 10/24/07, Misi Mladoniczky <[EMAIL PROTECTED]> wrote: > Hi All, > > In some databases, it is hard to find the start and end of each set of > SQL-calls. A commit/rollback is there in some databases. > > I recall that some kind of option was introduced in 7.0, so that the a > logrow was added after each set of SQL-calls. > > I have been unsuccessful in finding this setting in the documentation... > > Could someone please point me in the right direction? > > Best Regards - Misi, RRR AB, http://www.rrr.se > > Products from RRR Scandinavia: > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > * RRR|Translator - Manage and automate your language translations. > Find these products, and many free tools and utilities, at http://rrr.se. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
