I am soon going to be migrating the SCCM DB from being hosted on the primary site server, to a standalone sql box. I'm curious how others have handled patch scheduling for the DB server.
I have about 15 different server maintenance windows throughout the week. Currently the site server (which is the DB server also) patches at the same maintenance window as other servers, and it isn't a problem.
With separating the db from the site server, do I need to bounce the site server after the DB is rebooted? Should I separate the patch window for the site server and db server? Should I isolate those 2 on their own maintenance window?
Just looking for ideas on how others have handled patching with the roles being separate.
site:
single primary site (2k8 r2)
1 primary site server (holds all roles)
3 dist points (2k8 r2)
@1500 clients
soon to be separate db server (2k12 r2 with sql 2014)