User profile for benrees

Thanks again for your feedback, Linque - I've also added in your comments regarding the iPad/iPhone app. / comments

Thanks again for your feedback, Linque - I've also added in your comments regarding the iPad/iPhone app.

0 votes

Hi there - both of these issues are on our plans for the next release (v2.2 - due out in the next few months), but I'm afraid that doesn't guarantee they will make it in to this version. We keep a constant eye on what people are requesting and adjust our priorities during the project according to that feedback. Obviously your request here is an important vote for these two areas. In particular, the second request (alerting when monitoring stops) has been asked for by others and so is pretty certain to make it in to the 2.2 release. Would a release in the next 3-4 months fit in with your timescales, or are you looking for something sooner than that? / comments

Hi there - both of these issues are on our plans for the next release (v2.2 - due out in the next few months), but I'm afraid that doesn't guarantee they will make it in to this version. We keep a ...

0 votes

Hi Jim If you're using SQL Monitor on a large number of servers (for example, the 250+ that you mention), we certainly recommend you split your deployment in to a number of different Base Monitors. I.e. that you don't try to monitor all servers with a single Base Monitor service. Generally, we recommend around 40-50 monitored servers per deployment. Apologies that this wasn't made clearer to you earlier. In a future version we have plans to allow this sort of number to be covered by a single deployment via a number of remote proxies, but this is not on the roadmap for the next few months (monitoring 250+ servers presents a number of issues, not least how to display so many servers on one screen!). We will however have a version 2.2 out very soon (weeks, not months) that will provide the monitoring alerts (i.e. tell you when the system isn't monitoring) that I hope will have helped fix some of your problems. There are a lot of times, for example, where the Remote Registry service will fail on a monitored machine (for reasons outside our control obviously, but enough to prevent us from collecting certain data) and we will now send an alert to the user to let them know that they need to go and investigate this. Note also that if a problem fixes itself (e.g. the Remote Registry comes back up) the alert will be marked as Ended so that you know it's no longer a problem. On a separate note, we've also tried to be clear in the software when there are hiccups in monitoring. We collect a great deal of information from servers in a very low impact way, but one of the consequences of this is that we will occasionally miss a packet. E.g. we might collect CPU usage data every 15 seconds but miss one of these (for whatever reason) so that we've only collected this data 3 times in a minute instead of 4. In this case we will briefly show "Bad Data" to the user, and record something in the log, even though the missed bit of data is pretty inconsequential. Nevertheless we thought it useful to leave an audit trail so that the user can look in to any of these issues if he/she wishes. Again, hope that helps - and feel free to contact our support guys if you want any help with set up. Ben / comments

Hi Jim If you're using SQL Monitor on a large number of servers (for example, the 250+ that you mention), we certainly recommend you split your deployment in to a number of different Base Monitors....

0 votes

Hi Jim Apologies that you've been having problems with SQL Monitor. Are there any specific issues that our support people could look in to? Would it help if one of our support team gave you a call to go through the setup? Regards Ben Rees / comments

Hi Jim Apologies that you've been having problems with SQL Monitor. Are there any specific issues that our support people could look in to? Would it help if one of our support team gave you a call ...

0 votes

Hi - yes, absolutely. The data is stored in a SQL Server backend. We've created a number of VIEWs to help the user understand the database schema and we'll also be providing some sample SSRS reports to help users get started. Regards Ben Rees / comments

Hi - yes, absolutely. The data is stored in a SQL Server backend. We've created a number of VIEWs to help the user understand the database schema and we'll also be providing some sample SSRS report...

0 votes

Hi - I'm the Product Manager for SQL Response here at Red Gate. Version 1 will alert you when deadlocks occur, providing information that helps you find the problem causing the deadlock. You can download the fully-functional 14-day trial and see whether it finds your problem! You can find the download here: http://www.red-gate.com/products/SQL_Response/index.htm Version 2 will replicate this functionality - if you want to try out an Early Access Program release of this new version, you can find this at: http://www.red-gate.com/products/sql_response_eap/index.htm Hope that helps! / comments

Hi - I'm the Product Manager for SQL Response here at Red Gate. Version 1 will alert you when deadlocks occur, providing information that helps you find the problem causing the deadlock. You can do...

0 votes

How can we help you today?

benrees

Comments