Comments
Sort by recent activity
Hi Rhys,
We aim for minimal performance impact on the monitored SQL Server. Of course it isn't possible to eliminate this completely, but we are currently using SQL Monitor on Red Gate's production SQL Servers and we haven't seen any noticeable performance impact.
Cheers,
--
Daniel / comments
Hi Rhys,
We aim for minimal performance impact on the monitored SQL Server. Of course it isn't possible to eliminate this completely, but we are currently using SQL Monitor on Red Gate's production...
Hi Randy,
I'm sorry you've had a performance problem that might be related to SQL Monitor. If you can, please send any information that would help us reproduce or diagnose the problem to daniel.kenyon-jones {AT} red-gate.com .
Cheers,
--
Daniel / comments
Hi Randy,
I'm sorry you've had a performance problem that might be related to SQL Monitor. If you can, please send any information that would help us reproduce or diagnose the problem to daniel.ken...
Is the WMI problem intermittent or are you seeing it all the time? / comments
Is the WMI problem intermittent or are you seeing it all the time?
Hi,
You are right, we currently refer to all clusters by the cluster management virtual address not the SQL Instance virtual address. If you had two instances on that cluster, this would be the only name that would be relevant to both instances. If we used the SQL instance virtual address, we would have problems mapping multi instance clusters into the right hand side navigation tree and the Global Overview.
We realise that this isn't how most SQL Server DBAs are used to seeing clusters and we are planing to tidy this up, make it a little more intuitive and customisable in a future release.
I'm a bit perplexed by the error log entries you are seeing. All WMI connections made by SQL Monitor are using AuthenticationLevel.PacketPrivacy. Is the cluster on a different domain to the SQL Monitor Base Deployment?
--
Daniel KJ / comments
Hi,
You are right, we currently refer to all clusters by the cluster management virtual address not the SQL Instance virtual address. If you had two instances on that cluster, this would be the onl...
Hi Larry,
Sorry to see that you are having issues with SQL Response.
When you test the credentials for a clustered SQL Server we validate the connection via the cluster address. To license and monitor the cluster SQL Response has to connect to each node of the cluster individually. Unfortunately the nodes of clusters are stored by windows as unqualified network names (eg. node1 node2) and this can cause problems in multi domain environments.
If you have added your SQL cluster using its IP address, SQL Response will assume that the cluster nodes are in the same domain as the Alert Repository. The same is true if you are using unqualified network names.
If you add a cluster using the fully qualified domain name (eg. cluster.subdomain.example.com) then SQL Response will assume the nodes are part of the same domain (eg node1.subdomain.example.com, node2.subdomain.example.com)
You can use tracert to check how network fully resolves you cluster and node network names.
Let me know if you need more help sorting this out.
Cheers / comments
Hi Larry,
Sorry to see that you are having issues with SQL Response.
When you test the credentials for a clustered SQL Server we validate the connection via the cluster address. To license and moni...
Hi,
I think the problem here is when some machines have http://support.microsoft.com/kb/969083 installed and some don't. If you are seeing this issue, we'd recommend ensuring the hotfix is deployed on all machine you are using with SQL Response.
Cheers,
--
Daniel / comments
Hi,
I think the problem here is when some machines have http://support.microsoft.com/kb/969083 installed and some don't. If you are seeing this issue, we'd recommend ensuring the hotfix is deployed...
Good to hear it.
Got to keep those servers patched :oops:
--
Daniel / comments
Good to hear it.
Got to keep those servers patched :oops:
--
Daniel
We've had a similar issue here at Red Gate (and from a bit of searching around on the internet, SQL Response isn't the only software that's been hit with this)
Microsoft have issued a critical update to Windows Authentication via windows update which breaks comparability.
If the AR is hosted on a server that hasn't had the latest security updates applied, Windows 7 clients will not be able to connect it. This only affects only XP or server 2003 AFAIK.
We've found that applying the latest security updates to the server fixed the issue (you may need to reboot).
Let us know if this fixes the issue, or if we need to investigate further.
Cheers,
--
Daniel / comments
We've had a similar issue here at Red Gate (and from a bit of searching around on the internet, SQL Response isn't the only software that's been hit with this)
Microsoft have issued a critical upda...
I'm sorry to say that the only person who can fix this is the admin of your SMTP server.
SQL Response and SQL Backup do not use the same SMTP library, so this may cause a difference which is causing the SMTP server to reject the email.
The log file shows that the only error is caused by the SMTP Server rejecting the send request.
This is a security issue rather than a bug.
Let me know if you need any further information to help you resolve this. / comments
I'm sorry to say that the only person who can fix this is the admin of your SMTP server.
SQL Response and SQL Backup do not use the same SMTP library, so this may cause a difference which is causin...
You will need to have a friendly chat with your Sys Admin.
Your company SMTP server has been configured to reject certain email addresses or sending machines. This is a common restriction to prevent Spam and Malware propagation.
I'm guessing the machine that you are using for the SQL Response Alert Repository is not a SQL Server and therefore might not be white listed to have sending privileges on the SMTP Server.
Cheers,
--
Daniel / comments
You will need to have a friendly chat with your Sys Admin.
Your company SMTP server has been configured to reject certain email addresses or sending machines. This is a common restriction to preven...