March 9, 2020 at 5:50 pm
Hi All,
Would like to get some suggestion of SQL patching solution and automation for multiple servers. I have 150+ SQL with each version 2012,2014,2016 & 2017. We do not have cost to buy patching tool, is there any easy and good solution to automate this like WSUS, PS etc.
March 9, 2020 at 6:51 pm
One option with Powershell is to use dbatools and the cmdlet Update-DbaInstance. You can find more information on that cmdlet in this link: Update-DbaInstance
An example of how to use this and have some central location for the patches can be found in this post:
Patching Multiple SQL Servers With Powershell and dbatools
Sue
March 10, 2020 at 12:07 am
As a bit of a side bar, I'm always amazed when someone says they have a shedload of servers but no money to actually support them. It just doesn't make any sense.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2020 at 5:06 pm
Thanks Sue.
Yes Jeff, the same I have asked our management, they want all in zero cost. We are small 3 person team.
March 10, 2020 at 6:01 pm
Thanks Sue.
Yes Jeff, the same I have asked our management, they want all in zero cost. We are small 3 person team.
Heh... you're also a 150+ server team. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 12, 2020 at 4:12 pm
If you think its expensive to hire a professional to do the job, wait until you hire an amateur.
March 12, 2020 at 5:34 pm
One option with Powershell is to use dbatools and the cmdlet Update-DbaInstance. You can find more information on that cmdlet in this link: Update-DbaInstance
An example of how to use this and have some central location for the patches can be found in this post:
Patching Multiple SQL Servers With Powershell and dbatools
Sue
Hi Sue,
I am getting this error. I am admin of OS.
WARNING: [17:32:34][Update-DbaInstance] Failed to get reboot status from servername| Specified credentials are known to not work!
March 12, 2020 at 7:05 pm
Sue_H wrote:One option with Powershell is to use dbatools and the cmdlet Update-DbaInstance. You can find more information on that cmdlet in this link: Update-DbaInstance
An example of how to use this and have some central location for the patches can be found in this post:
Patching Multiple SQL Servers With Powershell and dbatools
Sue
Hi Sue,
I am getting this error. I am admin of OS.
WARNING: [17:32:34][Update-DbaInstance] Failed to get reboot status from servername| Specified credentials are known to not work!
The warning is due to running the commands using credentials that don't have permissions to reboot after the patching if needed. Wouldn't matter what you use to patch in that case, you would need to use a login that can reboot whichever patches require a reboot.
Sue
March 12, 2020 at 8:54 pm
Thanks, I have admin access to the remote server, do I need to add in any particular group of local policy.
March 12, 2020 at 9:05 pm
Just used other option -Credential $psCred -Verbose
[Update-DbaInstance] Explicit -Credential might be required when running agains remote hosts and -Path is a network folder
WARNING: [20:57:22][Update-DbaInstance] Failed to enumerate files in -Path | Access is denied
The path // is having permission to everyone with full access.
March 12, 2020 at 10:30 pm
Aren't those supposed to be backslashes instead of forward slashes? Could that be the remaining issue?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2020 at 10:02 am
Sorry that was typo \\.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply