Post reply

Patching

  • December 11, 2013 at 4:05 pm

    #287353

    Hi Experts,

    We have windows patching on SQL Server and the process we follow here is check jobs,kill jobs if any running,run checkpoint and then app team will take care of patching.

    Is this a good practice or it is good to stop SQL Server after checking jobs and then proceed with patching and once completed then start the SQL Server??

    Thanks In Advance

  • December 11, 2013 at 4:20 pm

    #1672784

    Ratheesh.K.Nair (12/11/2013)

    Hi Experts,

    We have windows patching on SQL Server and the process we follow here is check jobs,kill jobs if any running,run checkpoint and then app team will take care of patching.

    Is this a good practice or it is good to stop SQL Server after checking jobs and then proceed with patching and once completed then start the SQL Server??

    Thanks In Advance

    You're missing a most important step (IMHO)... take a full backup backup before the patch goes in.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • December 11, 2013 at 5:19 pm

    #1672795

    Thanks Jeff,

    My confusion is whether its good practice to reboot the whole server without stopping SQL Server or its ok with the above said steps?

  • December 11, 2013 at 9:55 pm

    #1672821

    Ratheesh.K.Nair (12/11/2013)

    Thanks Jeff,

    My confusion is whether its good practice to reboot the whole server without stopping SQL Server or its ok with the above said steps?

    Ah, understood.

    I probably play such things too safe but I'll typically take the SQL Service down before installing any Windows patches. It only takes a minute or two extra.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • December 12, 2013 at 5:10 pm

    #1673126

    I don't like the idea of killing jobs midway. Depending on what they do, partially completed jobs might be problematic.

    I'd prefer to disable in advance any jobs that might be running when the upgrade window starts. You can renenable and run the jobs manually upon completion depending on the nature of what the jobs do.

  • December 13, 2013 at 5:49 pm

    #1673433

    dan-572483 (12/12/2013)

    I don't like the idea of killing jobs midway. Depending on what they do, partially completed jobs might be problematic.

    I'd prefer to disable in advance any jobs that might be running when the upgrade window starts. You can renenable and run the jobs manually upon completion depending on the nature of what the jobs do.

    That would be my preference, as well.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 6 posts - 1 through 5 (of 5 total)

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