DNN SQL Server and Other Performance Best Practices
Because DotNetNuke performance issues can be so nuanced, there are a number of performance-related best practices that the previous articles didn’t cover. This article will sum them up.
DotNetNuke Performance Best Practices Overview
Besides the checking on the items covered in previous articles, you will also want to make sure that your antivirus software contains exemptions for all of your website folders. Otherwise, antivirus software can significantly slow down your website. Additionally, set debug=false and trace=false in your web configuration, and disable widgets if you don’t use them. And finally, if you’re trying to scale your website up, use a SQL server. You should do this even if you aren’t anticipating a traffic spike.
DNN SQL Server Best Practices
Only use the most recent edition of SQL server and its service packs, and always store it on a server that is separate from your database server.
With a few exceptions, we generally don’t recommend SQL Express, as its memory storage for the buffer pool is limited. Only use the most recent edition of SQL server and its service packs, and always store it on a server that is separate from your database server. From there, create a maintenance plan for your SQL server that includes data backups, index statistic updating, and compressing and reorganizing data and index pages. You can even set this up using a simple wizard already provided by Microsoft.
Increase Your DotNetNuke Performance with Clarity Ventures
Website performance optimization can be tricky and heavily dependent on a wide variety of factors. That’s why it’s so important to consult with an expert, who will know what to look for and where to improve. Our DotNetNuke experts are always on top of changes and updates that may affect your load time, and we can help you move ahead accordingly. Contact a Clarity representative today to learn more.
Find out more about Clarity VenturesSee our Enterprise Web Portfolio