Question Locked

is a second Domain controller really necessary or beneficial for us?

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a small office of 12 employees. We are running Small Business Server 2003, which is the host of our domain controller. We recently purchased another server with Windows 2003 Standard for the purpose of running SQL Server 2005 Standard edition.

The suggestion has popped up that we install a second Domain controller on the new SQL box, for the express purpose that if the first one goes down people will still be able to login to the network and access shared files on the SBS server.

Does anyone else think this second DC is necessary or beneficial? Is it worth it to try to crowd that onto the SQL box? We certainly don't need it to share the load, since we only 12 users. Also a DC on a SBS cannot give up its FSMO roles so I'm not sure how well the second DC would work as a fail-over. Any thoughts?

2 replies

by Member 30634329

You've already come up with a lot of valid reasons not to make your SQL server a domain controller. You want to keep your SQL separate from other applications if possible for performance reasons. Besides, if the SBS server (your file server, email server, and domain controller) goes down, people won't be able to get their files anyway.
Instead, examine your SBS hardware and make its hardware as redundant as you can (good RAID, dual power supplies, dual NIC's, etc.)

This discussion is closed to new replies.