Comments
Sort by recent activity
I believe that was what I saw too. "access violation error" I went ahead and ziped the files and emailed them to you, if you want to review them.
Chris Spencer wrote:
If the monitoring stops again then that would be a good time to check that logs page.
I'm particularly interested in what the diagnostic page says because I had an issue today that sounds exactly like the problem you describe here. I was running some nasty SQL on a 2000 server and the monitoring was stopping until I retried the connection. The diagnostic page was showing an access violation error.
If the issue doesn't re-occur then the log files at “C:\ProgramData\Red Gate\Logs\SQL Monitor 2†could help us. As before could you zip them up and send to chris.spencer@red-gate.com
Many thanks
Chris
/ comments
I believe that was what I saw too. "access violation error" I went ahead and ziped the files and emailed them to you, if you want to review them.
Chris Spencer wrote:
If the monitoring stops again...
Only thing I'm seeing there are events since it was reconnected. Nothing is showing before I established the connection.
Chris Spencer wrote:
The logs could contain some useful information but first it would be interesting to know if you see any error message on the diagnostic page.
This can be viewed by clicking the Show Log link for the relevant machine or instance on the Monitored Servers page and it can be filtered to show only errors.
Thanks
Chris
/ comments
Only thing I'm seeing there are events since it was reconnected. Nothing is showing before I established the connection.
Chris Spencer wrote:
The logs could contain some useful information but fir...
I have several servers being monitored and have not seen any high numbers. Did you open task manager to see what processes were consoming the memory.
randyv wrote:
I just un-installed Monitor 2 for the time being.
I'm going through an ETL to convert our company to a new system.
The new system server was being monitored. All day I've been trying to load data into a target table using the import tool of the vendor's software and it just wasn't going it.
I noticed memory use was very high during this time and I couldn't figure out why.
I decided to just uninstall Monitor 2. I did that (which was on another server for the web and base monitor); then started the batch load again.
The server ran like a scalded dog and finished in 10 minutes!
Anyone have any idea why that would happen? Could it just be coincidence? I don't think so because the batch was the same file. I just killed the load; uninstalled Monitor 2, then restarted the load clean.
Interested in any ideas anyone may have. I'd like to use Monitor 2 as this will be the going forward product, but I can't have it tying up my production servers.
/ comments
I have several servers being monitored and have not seen any high numbers. Did you open task manager to see what processes were consoming the memory.
randyv wrote:
I just un-installed Monitor 2 fo...
Yes Ben. That is the same name that is showing up under the SQL instance view. It was created by the Windows 2008R2 OS by default I belive.
That partition does not show in my Server overview, just under the SQL Instance overview. That was why I thought different counter we being used. In perfmon under the physcil disk counters the partition does not show up but under the logical disks counter they do.
Thanks for looking into it.
Thanks for a great monitoring tool!
Ben C wrote:
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
Yes Ben. That is the same name that is showing up under the SQL instance view. It was created by the Windows 2008R2 OS by default I belive.
That partition does not show in my Server overview, just ...
This is wonderful!
As a database administrator I would rather see Uptime based on the SQL instance. As far as either the (based on whether the service was running) or the (based on whether we could execute SQL), I quess either would be fine and which ever is easiest.
I nderstand about your statement: " If SQL Monitor or the machine running SQL Monitor failed then the value would be incorrect."
Thanks again.
Ben C wrote:
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
This is wonderful!
As a database administrator I would rather see Uptime based on the SQL instance. As far as either the (based on whether the service was running) or the (based on whether we could...
Email on the way.
Ben C wrote:
The script turned out to be quite long. Please email me at ben.challenor@red-gate.com to get it.
Thanks
Ben
/ comments
Email on the way.
Ben C wrote:
The script turned out to be quite long. Please email me at ben.challenor@red-gate.com to get it.
Thanks
Ben
Thanks. Hopefully you can get it fixed. This fixture is great.
Chris Spencer wrote:
This is an error we're seeing a lot via the automatic error reporting component in SQL Monitor. These are automatically entered into our bug-tracking system. I seem to remember seeing it in the log files you sent last week concerning a different issue.
I'll attempt to reproduce the issue in house and get it fixed for the next release.
Thanks again
Chris
/ comments
Thanks. Hopefully you can get it fixed. This fixture is great.
Chris Spencer wrote:
This is an error we're seeing a lot via the automatic error reporting component in SQL Monitor. These are automa...
As far as seeing all your alerts at once like in SQL Response 1, If you click on the alerts tab that gives you a view of all alerts and all servers simular to that of the prior version.
Also there is a lot more screens due to having a lot more features. This is a lot more customizable too.
As far as a web app. Now I can access the tool from any machine any where by just opening a browser.
I for one like the new design and hope they fix the little issues and maybe add just a few more .
randyv wrote:
Chris -
Yes, I know; you've already put the effort in. I understand.
The idea of a monitor is to provide the most insight possible 'at a glance'.
The click to drilll on alerts removes this. For instance in Version 1 I can simply expand all 4 of my servers and view the alerts all on one page; without the need to bounce back and forth. Also the font settings and other things in version 2 chews up a lot of screen; there is just too many things to go into now; but if you'd like I'll be happy to create a list over the next few weeks and post as a 'next design phase' request here.
Cheers
/ comments
As far as seeing all your alerts at once like in SQL Response 1, If you click on the alerts tab that gives you a view of all alerts and all servers simular to that of the prior version.
Also there ...
Chris. This was just the info I was looking for. I was not going to chage the time but wanted to understand how it was configured.
Thanks
Chris Spencer wrote:
Hi
If you check the description for Fragmented Index on this help page you'll see an explanation as to why we collect this so infrequently. Basically it's very resource intensive: http://www.red-gate.com/supportcenter/C ... 269920.htm
It is possible to configure this setting but currently it requires editing a config file - C:\ProgramData\Red Gate\SQL Monitor 2\RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config. If you edit the following section and restart the base monitor service it should pick up the new settings: <schedule qualifiedChannelName="[Cluster].[SqlServer].[Database].[Table].[Index]">
<weeklySchedule dayOfWeek="Sunday" hour="1" minute="00"/>
</schedule>
If you wish to go ahead and increase how often this is checked then I could find out some more details.
Hope this helps
Chris
Hope this helps
Chris
/ comments
Chris. This was just the info I was looking for. I was not going to chage the time but wanted to understand how it was configured.
Thanks
Chris Spencer wrote:
Hi
If you check the description for F...
Everthing is in (UTC-05:00) Eastern Time (US & Canada)
The blocked process was the only error I was seeing with + 5 hour time difference. The other errors I was seeing seem to be correct but I've only seen failed jobs, long query and this blocked process.
I do have the base monitor and webserver on the same machine.
Chris Spencer wrote:
Hi Harold
What time zone are you in? (so that we can investigate this specifically)
Also are the various machines in your setup all set to this time zone? I was just wondering if this could be caused by the base monitor and web server machines being on different timezones.
Thanks again
Chris
/ comments
Everthing is in (UTC-05:00) Eastern Time (US & Canada)
The blocked process was the only error I was seeing with + 5 hour time difference. The other errors I was seeing seem to be correct but I've o...