in a 2 server system, should both servers be domain controllers?

I have two servers, dell2650 with one running ad, dns, dhcp terminal services and some user programs. the other server is just for one specific sql 2000 multi user program (timematters).  I  set the system up but I am no expert, and just now see that the sql server is also a domain controller.  I did not intend this, and am considering demoting it, but don't know if I should or not.  what are the pros and cons of only having one domain controller vs two?
Who is Participating?
PapertripConnect With a Mentor Commented:
As with any important service, you do not want it to be a SPOF (single point of failure).  A domain controller definitely provides important services, so, what if your only DC goes offline for whatever reason?  That is where a backup domain controller comes into play.
SuperTacoConnect With a Mentor Commented:
Paper trip is correct, but on the same token, you do not want a terminal server to be a DC.  That's very insecure.  there are very few server roles, you don't want to be on a DC.  Exchange, Terminals Services, and in some situations SQL.  there's not much you can do with your current config.  In your situation, I would keep everything as it is and change things when you migrate/upgrade servers.  

How big is this client?  if they are fairly small, ans just running 1 app on the SQL server, there's really no harm.  
195ecentralaveAuthor Commented:
we have 15 terminals, 2 or 3 outside terminal services users,
its been running fine for some time but all of a sudden we have some issues with dns and I am looking at it again and see that the sql app server is also listed as a domain controller, i suppose there is no harm in leaving as is until we upgrade.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.