Avatar of I_play_with_DNA
I_play_with_DNA asked on

Database server as secondary domain controller - acceptable?

We currently have an SBS 2003 box as our primary domain controller (also running Exchange and file shares).  We also have two Windows 2003 Standard R2 servers on the network:  one runs Oracle 10g and holds a database used by about 9 people; the other runs MS SQL 2005 and hosts our Microsoft Dynamics CRM database, accessed frequently by about 12 people and infrequently by another 15 or so..

I would really like to add a secondary domain controller to the network for fault tolerance reasons.  Would it be acceptable to make one of the database machines a secondary domain controller?  Would I expect to see much of a performance impact?  I am under the impression that, in an organization as small as ours (approx 55 users) that the DC-related activity on a server would be extremely small.

Can someone please tell me if I am correct in my thinking, and provide any recommendations?

Thanks in advance!
Windows Server 2003

Avatar of undefined
Last Comment

8/22/2022 - Mon
Brian Pierce

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

I was thinking the effect would be minimal as well because, as I mentioned, the database systems are only accessed by a handful of people regularly and the amount of data being updated is relatively small.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy