This was going to be a side-by-side upgrade which meant we were to set up the SQL Server 2016 MIS version on a new box without interfering with the then SQL Server 2008-based MIS production environment. ![]() The MIS environment consisted of your typical Microsoft BI stack services. However, I was recently involved in a project whereby I needed to upgrade a client’s SQL Server 2008 based MIS environment to SQL Server 2016. DEV, UAT) to eventually roll it out on production When a service pack is released, install it in phases starting from the non-production environment (i.e. ![]() ![]() Instead of installing SQL Server Cumulative Updates, wait for release of service packs I’ve always been in favor of an orthodox strategy when it comes to applying SQL Server updates which often goes like:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |