Manage the suspect_pages Table on SQL Sever 2017

  • Junior Galvão - MVP

    SSCertifiable

    Points: 6362

    Comments posted to this topic are about the item Manage the suspect_pages Table on SQL Sever 2017

  • HappyGeek

    SSCoach

    Points: 18650

    Nice simple one to end the week on thanks Junior.

    ...

  • Stewart "Arturius" Campbell

    SSC Guru

    Points: 71251

    Nice one to end the week on, Junior, thanks - learned something

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

  • Junior Galvão - MVP

    SSCertifiable

    Points: 6362

    HappyGeek - Thursday, April 19, 2018 10:04 PM

    Nice simple one to end the week on thanks Junior.

    Thanks.

  • Junior Galvão - MVP

    SSCertifiable

    Points: 6362

    HappyGeek - Thursday, April 19, 2018 10:04 PM

    Nice simple one to end the week on thanks Junior.

    Thanks.

  • webrunner

    One Orange Chip

    Points: 29828

    Thanks for the instructive question.

    PS Does anyone know why the suspect_pages table is in MSDB and not in master? Just curious.

    -------------------
    A SQL query walks into a bar and sees two tables. He walks up to them and says Can I join you?
    Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

  • Junior Galvão - MVP

    SSCertifiable

    Points: 6362

    webrunner - Friday, April 20, 2018 12:36 PM

    Thanks for the instructive question.

    PS Does anyone know why the suspect_pages table is in MSDB and not in master? Just curious.

    I'm guessing it's for access permissions issues.
    Because it is a table that can be accessed both for reading and also for writing by any user with permission in MSDB.
  • webrunner

    One Orange Chip

    Points: 29828

    Junior Galvão - MVP - Friday, April 20, 2018 4:18 PM

    webrunner - Friday, April 20, 2018 12:36 PM

    Thanks for the instructive question.

    PS Does anyone know why the suspect_pages table is in MSDB and not in master? Just curious.

    I'm guessing it's for access permissions issues.
    Because it is a table that can be accessed both for reading and also for writing by any user with permission in MSDB.

    Got it - thanks for your explanation!
    - webrunner

    -------------------
    A SQL query walks into a bar and sees two tables. He walks up to them and says Can I join you?
    Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

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

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