Comments
Sort by recent activity
I'm sorry for the delay in replying to your post.
I believe that you have encountered a bug with SQL Monitor. This is a use case that the development team never considered and so it is only recently that we started looking at it. Unfortunately, it does mean that I cannot give you any timescales on when we might be able to address it and release any fixes (if appropriate). / comments
I'm sorry for the delay in replying to your post.
I believe that you have encountered a bug with SQL Monitor. This is a use case that the development team never considered and so it is only recent...
Thank you for your post.
There is currently a bug in the tool which I think that you have encountered. This is logged in our system as SRP-9426. I have been working with the development team and we believe that we have a viable fix for it, but we have not been able to implement this fix as yet. Unfortunately, I cannot give any timescales for when this work can happen either as the development team are not able to give me this information at the moment. It is high on the list of work though.
In the meantime there is a workaround that a number of other users have been able to implement. For scheduled or anticipated events then also schedule a restart of the SQL Monitor Base Monitor service for immediately afterwards. Unfortunately, this isn't the prettiest of workarounds and isn't much help for unscheduled events, but does work.
If you have any questions then please let me know. / comments
Thank you for your post.
There is currently a bug in the tool which I think that you have encountered. This is logged in our system as SRP-9426. I have been working with the development team and ...
I'm sorry for the delay in replying to your post.
When you reinstalled did you uninstall the old version?
Is the new install monitoring too? / comments
I'm sorry for the delay in replying to your post.
When you reinstalled did you uninstall the old version?
Is the new install monitoring too?
Thank you for your post and I am sorry for the delay in my reply.
It currently is not possible to customise the Global Overview or any of the other webpages in the tool. This is something that has been requested before, and we have some suggestions on the SQL Monitor UserVoice forum which you are very welcome to comment on. https://sqlmonitor.uservoice.com/forums ... uggestions / comments
Thank you for your post and I am sorry for the delay in my reply.
It currently is not possible to customise the Global Overview or any of the other webpages in the tool. This is something that has...
Is there any further information logged in the SQL Server error log? / comments
Is there any further information logged in the SQL Server error log?
My guess is that the regular expression you are specifying is not matching the BACKUP LOG in the SQL Process fragment.
Possibly consider using:
BACKUP/sLOG
(assuming that the SQL Process will always be in capitals and it is all backup log jobs you want to ignore).
(/s is the escaped character for 'space')
It may take some trial and error to get exactly the behaviour you are looking for.
RegExLib.com may also help: http://regexlib.com/CheatSheet.aspx / comments
My guess is that the regular expression you are specifying is not matching the BACKUP LOG in the SQL Process fragment.
Possibly consider using:
BACKUP/sLOG
(assuming that the SQL Process will alway...
Thank you for your post.
SQL Monitor uses a SQL Server table valued function called sys.dm_exec_sql_text (based upon a sql_handle found using the view sys.dm_exec_query_stats) to gather information about queries which are run. These are used in a number of places including the long-running query alert.
sys.dm_exec_sql_text (Transact-SQL) http://msdn.microsoft.com/en-gb/library/ms181929.aspx
sys.dm_exec_query_stats (Transact-SQL) http://msdn.microsoft.com/en-us/library/ms189741.aspx
The tool uses a complex query to get this information, and unfortunately neither of these hold the parameters specified when running stored procedures. To the best of my knowledge there is no way to retrospectively find these out either.
I'm sorry that I don't have a better answer for you. But feel free to add any additional questions. / comments
Thank you for your post.
SQL Monitor uses a SQL Server table valued function called sys.dm_exec_sql_text (based upon a sql_handle found using the view sys.dm_exec_query_stats) to gather information...
Is it possible that the user account you are using for monitoring the SQL Server instance only has permissions to view the system databases? Or some variation of permissions which does not give it full access?
This forum post suggests a query that you can use to see what permissions a user account has on each database. It should help you see whether this is the problem http://stackoverflow.com/questions/7048 ... a-database / comments
Is it possible that the user account you are using for monitoring the SQL Server instance only has permissions to view the system databases? Or some variation of permissions which does not give it...
A windows admin account doesn't necessarily have full permissions on a SQL Server instance, so it is still worth double checking. / comments
A windows admin account doesn't necessarily have full permissions on a SQL Server instance, so it is still worth double checking.