For those running Sitecore PaaS, you should consider using Solr (and SolrCloud in Production) as Azure Search has some significant limitations. For Sitecore XM and XP, you may be able to get by with Azure Search… but given the field limits, it can quickly paint your Sitecore environment into a corner. For XC (aka, Sitecore …
In order to leverage the Sitecore Publishing Service, you need the actual service and the module. The actual Publishing Service is what you will install to run the publishing as a distinct role, while the module is separate item added to your CMS and CDS roles. The Publishing Service can be downloaded at: https://dev.sitecore.net/Downloads/Sitecore_Publishing_Service.aspx Ensure …
If you ever need to find your Sitecore Version number without logging into the CMS, you can browse to the /sitecore/shell/sitecore.version.xml file.
Of note, you can also check your applied hotfixes. These will reside in the /sitecore/shell/hotfixes directory.
Review the following for full details: https://kb.sitecore.net/articles/891209
A slow Sitecore PaaS environment is more than just the Web Apps. The backend is just as important as the front end. If this is not properly scaled, you will run into limitations. Consider Elastic Pools As a best practice, you should group your Azure SQL databases into Elastic Pools and provide an overhead large …
Announced at this mornings 2019 Sitecore Symposium is the option to move to SaaS for Sitecore. While the plan is to make an initial iteration available in Summer 2020, now is the time to start planning for the considerations this move could bring. With the promise of continual updates of the base Sitecore platform, which …
Using MongoDB for xDB in Sitecore 9.2 is an option. By default, the Sitecore Installation Framework (xDB) uses the Shard Map Manger in SQL for this purpose, and is the default recommendation. However, if your requirements are to run xDB in Sitecore 9.2. using Mongo, here are the steps per the Sitecore 9.2 installation guide …
Non-optimal code in the GetDefinitions and SaveDefinitions stored procedures may cause a Sitecore 9 Reference Database under load to consume a lot of CPU resources… which can cause degradation in CD Server performance.
Sitecore provides details of this issue, and resolution in the following: https://kb.sitecore.net/articles/595419
When having multiple CD Nodes in rotation via a load balancer, its imperative to know if they are actually in rotation. While you can check the load balancer settings, you may not have access and need to determine from an front end perspective if all CD Servers are operating as expected.
A few tricks to determine if nodes are in rotation are as follows:
If you see the “Failed to instantiate a processor of type ‘”Sitecore.Xdb.MarketingAutomation.Processing.EventProcessor”” error in your Marketing Automation Engine Logs (located within the AppData/Jobs path, not the actual Marketing Automation Role), there are a few things to check. This issue is generally caused by the Marketing Automation Engine Windows Service being unable to communicate to xConnect …
Sitecore logs are a helpful resource for anyone managing their Sitecore environment… but as part of good Sitecore governance, you need to adjust the logging retention for how long to keep your Sitecore logs (this can be shorter or longer than the defaults). As the Sitecore CMS, Processing, Reporting, and CD Roles are different than …