New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Server Farm and SQLServer Farm and SQL
New Post
1/21/2012 4:26 PM

I'm new to the whole server farm idea and recently got it working with Windows Server 2008 R2.  I have 2 computers synchronizing their files through one control server.  All the files in DOTNETNUKE synchronize but the database gets an error because the server its synchronizing off locks it.

Does anybody know how to set up a dedicated SQL Server in the Community Edition, and would this solve my problem of one computer locking the SQL database?

I am running SQL Express.


  1. Control Server running Windows Ultimate to handle requests and forward them to the Primary and Secondary Servers
  2. Primary Server running DOTNETNUKE and has full copy of installation
  3. Secondary Server mirrors Primary Server
  4. *Possible SQL Server to keep database in SYNC
New Post
1/22/2012 12:07 PM
Typically the farm would only be on the web heads. In a high performance environment SQL server would be on it's own server.

I think you're going to want to prevent SQL server from replication at a file level. Typically you would implement SQL Server Merge Replication (active/active) or Log Shipping (active/standby) from to support DIsaster Recovery.

I guess my question here is what are you trying to achieve with the farm? Reliability, load balancing, disaster recovery, etc?

SQL Server replication is notoriously finicky and requires an enterprise license to work. SQL Clustering is another option as well but again this is typically a high availability concept and very expensive.

I currently manage a large DNN install that uses SQL merge replication across Data Centers for disaster recovery. It's a big PITA and we're planning to virtualize everything in order to perform VM level replication instead.

Steven Webster
Manager, Community Platform
F5 Networks, DevCentral
New Post
11/10/2012 4:19 PM


I know this thread is a bit old...but I've got a few questions I was hoping you might be able to answer if you have time.  I'm working on a graduate project using DNN (simulated) and want to setup an SQL 2008 server farm...from the sounds of it I should be able to use the same process you mentioned "SQL merge replication across Data Centers" this case my model is using Dell M series blade servers with 12 blade servers...I don't know if it makes sense at this point to use all 12 servers with SQL on each server or to use VM's as you suggested...I'm looking for redundancy, security, and load balancing.  My DNN portal should be able to support up to two or three thousand users concurrently using the social tools built into DNN 6.2.4 and a chat module.  Any suggestions are appreciated.

New Post
11/11/2012 4:57 AM
Terence, you need to identify the bottlenecks of the system and configure your servers accordingly. If you use proper caching, you reduce the load on SQL server, i.e. you would start with a server farm for the web heads and a separate SQL server (like the file server) and in the next step extend file server and sql server into clusters, usually with less machines than used in the web farm.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
New Post
11/11/2012 7:56 AM


Thank you! That is very helpful and confirms the topology I was leaning toward.  We are required to build redundancy and high availability into the project so I'll need to start with a few sql server clusters.


HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Server Farm and SQLServer Farm and SQL

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out