Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Detecting SQL Server Activity

Detecting SQL Server Activity

Scheduled Pinned Locked Moved Database
sysadmindatabasesql-serveragentic-ai
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    cjb110
    wrote on last edited by
    #1

    I would like to detect if SQL Server is 'doing anything'. I know this is vague so a bit of background: I have a GUI that starts a long set SQL server processes (its a financial model), and in order to overcome the extremely cack network we have, I start this SQL process via a SQL agent job, so that the 'server' owns the process rather than the user running the GUI. Now I've got control logic in the sql, updating timestamps in tables etc, but I would like a 'backup' to this. Originally I thought about using the sql server cpu activity which I can get via WMI, and some kinda of threshold value...so if cpu >33% then the server is likely to working and not idling? But I just wondered if there was a better way? I'm using SQL Server 2000 and VB6 (yea you can laugh!)

    G 1 Reply Last reply
    0
    • C cjb110

      I would like to detect if SQL Server is 'doing anything'. I know this is vague so a bit of background: I have a GUI that starts a long set SQL server processes (its a financial model), and in order to overcome the extremely cack network we have, I start this SQL process via a SQL agent job, so that the 'server' owns the process rather than the user running the GUI. Now I've got control logic in the sql, updating timestamps in tables etc, but I would like a 'backup' to this. Originally I thought about using the sql server cpu activity which I can get via WMI, and some kinda of threshold value...so if cpu >33% then the server is likely to working and not idling? But I just wondered if there was a better way? I'm using SQL Server 2000 and VB6 (yea you can laugh!)

      G Offline
      G Offline
      Garth J Lancaster
      wrote on last edited by
      #2

      I think you're on the right track - SQL server has some of its own performance counters, they might be of good use to you - this shows a list http://www.extremeexperts.com/SQL/Articles/SQLCounters.aspx[^] see [SQL Server:Databases - Transactions/sec] for instance 'g'

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups