July 5, 2012 at 7:58 am
Hello,
Can someone provide me set of instructions to consider at the time when testers works on database. What I know is to monitor the space and locks. Apart from this as DBA do we need to do monitor any other thing on the database/server level.
July 5, 2012 at 8:05 am
Why would you need to specifically monitor anything that yuo don't normally monitor when testers are working on a testing server?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 5, 2012 at 8:47 am
To just make sure of log space is not running.out of space...and database is functioning as is....
July 5, 2012 at 9:30 am
what kind of testing ?
performance testing (soak, stress, load tests)?
functional testing / Unit testing?
environment/patch deployment testing ?
MVDBA
July 5, 2012 at 10:53 am
performance testing(load)
July 6, 2012 at 2:30 am
in that case (depending on how dilligent your test analyst is and what methods/tools they are using for the test) then i would just leave it alone - any changes to monitoring may skew their results.
the whole point of these tests is to push the server as far as possible and see if it breaks. If you test analyst is a good one then he will be grabbing performance data as the test is run that will support his findings (test evidence) - if he's not collecting test evidence then point him at the ISEB/ISTQB foundation level certification for test professionals.
i would imagine that the tester will be running perfmon for the duration of the test and collecting the following data
Page life expectancy
locks per second
Various Memory statistics
compiles/recompiles per second
cache hits/misses
disk i/o statistics
disk queue length
cpu statistics
he will most likely not care about t-log usage or data file expands/shrinks or tempdb usage , which are the things the DBA should be monitoring anyway
MVDBA
July 6, 2012 at 2:56 am
in that case (depending on how dilligent your test analyst is and what methods/tools they are using for the test) then i would just leave it alone - any changes to monitoring may skew their results.
the whole point of these tests is to push the server as far as possible and see if it breaks. If you test analyst is a good one then he will be grabbing performance data as the test is run that will support his findings (test evidence) - if he's not collecting test evidence then point him at the ISEB/ISTQB foundation level certification for test professionals.
i would imagine that the tester will be running perfmon for the duration of the test and collecting the following data
Page life expectancy
locks per second
Various Memory statistics
compiles/recompiles per second
cache hits/misses
disk i/o statistics
disk queue length
cpu statistics
he will most likely not care about t-log usage or data file expands/shrinks or tempdb usage , which are the things the DBA should be monitoring anyway
MVDBA
July 6, 2012 at 2:58 pm
Thanks mike..
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply