Automation of SQL Patching with DBATools

[sharmakneeraj4]

Update-DbaInstance -ComputerName $Servers -Path '\xyz\SQL2012\CU' -Credential $cred -Version $version -Restart -Confirm:$false

I want to generate a log that can tell if there is any failure in the script. Can someone please suggest how to do that?

[niphlod]

isn't the "Notes" property reporting what you're seeking already ?

[sharmakneeraj4]

I guess you are talking about messages that come while running this script or I am missing something here?

All those notes are displayed on my profile. So consider a case when my RDP session is disconnected and few servers were not patched with XYZ reason. I need to go through logs and find out reason why servers were not patched.

[niphlod]

Update-DbaInstance returns an object for each updated instance that has a property "Notes" with (if they pop up) exceptions that occurred during the update phase. Just save it to a variable/file/whatever and you should be fine.
i.e.

$results = Update-DbaInstance - .......
$results | Export-CliXml path\to\file

you can later inspect them by doing

$results = Import-CliXml path\to\file
$results
## specifically, you'd need to look at $results.Notes

if you want instead a full trace of your script, that contains other functions other than Update-DbaInstance, look at Start-Transcript, or use redirection.

[sharmakneeraj4]

Thanks. I will try it out.

[potatoqualitee]

In addition, Get-DbatoolsLog should help

[pareshmotiwala]

Hi Guys(and gals) would this apply Windows patches as well? Somehow we have to apply Windows patches every month on a 100+ servers, some with AG and some not.

[niphlod]

nope. look at https://github.com/mgajda83/PSWindowsUpdate