Hi All,

I had this question posed to me from a client. I'm wondering how true this is and how scalable DNN is with regard to high volume of traffic? How many concurrent connections can MS SQL database handle before it starts to choke? Thanks!

/*START QUOTE*/
.DotNetNuke generates asp files and uses an MS SQL database. So every time the users view a page, it has to process through the database (pull files to be displayed from the database) which in high volume traffic situations CAN make this process slower.
/*END QUOTE*/

There are also strategies such as page caching for non-authenticated page reads with a tool such as Snapsis PageBlaster. This bypasses the need for a trip to the database at all; essentially, the web server returns a static page. That static cached page is refreshed from the database on configurable schedule.