Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Windows Server 2016 running IIS and SQL Server: configuration topology and optimization – recommendations

Posted on 2016-11-03
3
103 Views
Last Modified: 2016-12-09
All,

I am in the process of setting up a 2-servers home-based network to run IIS and SQL Server. It is my understanding that is best to use one server for SQL and the other one for IIS. I will appreciate your can share you recommendation in setting this up in order to secure and optimize performance in both servers. For example, should I setup the servers as Domain or just as Workgroup? What's the best practice to secure the two systems? I know each topic can get *very* deep and can have many variable, so please think on my environment. Both, SQL and IIS will not run anything fancy (heavy). I know Server 2016 is new and I am aware of the existence of the nano-server option, however, will prefer to use a traditional interface (GUI). Thank you much!!!
0
Comment
Question by:Cobra967
3 Comments
 
LVL 27

Assisted Solution

by:Dan McFadden
Dan McFadden earned 250 total points
ID: 41873623
If you are not running anything "heavy" then you should deploy IIS and SQL together on 1 server.

If this is just a one-off application, deploying AD just makes your build more complex.

In general, for medium to large load sites, I would recommend separating the web app from the db.  For smaller loads, there is no reason to not run the app and db on the same server.  For light work, running SQL Server Express would probably be enough.

I would recommend to run a single server that contains IIS and SQL Server in a workgroup setup.

If you post more about what your application setup requires, better recommendation could be made.

Dan
0
 
LVL 28

Accepted Solution

by:
Ryan McCauley earned 250 total points
ID: 41876622
I'd agree that AD may be overkill - if you're trying to learn how active directory works and want to work with that configuration, you can use it, but neither SQL Server nor IIS requires it. You can log in to the SQL Server using local SQL authentication (rather than windows users) and you won't have any issues.

It may be worth setting this up on two different servers just so you can see what it's like to configure the networking and make sure they're communicating, but it isn't required - both applications will fit just fine on one server, especially if you're not doing much with them. Ideally, SQL Server would have it's own physical disks (one for logs and one for data), but that's also not a requirement if they're light use.
0
 

Author Closing Comment

by:Cobra967
ID: 41877065
Thank you all for your comments!
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
Remote Apps is a feature in server 2008 which allows users to run applications off Remote Desktop Servers without having to log into them to run the applications.  The user can either have a desktop shortcut installed or go through the web portal to…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question