Comments
Sort by recent activity
Thanks for the suggestion. You're also not the first to make this one so I think it will be on the list of things to look at. / comments
Thanks for the suggestion. You're also not the first to make this one so I think it will be on the list of things to look at.
Jason Cook wrote:
Hi,
Currently:
* If you only wish to monitor local SQL Server instances, you can use an administrator, or the "Local System" account.
* If you wish to monitor remote SQL Server instances, you will need an administrators account , which is an administrator on all of the machines you wish to administer.
Just to clarify slightly windows auth for the sql servers is fine, but the account running the incident repository needs to have administator rights on the remote machin (e.g. by being put in the remove machines local administrators group) / comments
Jason Cook wrote:
Hi,
Currently:
* If you only wish to monitor local SQL Server instances, you can use an administrator, or the "Local System" account.
* If you wish to monitor remote SQL Serv...
The issue is (embarassingly) that you live in a timezone that isn't UTC :oops: . We often use UTC internally and convert back to the server time and there was an issue there that we've hopefully now fixed here for next release. / comments
The issue is (embarassingly) that you live in a timezone that isn't UTC :oops: . We often use UTC internally and convert back to the server time and there was an issue there that we've hopefully ...
thomasswilliams wrote:
Hi All - I'd been using SQL Response for a while, but now I see this error beside the server name in the "monitored objects" list:
WMI Error : The RPC server is unavailable
I've tried searching on the forums unsuccessfully; googling brought up too many different "solutions", so I thought out of desperation I'd post here.
Thanks!
Hi,
I know what you mean about the many "solutions" out there! You said this used to be working to that same server OK?
The error messages WMI returns can be unhelpful - and I've often seen that one when the real error is that logon has changed, or when it's trying to authenticate a user from a different domain than the machine is in. / comments
thomasswilliams wrote:
Hi All - I'd been using SQL Response for a while, but now I see this error beside the server name in the "monitored objects" list:
WMI Error : The RPC server is unavaila...
Hi Luis - I'd be interested to know which of Response's queries are comming up as long - could you perhaps send me the SQL that comes up for them in a pm please?
Profiler doesn't show itself as it doesn't really run SQL once it's set up the trace it just sits there and listens. By contrast we're actually interrogating the server occasionaly to get information out of it.
Now obviously we should be having minimal impact on a server, but if we just filtered out all our own queires then this may give a false picture - i'd rather we heard about them so we can fix it properly.
Thanks,
Nigel / comments
Hi Luis - I'd be interested to know which of Response's queries are comming up as long - could you perhaps send me the SQL that comes up for them in a pm please?
Profiler doesn't show itself as it ...
Hi,
Which version of SQL Server are you running?
On 2000 we can only get the "input buffer" of the running SQL which may only be the first 255 bytes or so. If it's 2005 then it should have more (i think up to 8Kb)
Perhaps you put the fragment and complete queries into a pm to me here?
Thanks,
Nigel / comments
Hi,
Which version of SQL Server are you running?
On 2000 we can only get the "input buffer" of the running SQL which may only be the first 255 bytes or so. If it's 2005 then it should have more (...
We think we've found the problem causing this and hopefully have fixed it for next release. / comments
We think we've found the problem causing this and hopefully have fixed it for next release.
Well that blows that theory out the water... (although was good to know anyway for when someone else has the issue!)
We'll take a look at the same version you're using and get back to you.
Thanks / comments
Well that blows that theory out the water... (although was good to know anyway for when someone else has the issue!)
We'll take a look at the same version you're using and get back to you.
Thanks
Just to add to what Priya said - when it does a check DB SQL Server should write to the error log with a line similar to... DBCC CHECKDB ( database name )
or DBCC CHECKALLOC
or something like that. You could either email us the whole log file, or if you're not comfortable with that then just an example of the line in question. / comments
Just to add to what Priya said - when it does a check DB SQL Server should write to the error log with a line similar to...DBCC CHECKDB ( database name )
orDBCC CHECKALLOC
or something ...
Could I ask what version of SQL Server you are using?
SQL Response checks the log file looking for DBCC CHECKDB lines. There was an issue with SP2 of Sql Server 2005 that meant that when using maintainance plans it would lose the database context and run the check on the default database. If this happens the log shows
DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs ((etc.))
rather the name of the DB it was meant to check. The information can be found here http://support.microsoft.com/kb/934459/ which as I read it meant that the maintainance plans weren't actually checking the DB.
I tried this locally on a test box and adding the fix from that link fixed it here.
Reading this http://blogs.msdn.com/psssql/archive/20 ... ained.aspx it looks like there were multiple issues with SP2 that needed patching (indeed they re-released SP2 after a while it seems) / comments
Could I ask what version of SQL Server you are using?
SQL Response checks the log file looking for DBCC CHECKDB lines. There was an issue with SP2 of Sql Server 2005 that meant that when using mai...