Results 1 to 2 of 2
  1. #1
    Join Date
    Aug 2004
    Calgary, Alberta

    Unanswered: sql server 2000 authentication costs

    Hey all,

    I've got an app that's poorly designed and doesn't do connection pooling. It causes the login rate/sec on our prod server to jump up to 15/sec. I'm trying to qualify the resource cost of this behaviour. Althought this application logs in and out, it only ever has one active spid. It never holds anything in the db, it's purely an auth cost. I'm currently trying to correlate this with SQL Server cpu time, and memory.

    Does anyone know where I can find some documentation, or some tips as far as login rate is concerned?

    There is nothing more helpless and irresponsible than a man in the depths of an ether binge. -HST

  2. #2
    Join Date
    Nov 2004
    on the wrong server
    Provided Answers: 6
    you can do this in profiler can't you? Yep, I just setup a trace with the standard columns and only the login and log out events on my local machine and after a few tries I did get some cpu time in millisecods in the CPU column.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts