Database Properties

  • Junior Galvão - MVP

    SSCertifiable

    Points: 6426

    Comments posted to this topic are about the item Database Properties

  • Stewart "Arturius" Campbell

    SSC Guru

    Points: 71483

    Good question, thanks Junior.

    Nice new option... learned something today

    ____________________________________________
    Space, the final frontier? not any more...
    All limits henceforth are self-imposed.
    “libera tute vulgaris ex”

  • DinoRS

    SSCrazy

    Points: 2564

    So, Maybe I didn't get it but a MVP just told me this:

    In previous versions of SQL Server, the Page_Verify database property algorithms were used to verify and identify possible incomplete, suspected, or broken pages of data.

    In SQL Server 2017, what is the new option that should be set to add a certain bit in the header of a page?

    I'm not going to argue with a MVP here but I can prove that Checksum was for Page_Verify Option available at least a few versions back.

  • Andrey

    Say Hey Kid

    Points: 691

    hi

    first link in References section doesn't work

    https://www.sqlservercentral.com/blogs/cleveland-dba/2012/06/07/page_verify-checksum-vs-torn-page-detection/

     

    also, it's not clear what do you mean by the question

    "In SQL Server 2017, what is the new option that should be set to add a certain bit in the header of a page?"

    when correct answer is "Checksum".

    Checksum option has been introduced in SQL2005 , so it's not "the new option in SQL2017".

    https://blogs.msdn.microsoft.com/sqlserverstorageengine/2006/06/29/checksum-in-sql2005/

     

  • Toni-256719

    SSCarpal Tunnel

    Points: 4938

    I didn't think Checksum was a new option.  It's been around for quite a few versions.

  • DinoRS

    SSCrazy

    Points: 2564

    I think we should all send in QotD with what we think might be a 2017-ish thingie - , feels almost like a Jersey thing to do.

    Sorry no hard feelings but I would assume both MVP and QotD approver, know this - now - basic (2005) story.

  • Data_God

    SSCrazy

    Points: 2688

    I also got this wrong this morning as I know that Checksum has been around for quite a few versions. I even went back and verified this on several of our SQL Server installations including 2005, 2008, 2012 and 2016 and Checksum is available in all of those.

  • Tom Schuettke

    SSCarpal Tunnel

    Points: 4103

    I think we need an explanation from the author.  Checksum was added in 2005.  He backs up his answer with one broken link and one that doesn't mention this being added in 2017.  Almost like he took a 2005 question and changed the date to 2017.  The correct answer probably should have been none.

  • Scott Coleman

    One Orange Chip

    Points: 27406

    To begin with, none of the options are new in 2017.  Then the question asks for the option that will "add a certain bit in the header". None of the options adds exactly one bit, but TORN_PAGE_DETECTION adds only two bits while CHECKSUM adds 32 bits.  CHECKSUM is the better answer if you want to have more confidence that data corruption will be detected, but it doesn't seem to me that it is the best choice the way the question is worded.

     

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply