?
Solved

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

Posted on 2016-11-03
3
Medium Priority
?
226 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
[X]
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
3 Comments
 
LVL 28

Assisted Solution

by:Dan McFadden
Dan McFadden earned 1000 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 1000 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

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

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

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

752 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