Demoting a SQL 2000 server that is also a Domain Controller

In a domain a client has several Domain Controllers.  One of them is also a SQL server (I know this isn't reocmmended, it was already like that).  That server now needs to be demoted.  The only ramification I can think of pertains to how the services are configured.  As long as all services aren't running as local accounts on the server when it's demoted is anyone aware of other complications that I'm not taking into account?  Also, after the demotion people will need to continue to access this machine until I can schedule a restart....is anyone aware of complications not restarting immediately?
IBS_TechAsked:
Who is Participating?
 
BrughConnect With a Mentor Commented:
Cool. I think you should be fine.  However, i would still maybe hold off until you can actually reboot following the promotion.  But that's your call.

Good luck.

 - brugh

0
 
BrughCommented:
Yea, you may run into some authentication issues with users trying to access that box.  
The SQL jobs may also fail because of this

Before you demote,
 - Figure out which FMSO roles the server has or if its strictly a BDC.
 - make sure it is pointing to the PDC for DNS resolution.  

Other than that, you can probably get away with it, but you could also just hold off on the demotion until you are able to reboot.

 - brugh

0
 
IBS_TechAuthor Commented:
The SQL server holds no FSMO roles.  It is also not the source of DNS.
0
 
IBS_TechAuthor Commented:
Can you foresee (as much as possible) any issues before the reboot.  I've love to hold off till after hours, but it may be possible as the restart will be scheduled.
0
 
IBS_TechAuthor Commented:
No issues, for all who are interested...thanks for confirming my thoughts.
0
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.