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. Query Analyser 'responce time'

Query Analyser 'responce time'

Scheduled Pinned Locked Moved Database
databasebeta-testingsharepointsql-serversysadmin
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 have a SQL Server 2000 program which has logging sp which writes a record to a table and also print of that record. i.e. we can run the program in QA and see what its doing. However QA only updates every so often...is there a way we can make it update more regularly? It just to help with testing/development. In production a GUI sits on top.

    C 1 Reply Last reply
    0
    • C cjb110

      I have a SQL Server 2000 program which has logging sp which writes a record to a table and also print of that record. i.e. we can run the program in QA and see what its doing. However QA only updates every so often...is there a way we can make it update more regularly? It just to help with testing/development. In production a GUI sits on top.

      C Offline
      C Offline
      Corporal Agarn
      wrote on last edited by
      #2

      Instead of the print try populating a table that a second QA session can access and query that while the sp is running. You could try linking SQL 2008 Express and running from there as 2008 reports back more often. Another trick is to put in "timestamps" on your print so you can tell where things are taking so long. As you can tell tuning is not my specialty, so I hope one of these helps or someone comes up with a better idea. Good Luck.

      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