Home Dashboard Directory Help
Search

MSFT-MSO: Document DBCC LOGINFO() or create new DMVs to view VLF info by Narayan_Iyer


Status: 

Active


65
0
Sign in
to vote
Type: Suggestion
ID: 322149
Opened: 1/12/2008 11:28:09 PM
Access Restriction: Public
0
Workaround(s)
view

Description

I currently use DBCC LOGINFO() to view the VLF information of my database. I searched through BOL and I neither could find any documentation for this DBCC command nor any documented or officially supported way of listing the VLF information of a database.

Details
Sign in to post a comment.
Posted by Chris Fradenburg on 10/9/2012 at 6:04 AM
Based on the performance impact that the number of VLFs can have there really should be a documented method of getting that information.
Posted by Arvind Shyamsundar on 12/8/2011 at 12:48 AM
I voted for this, and would also like the product team to also consider incorporating it as a property of the Log File facet in Policy Management.
Posted by Microsoft on 8/4/2009 at 2:04 PM
Thank you for your comment.
We agree that this is the right thing to do for the product.
We have defined this DMV as a DCR to the product, and it is currently a pick-list item for the next release, meaning that after the large features are complete, we will pick from the list of high priority DCRs to implement as we have resources.
Posted by A.Lockwood on 8/4/2009 at 9:56 AM
This really should be visible in a DMV. It plays a role in database performance and is something that we've all got to keep an eye on. Why not help out us DBAs and make this easily viewable/trackable through a DMV?
Posted by Microsoft on 2/28/2008 at 2:19 PM
To reiterate, this functionality will not be part of the Katmai release, but is being kept as an active request for the next version.
Posted by Microsoft on 2/6/2008 at 10:08 AM
Thank you for your suggestion.
Our direction is not to document DBCC commands, but for informational queries such as this to add appropriate DMVs. I will add this to the list of DMV requests. Unfortunately it will not make the Katmai release. We will consider it for a future release.
Sign in to post a workaround.