Hi all,
I've got an scenario that hopefull you can evaluate for me. We have a
Windows 2000 server running AD that has an access database in the data
partition. The Access database is getting huge and we have just
ordered a server to run SQLSERVER on. I'm not worried about getting
the new server on the domain and getting AD to replicate. I also have
a DBA that is going to import the Access database into SQLSERVER and
handle all of the odbc work. I"m going to keep the orignal sever
running to handle domain logons and user data storage. It will also be
nice to have some AD replication in the even of a server failure.
Back to my original server. After my new server is implemented, I'd
like to take the original server down to install new drives and a
bigger processor. What kind of trouble am I going to cause, since this
is the original server in our domain that I'm speaking of. As long as
I rename the server with the original name am I ok? By taking it down
to upgrade the components and then bringing it up with a fresh load,
what type of interopability issues am I dealing with among the users
(there are only 10) and the SQL server?
I'm just assuming the the original server is assigned some unique
class ID and bringing it backup with the same server name and domain
name will still cause havoc. Thanks in advance for your thoughts and
expertise.
Steve
|