Changing machine name & IP number on SQL Server 7.

Hi all!

We run a NT4 server machine running SQL 7 which contains some vital data on older databases. This machine was PDC for a long time, untill we got a new win2k server, which got the same machine name and IP number as the old NT4 machine which isn't yet connected to the AD. This new server does SQL 2000.

Since it's still important for us to have access to the SQL 7 data which cannot be used on SQL2000 server, I want to put the NT4 machine in the Win2k domain, but when I change the server's name and IP adress into something free (machine name and IP number are both taken over by new server) the SQL 7 server won't start anymore.

Is there anyone out there that knows how to solve this problem?

Thanks!!!! A LOT! :D :DI think you can run SQL 7 on the same machine as SQL 2000 and they won't bump into eachother.

blindman|||You can have SQL 2000 and one of the previous versions on the same machine. See if you want to do this. If not, see if the following article resolves your issues.

http://www.databasejournal.com/features/mssql/print.php/10894_2194711_3

All the best

Changing domains and restoring db's

I have a 2000 server that also runs SQL 7.0.
This server is a PDC of domain "A". It also happens to be
the only server on the domain.
I am tasked to eliminate this domain and bring this server
into domain "B". I have been told that unfortunately, I
will have to FDISK this guy to scratch and reinstall OS,
SQL, everythng, to bring him into new domain.
Is this true?
Also, the SQL has some pretty big databases and of course
they are backed up nightly, but I was hoping not to have
to restore these db's from tape but instead, copy the
databases over to another server, then copy them back
after I have reinstalled the server and brought him into
domain "B".
Can I do this and what do I need to know how to go about
this?"Rick" <anonymous@.discussions.microsoft.com> wrote in message
news:00aa01c39991$10541780$a501280a@.phx.gbl...
> I have a 2000 server that also runs SQL 7.0.
> This server is a PDC of domain "A". It also happens to be
> the only server on the domain.
> I am tasked to eliminate this domain and bring this server
> into domain "B". I have been told that unfortunately, I
> will have to FDISK this guy to scratch and reinstall OS,
> SQL, everythng, to bring him into new domain.
> Is this true?
> Also, the SQL has some pretty big databases and of course
> they are backed up nightly, but I was hoping not to have
> to restore these db's from tape but instead, copy the
> databases over to another server, then copy them back
> after I have reinstalled the server and brought him into
> domain "B".
> Can I do this and what do I need to know how to go about
> this?
First make sure that the SQL services are not running under a domain
account. Go to the services applet and change the SQL services to use a
local system login (note: from this point SQL won't be able to use network
resources).
Then run dcpromo. Tell the wizard that this is the last domain controller
in the domain. This should turn it into a standalone server. Then you
should be able to join domain B and run the SQL services under a new domain
account.
To transfer databases from one SQL server to another use the DTS wizard from
Enterprise Manager. It has an option to transfer all objects from one SQL
database to another.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 22/10/2003|||So you're saying that I do not have to FDisk this server
and reinstall everything? I can just turn it into a
standalone server first and then bring it into a new
domain?
If that is the case, then I wouldn't have to do anything
to the SQL portion right? I'd just leave it as is?