locked
logins/sec RRS feed

  • Question

  • I'm monitoring 2005 while running our application by looking at

    sys.dm_os_performance_counters, general statistics, logins/sec.

     

    I began testing a .NET 2 application, and logins/sec went from 63 to 11,433 in 30 minutes.  Even though I have closed the application, it is still showing 11,449 - the only thing that's happened in the last hour is that I've run some queries from QA.  is this login number cumulative, or is it an actual reflection of logins/sec?  How on earth could that many logins be happening when no one else can even get to that server?

    Tuesday, June 19, 2007 5:30 PM

All replies

  • Hi,

     

    This counter is indeed cumulative in the dmv.

    I would check out the .NET application if it is creating 11000+ logins in 30 minutes.

     

     

    WesleyB

    Visit my SQL Server weblog @ http://dis4ea.blogspot.com

    Tuesday, June 19, 2007 6:44 PM
  • Try to log the logins on the server using the logging functionality on the server, logging the failed as well as the successfull logins.


    Jens K. Suessmeyer.

    ---
    http://www.sqlserver2005.de
    ---

    Friday, June 22, 2007 1:08 PM
  • in looking at the event viewer, there are hardly any logon/logout events.

    Logging all logins.

    ?

    Monday, June 25, 2007 4:11 PM
  • Here's what I'm seeing over and over in my trace.  Our stored procedure should be writing a record each time, but it doesn't come accross in the trace as anything but a read.  I have verified that the data is actually getting written to the table.

     

    All spid 62.

    All application name = .Net SqlClient Data Provider

     

     

    EventClass                     textdata                                          reads     writes  

      Audit Logout                     NULL                                           68              4        
     RPC:Completed              exec sp_reset_connection            0                 0 
     Audit Login                       -- network protocol: TCP/IP  set quoted_identifier on  set arithabort off  set numeric_roundabort off  set ansi_warnings on  set ansi_padding on  set ansi_nulls on  set concat_null_yields_null on  set cursor_close_on_commit off  set implicit_transactions off  set language us_english  set dateformat mdy  set datefirst 7  set transaction isolation level read committed   NULL NULL 

    RPC:Completed                exec <<<our stored procedure>>> 2       0   
    Audit Logout                      NULL                                               70          4 

    RPC:Completed              exec sp_reset_connection            0             0 
    Audit Login  -- network protocol: TCP/IP  set quoted_identifier on  set arithabort off  set numeric_roundabort off  set ansi_warnings on  set ansi_padding on  set ansi_nulls on  set concat_null_yields_null on  set cursor_close_on_commit off  set implicit_transactions off  set language us_english  set dateformat mdy  set datefirst 7  set transaction isolation level read committed   NULL NULL 

    RPC:Completed                 exec <<our stored procedure>>  2           0  

    Audit Logout                     NULL                                                  72       4 

    Monday, June 25, 2007 5:08 PM
  • Did you try to implement something like an audit mechanism, to track the written information or execution information in a table ?

    Jens K. Suessmeyer.

    ---
    http://www.sqlserver2005.de
    ---
    Tuesday, June 26, 2007 11:42 AM
  • not sure what you mean...some kind of trigger?
    Tuesday, June 26, 2007 8:16 PM
  • Yep.

    Jens K. Suessmeyer.

    ---
    http://www.sqlserver2005.de
    ---
    Thursday, June 28, 2007 11:14 AM