Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL server 2000, moving domains/PDC

Status
Not open for further replies.

chris4ops

Technical User
Jun 5, 2008
7
US
Hi,

First off, i'm going to give you some background information of what position i'm in to better understand where I am comming from and want to do. I inherited a very small companies network about 9 months ago couple months out of school, so i've slowly been understanding the ins and outs of everything. One of the last things I have gone deep into is our SQL server, which I've never used before now. A couple of months ago, we had a power line go down a couple blocks down and the entire streets power went out for about 6 hours, and when it came back our PDC was corrupted and crashed. I built a new PDC but with a different domain name since the company has been meaning to change it to fit their company name, instead of using the default "workgroup". Anyway, I bring it up and first thing I change over is the application server where the SQL server is installed. I couldn't open any of my applications, which you probably all would have guessed. So my question(s) is/are:

1. Are there any settings I can change to make it look for the new domain instead of the old one to make it work? (how would I do that? the only tool i'm kinda familiar with is enterprise manager, which was just by exploring it)

2. My second question is keeping the same domain name, and computer name as my old PDC, and hooking everything back up to that, would THAT work without changing settings? or minimal settings? I'm VERY hesitant to do this since we really have no budget for IT support, and if I change "domains" it HAS to work since I can't move it back to the old one which is running off a Secondary DC.

I've searched a few threads and found some potential help, but one was for NT server
(Which btw, we are using w2k AS, and want to move to w2k3 eventually, so once we get a new server i'll need to install SQL again, but thats not for a very long time)
and i wasn't sure if that would work with w2k.
Sorry for my run ons and rambling, but I hope you all understand what I was trying to say.

Thanks for any help, it's all appreciated.
 
After doing a lot more reading and researching, the problem I *Think* more people have with moving to a new domain is user permissions. We use ODBC to connect, and the admin before me always connected using the SA name. I also notice in enterprise manager that in all the databases, there arn't many users listed that still work here, (we have about 9 people total that use SQL).

This brings me to another question: Is it because we use the SA name to authenticate to SQL in ODBC that makes having users in SQL obsolete?

If this is the case, I want to authenticate with users after the domain change. So would I basically be starting from scratch anyway? (user permission-wise)

Also, thank you unclerico for posting in another thread. I'm hoping to try it over the weekend if I feel well enough assured that it will work.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top