Billy Pang
tuxedo_man at hotmail.com
Fri Oct 28 19:53:19 CDT 2005
maybe some sort of connection pooling on the application side to optimize performance? >From: Francisco Tapia <fhtapia at gmail.com> >Reply-To: dba-sqlserver at databaseadvisors.com >To: SQL Server 2k List <sql2k at ls.datareturn.com>, >dba-sqlserver at databaseadvisors.com >Subject: [dba-SQLServer] Sql Audit Logouts >Date: Thu, 27 Oct 2005 10:16:52 -0700 > >I'm running the profiler on a Server who has had some issues w/ >connectivity... initially I'm reading through the tracelogs and there >are not really big problems such as huge duration times on anything >"except" Audit Logouts... i've never seen them take this long... the >program is from a vendor so I do not know how it's configured from >their app... but i'm looking at logout times up to 9.64 hrs... with >the shortest ones being only a few hundred milliseconds (ie... 200ms). > >The majority of the application names point to their appname, but some >point to the .Net sqlClient Data provider > >here is a sample snapshot >APP CPU READS WRITES DURATION ClientID SPID > StartTime >COLLOGIN 129776 14759675 3305 34718656 788 >53 10/26/05 8:11 >LTILOGIN 2033 96237 252 29670173 1960 > 54 10/26/05 8:12 >LTILOGIN 779 50651 641 34692673 2364 > 55 10/26/05 8:12 > 4784 249436 191 29748840 >2376 56 10/26/05 8:12 > 0 73 0 >29744313 2376 57 10/26/05 8:12 >COLLOGIN 55892 4235589 782 26828546 856 >58 10/26/05 8:13 >COLLOGIN 313 23476 14 27890093 1524 > 60 10/26/05 8:13 > > >-- >-Francisco >http://pcthis.blogspot.com |PC news with out the jargon! >http://sqlthis.blogspot.com | Tsql and More... >_______________________________________________ >dba-SQLServer mailing list >dba-SQLServer at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >http://www.databaseadvisors.com >