Hello Sitecore Lovers!
We recently upgraded our Sitecore Solution from 6.3.1 rev. 110113 to 6.4.1. rev 120113 (Update-6). And in this post and some coming later I would like to share some basics, tips and findings that we had during this task.
Before we go into much details, I would like to apologize, as this one’s going to be a Theoretical Post. But actually, I can guarantee that its going to be very informative and useful for any version upgrade, plus it will be interesting!
Sitecore Verison Upgrade from a broader perspective looks as simple as executing some SQL Scripts on the Sitecore Databases and installing an Upgrade Package. But it becomes more critical as and when you move to its core. And actually, when you have multisite instance Sitecore Solution, (like the one in our case) it becomes one of the most critical and complex projects as even a small change can affect all the clients!
Now, lets move into the very fundamental details and basic questions which come in mind, when we talk about Sitecore Version Upgrade. Obviously, Sitecore has a very strong documentation, and I am going to refer to many of its links here, but just trying to make a job easy. Some very frequent questions that come up along with a small explanation are as follows:
- Sitecore Version Upgrade is a 1-step Process? Or we need to perform multiple steps for it?
- Decide the Target Sitecore Version that you want.
- Check if you have its pre-requisite version.
- Backup your Application and Database.
- Check which version you are currently on and what target version
- Execute the Pre-Install Database Script (SQL or Oracle, depends upon which Database System you use) if any.
- Install the Sitecore Upgrade Package.
- Execute the Post-Install Database Script if any.
- Check that your solution is working fine — Some level of regression testing.
- Make all the required changes to your custom code if it has stopped working, (also, even if its working, its better to build your solution again and deploy the latest build onto your Environment, but only after you test it throughly!).
- How do we understand which functionalities are added to which version of Sitecore?
- Do we need to move to the recommended version of Sitecore? Or can we move to a more later version even if its not recommended by Sitecore?
Actually, you should move to the Sitecore’s Recommended Version. The reason behind this is they have thoroughly tested it, not only for a functional bugs but even for performance related issues and have fixed them. But then, there might be a case, that a version later to the recommended version could cover the functionality that you badly need or which might be the sole reason for you to upgrade your Sitecore Solution. Then, in this case, you can ask me as a comment here. I will try to answer it to the best of my knowledge. If can’t then will ask you to raise it with experts i.e. Sitecore Forums or Sitecore Support! 🙂
- Do we need to upgrade the CM and CD Environments together? Or can we do it as a 2-step process?
- What all is included in upgrading a CD Server Application? Do we have to execute the upgrade wizard on CD Server too?
- Files in the Sitecore Folder (mainly in Sitecore/Shell which is not present on CD Server).
- Items in Core Database.
- Items in Master Database.
- Executing the Database Scripts — in the order from current version to the target version.
- Finally replacing all the files from your latest build — from your Development Repository (CI Server) where you have your latest build.
- What if we have multi-instance in CM environment? Do we have to execute upgrade package on both the instances?
- Files in Sitecore Folder
- Items in Core Database
- Items in Master Database
- Why Upgrade?
Good one Varun…
Thanks Hardeep! 🙂
That’s indeed a in depth analysis and very helpful for upgrades!.
Thanks for the energizing words! I wish this and a couple of them to follow be helpful to everyone who take up Sitecore Upgrades.
Sincerely,
Varun Shringarpure
Hi Varun,
My CD server has only core and web databases. How can i upgrade sitecore on CD server?