SQL DMVs to read SQL ErrorLog, Windows NT Log for Application , Security , system etc - by Ranga1

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 543213 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 3/19/2010 7:24:36 AM
Access Restriction Public


Since SQL 2005 I can see Windows NT log from SQL Server under management, thats really cool, but I can query them.
Sign in to post a comment.
Posted by Ranga1 on 6/9/2010 at 6:57 AM
It is unfortunate this item is closed. I did look at extended events, We have to manually add events to be monitored, but whereas sql log/windows log, there is a goldmine of info to be monitored without any preconfiguration and most administrators are already well educated in these logs, whereas extended events is a new concept yet to catchup!

This feedback item will be of huge benefit to DBAs. Though it is not a selling point for MS, it will help DBAs to adminster SQL server efficiently. Please reconsider opening this item.

Posted by Madhan [MSFT] on 6/7/2010 at 10:02 PM
Thanks Kevin for your comments. Unfortunately after looking into this, we think DMVs are not the right vehicle to expose such logging information. However if you have specific request in enhancing the Extended events we collect today, we would be really interested and i highly encourage you to file a request against that component.

I am resolving this item as a Won't fix. Once again i highly appreciate your time in giving us your suggestions. Please keep them coming.

Posted by Kevin Nicholas on 3/26/2010 at 6:37 PM
Adding to this, I would suggest that the Event alert definition section of a new alert is enhanced. The 'Raise alert when message contains:' section could possibly emulate Profilers Filters which allows for 'like', 'not like' etc. The ability to also search 'all' severity and/or error numbers would be a plus as this would reduce the number of alerts which need to be created. The ability to plug into sys.messages and set is_event_logged would be also be great.
Posted by Madhan [MSFT] on 3/26/2010 at 8:51 AM
BTW, Have you looked into leveraging Extended Events to accomplish some of these tasks? After thinking about this more, i am wondering if perhaps scalable technologies such as XE is more suited to monitor information you are requesting. DMVs as you know is meant to expose SQL Server internal implementation specific information.

Posted by Madhan [MSFT] on 3/24/2010 at 8:25 AM
Dear customer,
thank you for your feedback and suggestion.
your proposal is an interesting one and we would take a look at it for our next release. In the past we've tried to limit the OS level information exposed via DMVs to things relevant to the sql server process (process memory, # logical processors etc.,) Exposing additional things would mean that we would not only have to make sure the information plumbed out are protected, but also might have to incur the cost of extracting that information from the source. regardless, i can see how it could be useful in customer scenarios.

As i mentioned above, i will keep this DCR in books for our next major release and reassess its feasiblity.
thank you for your time and feedback,