Comments
Sort by recent activity
We could show the memory used at the time we last captured it (obviously we poll every N seconds (where N is less than 60 but i can't recall what it is exactly!)
The other thing we could show that we capture is total CPU time so far - capturing the %cpu for each process gets a little tricker for various practical reasons.
We'll look at this for the final release [image] / comments
We could show the memory used at the time we last captured it (obviously we poll every N seconds (where N is less than 60 but i can't recall what it is exactly!)
The other thing we could show that ...
Ok - this should do it... [image]
Open a command prompt and type the following 2 commands net stop SqlResponseMonitorService
sc delete SqlResponseMonitorService
they should stop the service (which probably isn't running anyway) and then remove it.
You can then safely delete everything in the following folders
C:\Program Files\Red Gate\SQL Response Incident Repository 1.0 Beta
C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Response
and that should do it [image] / comments
Ok - this should do it...
Open a command prompt and type the following 2 commandsnet stop SqlResponseMonitorService
sc delete SqlResponseMonitorService
they should stop the service (which proba...
We may need to work out some manual uninstall instructions. Bear with me a minute.... / comments
We may need to work out some manual uninstall instructions. Bear with me a minute....
It's a good question to which I don't have a good answer!
We capture the information but don't display it - so we can look into this for the final release / comments
It's a good question to which I don't have a good answer!
We capture the information but don't display it - so we can look into this for the final release
That implies there was an error when we were writing the incident file (otherwise you would see a message more akin to what you were looking for [image] ).
We have fixed a couple of problems in this area for final release but could you please send me the alert repository log files from c:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\Logs please? (ideally with a screen shot showing the incident in question) to nigel.morse @ red-gate.com
Thanks / comments
That implies there was an error when we were writing the incident file (otherwise you would see a message more akin to what you were looking for ).
We have fixed a couple of problems in this area ...
The negative durations was an error - it has been fixed for final release [image] / comments
The negative durations was an error - it has been fixed for final release
It does look like there's a problem here. Clearly the average should be the the average of the last 10 runs - need to find out what's going on :oops: / comments
It does look like there's a problem here. Clearly the average should be the the average of the last 10 runs - need to find out what's going on :oops:
That would be very useful please [image] Send to nigel.morse at red-gate.com please [image] / comments
That would be very useful please Send to nigel.morse at red-gate.com please
Reponse will take an average of the last 10 succesful job runs as the basline, but often it can get this from the job history which may keep a lot more than the last 10 runs so it can get the baseline from that.
Could you send me the log files please - you'll find them in
C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\Logs\SQL Response AlertRepository.
If you could send them to nigel.morse at red-gate.com please? / comments
Reponse will take an average of the last 10 succesful job runs as the basline, but often it can get this from the job history which may keep a lot more than the last 10 runs so it can get the basel...
oh... hmm - well the explict check is in there now anyway [image] / comments
oh... hmm - well the explict check is in there now anyway