Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...best to run sql server on same box or different?best to run sql server on same box or different?
Previous
 
Next
New Post
7/21/2009 10:24 AM
 

We are getting ready to go live with our site in a few weeks.  We just purchased a new server to put the dnn app on.  We have a sql box we use for another site (it runs ON that sql box).  The new server is running Server 2008 64-bit, the old server is Server 2003 with sql 2005.  Our site gets moderate traffic (about 160-200,00 hits per day is average depending on the month).

I had planned on running the app on the new box and putting the db on the box we already use for sql server (2005) with a Gb connection between them.  For performance purposes, is it better to run the app and db on the same server or split them up?  This is the first site I have ever set up so it's been an interesting ride.  I would appreciate any input on the subject!

Thanks,

Kevin

 
New Post
7/21/2009 10:57 AM
 

IMHO, strictly from a security standpoint, IIS and SQL Server should be on separate servers, preferably with a firewall between them. IIS is exposed to the world, I don't think having SQL server on that box is a great idea.

Then from a performance standpoint, both SQL and IIS are heavy memory consumers, in the case of DNN where caching is relied on heavily, this raises the chance of a conflict.

HTH



 
New Post
7/21/2009 11:07 AM
 

You would need to run your own tests. All down to RAID speed/memory/CPU/LAN performance - but given the opportunity I would always consider a seperate SQL box as SQL server takes a lot of resources and hammers the hard drive. Plus your data is centralized for backups etc. It's also a good security consideration.

Nowadays though server virtualization completely muddies the waters, it has an overhead - but it makes best use of existing resources/scalability and you can play around.... I would recommending investigating this path should this be important to you (i.e. VMWare).



Alex Shirley


 
New Post
7/21/2009 11:17 AM
 

khankins-
Separating DB and web front end is more about security than performance (although that is also a consideration).  In a multi-tier setup the DB should be more heavily firewalled than the web server (i.e., the DB should not run on some other web server, either).  Running the DB on your web server provides more "surface area" for attack by the outside world.  Instead, run the DB on a separate box with limited/minimal file shares, minimal exposed ports and different service accounts than those used on your web server.  Your DB service accounts should only have enough rights to run SQL.
 
See here for a general security "checklist" for SQL Server (written for SQL 2000 but still applies to current versions):
http://msdn.microsoft.com/en-us/library/aa302337.aspx

Performance-wise running SQL on the web server could be better or worse than running on a separate box depending on your environment.  If you had very beefy servers doing very little work then you'd probably see no improvement with running the DB on a separate box.  On the other hand, if you are leveraging your DB server for more than just DNN then a dedicated DB box will probably be more performant.  Typically your web server will be a lesser box and the DB server a beefier box with a heavy dose of RAM.
 
That said, though, there are still plenty of people out there that run DNN with both the DB and website on the same box.  Anyone who says they run their website on a "virtual private server" is probably doing this.  I don't do this myself but, unless you are handling very sensitive information (credit card info, medical patient records, etc) then the higher security risk is probably outweighed by the cost savings of not adding a second server to be a dedicated DB server.  (Just make sure to stay on top of your backups in case your DB is victimized!)


Good luck!
-mamlin


esmamlin atxgeek.me
 
New Post
7/22/2009 11:23 AM
 

Awesome guys thank you very much for the input!

Kevin

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...best to run sql server on same box or different?best to run sql server on same box or different?


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