User profile for Ben C

Hi PDinCA We might have to ask for an ANTS Performance Profiler trace of your installation, but first, the following questions would help narrow down the problem. Where do you have the Base Monitor and Data Repository installed? Are they also on your IIS machine? What is the CPU utilization of RedGate.Response.Engine.Alerting.Base.Service.exe and the repository SQL Server - do they show the same spike when you use the UI? Is the rest of the UI slow or is it just the alert pages? Did you change any part of your configuration (other than the 2.0 to 2.1 upgrade) before these performance problems occurred? Thanks Ben / comments

Hi PDinCA We might have to ask for an ANTS Performance Profiler trace of your installation, but first, the following questions would help narrow down the problem. Where do you have the Base Monitor...

0 votes

Hi Rhys There was a bug in long running query alerting in the 2.0 EAPs but it should have been fixed from 2.0 onwards. Every time we see a running query, we make a note of the date. The duration of the query is simply the difference between the current date and the first date that we saw the query. We determine that it is the same query by using a combination of the process ID, the login date, and the last batch date. Hope this helps. Ben / comments

Hi Rhys There was a bug in long running query alerting in the 2.0 EAPs but it should have been fixed from 2.0 onwards. Every time we see a running query, we make a note of the date. The duration of...

0 votes

Hi We do not collect any information from the Physical Disk counters. We currently have a bug open for excluding "HarddiskVolume1" from the overviews - is this the same system partition that you are seeing? Thanks Ben / comments

Hi We do not collect any information from the Physical Disk counters. We currently have a bug open for excluding "HarddiskVolume1" from the overviews - is this the same system partition that you ar...

0 votes

The script turned out to be quite long. Please email me at ben.challenor@red-gate.com to get it. Thanks Ben / comments

The script turned out to be quite long. Please email me at ben.challenor@red-gate.com to get it. Thanks Ben

0 votes

Hi There are several different uptime estimates that we could make: 1) Uptime of the machine (based on whether we could ping it) 2) Uptime of the SQL instance (based on whether we could execute SQL) 3) Uptime of the SQL instance (based on whether the service was running) However, the estimate would only be valid if SQL Monitor was running successfully over the same time period. If SQL Monitor or the machine running SQL Monitor failed then the value would be incorrect. If that is OK, we could suggest some SQL to calculate one or more of these estimates. Which would be most useful? Thanks Ben / comments

Hi There are several different uptime estimates that we could make: 1) Uptime of the machine (based on whether we could ping it) 2) Uptime of the SQL instance (based on whether we could execute SQL...

0 votes

Hi Kevan Did you get anywhere with the VMWare document? Thanks Ben / comments

Hi Kevan Did you get anywhere with the VMWare document? Thanks Ben

0 votes

Do you have VMWare Tools installed on the guests? The support document indicates that it helps with time synchronization. / comments

Do you have VMWare Tools installed on the guests? The support document indicates that it helps with time synchronization.

0 votes

Hi Kevan We haven't noticed particular issues with clock drift on VMs, but it seems that other people have. There is a question on Stack Overflow about it, and VMWare have a support document. What VM host are you using? What guest OS? Are the guests in a domain? Thanks Ben / comments

Hi Kevan We haven't noticed particular issues with clock drift on VMs, but it seems that other people have. There is a question on Stack Overflow about it, and VMWare have a support document. What ...

0 votes

Hi Jeroen Yes, you are right - this was fixed quite recently. I'm glad that it's working for you now. Thanks Ben / comments

Hi Jeroen Yes, you are right - this was fixed quite recently. I'm glad that it's working for you now. Thanks Ben

0 votes

Hi Jeroen Reusing the connection is quite common for performance reasons. Every time we see a running query, we make a note of the date. The duration of the query is simply the difference between the current date and the first date that we saw the query. We determine that it is the same query by using a combination of the process ID, the login date, and the last batch date. Hope this helps. Ben / comments

Hi Jeroen Reusing the connection is quite common for performance reasons. Every time we see a running query, we make a note of the date. The duration of the query is simply the difference between t...

0 votes

How can we help you today?

Ben C

Comments