So for my upgrades I follow this basic structure where stopping any writes to SQL is the priority goal during the dB update:
- Distribute the installation files
- Stop IIS, this stops outside/inside communications
- Take a snapshot or run a SQL backup depending on your preference. Key is to have. a backup of SQL prior to starting.
- Snapshot your Application server if possible
- Run the Application installer on your server until it tells you to stop and go work on your dB
- Drop all connections to your SQL database by taking it offline and the back online to be safe
- If you are using ETL (connector for intelligence) make sure to stop that as well
- Once you have all the connections dropped, Run the SQL DB installer
- If the dB install was a success, say yes on the application server and let the install complete
- you may have to restart server(s) based on the installer and requirements
- Start IIS again if it is not started
- Now login to your console (which may seem slower than usual after an update due to SQL doing it's ramp up)
- That wraps up your install
I do the following after each install for testing
- enroll a device(s) based on your use cases
- send some commands like a lock etc to verify things are active
- I also look at my device list view and see if devices are checking in
- Do some of your daily activities to try and stave off any complaints before actual admins and users come back into play