Comments
Sort by recent activity
Yes... it shouldn't. Thanks I'll add it to the bug list / comments
Yes... it shouldn't. Thanks I'll add it to the bug list
Ok, Response won't mention Log backup overdue for any DB with the simple recovery model. Which means you may have set your master DB to have a full recovery model perhaps?
Even if you do this you still can't log bakup master anyway, so i've added an explict check for that.
Thanks / comments
Ok, Response won't mention Log backup overdue for any DB with the simple recovery model. Which means you may have set your master DB to have a full recovery model perhaps?
Even if you do this you ...
[image] I guess i could argue it's a little embarassing that I even attempt to get 6 months worth of history! But I guess for a monthly job I would still want to get that baseline. SQL agent seems to limit it to 1000 rows, and upto 100 per job by default but obviously people can change that.
We'll look into what we can do to allieviate this, if not for the release then for a futrue version.
Thanks for your help [image] / comments
I guess i could argue it's a little embarassing that I even attempt to get 6 months worth of history! But I guess for a monthly job I would still want to get that baseline. SQL agent seems to lim...
I misread. It's trying to get the job history. So the query we run is msdb..sp_help_jobhistory @mode='FULL'
Maybe you could run that via SSMS and see how long it takes (and how many rows it returns)
Thanks[/code] / comments
I misread. It's trying to get the job history. So the query we run ismsdb..sp_help_jobhistory @mode='FULL'
Maybe you could run that via SSMS and see how long it takes (and how many rows it retur...
Thanks. I asume that must be from when we gather all the job information from the server. I'm suprised that's taking so long. Can I ask how many jobs do you have on this server please? / comments
Thanks. I asume that must be from when we gather all the job information from the server. I'm suprised that's taking so long. Can I ask how many jobs do you have on this server please?
This is an argument we've had internally as well. I happen to think we should report them as I would like to know why we are causing these. Not reporting a long running query that we are running would be counter productive to what we're trying to do which is to give an accurate report of what is happening on the sql server.
To that end could you please post the details of the query that is taking a long time please? Then we can take a look at why it's slow [image]
Thanks / comments
This is an argument we've had internally as well. I happen to think we should report them as I would like to know why we are causing these. Not reporting a long running query that we are running w...
It's been a a... thorny issue shall we say [image]
The main issue is which the SQL account in the SQL connections use the "logged in" user (like connecting via SSMS - it trys to connect as you) - so that's the one it's best to get correct.
WMI allows you to specify an account on the remote machine to use which is why that can be changed per-computer. Having a default is a good idea, but also complicates things even more. / comments
It's been a a... thorny issue shall we say
The main issue is which the SQL account in the SQL connections use the "logged in" user (like connecting via SSMS - it trys to connect as you) - so that'...
This is beacuse the service account is the default account used to connect to the monitored servers both via SQL and WMI. Beacuse of what we monitor we need this to be an admin account on those servers.
Although you can specify a different windows account for each servers WMI connection and a SQL Authentication account for the SQL connection it is far far easier to have one admin account for all the connections. If you didn't choose an admin account up front at install time you'd need to reinstall, so to avoid that we thought it easier to require an admin account at install. / comments
This is beacuse the service account is the default account used to connect to the monitored servers both via SQL and WMI. Beacuse of what we monitor we need this to be an admin account on those se...
Hi,
I'm afraid I've not seen that particular error before but I suspect the firewall is the problem.
In order to monitor a server SQL Response needs both a SQL Connection (probably using port 1433 that you have open) but it also needs a WMI connection which uses DCOM. This intially uses port 135 for a connection but after that it can use other ports to carry on the communication. http://msdn.microsoft.com/en-us/library/ms809327.aspx explains how you could get DCOM working across a firewall and how to restrict the pots it will use (however I'm afraid I've not tried any of this) / comments
Hi,
I'm afraid I've not seen that particular error before but I suspect the firewall is the problem.
In order to monitor a server SQL Response needs both a SQL Connection (probably using port 1433 ...
Note - if these servers are accessable to the whole internet (via that firewall) then I would not recomend opening up the DCOM ports. / comments
Note - if these servers are accessable to the whole internet (via that firewall) then I would not recomend opening up the DCOM ports.