The project goal was to upgrade all of the client’s SQL servers that were running SQL 2014 to SQL 2016 SP1, while leaving the SharePoint Enterprise version at 2013.įortunately our team already had a test environment that we kept up to date for scenarios exactly like this. The entire system consisted of 7 of these farms. Each SP farm consisted of the following server formats: The client’s current SharePoint farms were running SharePoint 2013 Enterprise edition, SQL Server 2014, and SQL Server Reporting Services 2014 (all on the latest versions etc.).I was working with a large organization that had a user base in the tens of thousands that was consuming BI through SharePoint SSRS integration. Having a good test environment turned out to be crucial. I recently went through the following scenario with a client who had a large user base. Regardless of how scaled back the hardware/CPU ability is in the test environment, a test environment can only add value if test mimics Production in as many ways as possible. It’s crucial to keep your test environment at the same version/configuration level as your dev/production environments. You aren’t wrong, but what if the update/upgrade will make a big change in your dev environment as well? Some of you might be screaming at me right now shouting, “but that’s what our dev environment is for!” Only once you get access you find out the machine is running SharePoint 2003 on a Windows 95 operating system…not exactly helpful for testing potential changes in Production. Has anyone else heard these words from a client or IT department? You think “Ok, great. If you have a very small production SharePoint environment (let’s say <100 users), you can sometimes get away with not testing updates/upgrades in a dedicated environment because it’s fairly easy to recover the system if something goes wrong.īut what if the user count was in the tens of thousands? It then becomes very important to know if any key SharePoint features will stay the same, change, or be removed altogether after applying the update. Sometimes it’s easy, as SP admins, to get in the habit of simply hitting “next, next, Finish” when applying updates to SP farms or systems.
#Report builder sharepoint update
It’s always important as a SharePoint Administrator to try to understand what effect an update or upgrade to your system will have on the user base.
0 kommentar(er)
