DBCC DBINFO in SQL Server 2008 SP1 reports the dbi_dbccLastKnownGood info twice - by Sankar Reddy

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.


1
0
Sign in
to vote
ID 485869 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 8/28/2009 12:50:57 AM
Access Restriction Public

Description

Hi,

In SQL Server 2008 SP1, DBCC DBINFO WITH TABLERESULTS displays the dbi_dbccLastKnownGood  information twice. The same command displays the above mentioned information only once in prior releases.
Sign in to post a comment.
Posted by Emily [MSFT] on 9/1/2009 at 4:20 PM
Hi Sankar,
Thanks for taking the time to send us your feedback. This certainly looks like an error, but doesn't appear to have severe enough effects to meet the bar to require a QFE. If this is causing a more severe issue than it appears on the surface, please let us know.

thanks,
emily
Posted by Emily [MSFT] on 9/1/2009 at 4:20 PM
Hi Sankar,
Thanks for taking the time to send us your feedback. This certainly looks like an error, but doesn't appear to have severe enough effects to meet the bar to require a QFE. If this is causing a more severe issue than it appears on the surface, please let us know.

thanks,
emily
Posted by Emily [MSFT] on 9/1/2009 at 4:20 PM
Hi Sankar,
Thanks for taking the time to send us your feedback. This certainly looks like an error, but doesn't appear to have severe enough effects to meet the bar to require a QFE. If this is causing a more severe issue than it appears on the surface, please let us know.

thanks,
emily
Posted by Emily [MSFT] on 9/1/2009 at 4:19 PM
Hi Sankar,
Thanks for taking the time to send us your feedback. This certainly looks like an error, but doesn't appear to have severe enough effects to meet the bar to require a QFE. If this is causing a more severe issue than it appears on the surface, please let us know.

thanks,
emily