Changing physical SQL Server

Hello all,

We are in the process of upgrading our SQL physical server (with SS2k). In
the process we will change the OS form NT4 to W2K. What is the best way to
copy all my databases and SQL logins, roles, jobs, alerts, etc. from my
actual (old) SQL Server to my new one?

Thanks for your time.

YannickTransfer logins: see msft support article KB 246133

Transfer databases: backup and restore the Dbs on the new server. This
should copy the permissions and roles. (I recommend ftp'ing the backup
files from one server to another. I learned this the hard way.)

Transfer jobs & alerts: I don't know an easy way. I used EM to
generate sql scripts for each one and then ran them on the new server.|||Thanks for that Louis.

Yannick

"louis" <louisducnguyen@.gmail.com> wrote in message
news:1105044803.604211.75490@.z14g2000cwz.googlegro ups.com...
> Transfer logins: see msft support article KB 246133
> Transfer databases: backup and restore the Dbs on the new server. This
> should copy the permissions and roles. (I recommend ftp'ing the backup
> files from one server to another. I learned this the hard way.)
> Transfer jobs & alerts: I don't know an easy way. I used EM to
> generate sql scripts for each one and then ran them on the new server.

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 IP

I am using merge replication with SQL ver 7, on a NT4 box. I need to
move one of seven subscribing servers to a new location which means
changing the IP address. I want to do the move without taking down
replication if possible. My plan is to move the box and change to new
IP address. Then update the WINS entry for the new address, and have
replication resume.
Should this work? Let me know if anyone can think of potential
problems.
thanks in advance, Jim
It should work. Replication is sensitive to subscriber name changes, not ip
address changes. Just make sure that you did not hard code an ip address in
the alias you may have created for this server in client network utility.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jim" <ndpace@.att.net> wrote in message
news:c834d859.0409291039.4499a3df@.posting.google.c om...
> I am using merge replication with SQL ver 7, on a NT4 box. I need to
> move one of seven subscribing servers to a new location which means
> changing the IP address. I want to do the move without taking down
> replication if possible. My plan is to move the box and change to new
> IP address. Then update the WINS entry for the new address, and have
> replication resume.
> Should this work? Let me know if anyone can think of potential
> problems.
> thanks in advance, Jim
|||Guys!
I have the similar problem, but the server name will be changed also.
I believe it should be enough to call a kind of system SP, which will
replace old box names to the new ones. Could you point me to the right
direction?
Best regards,
Serge.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uEUCatlpEHA.1816@.TK2MSFTNGP09.phx.gbl...
> It should work. Replication is sensitive to subscriber name changes, not
ip
> address changes. Just make sure that you did not hard code an ip address
in
> the alias you may have created for this server in client network utility.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jim" <ndpace@.att.net> wrote in message
> news:c834d859.0409291039.4499a3df@.posting.google.c om...
>
|||Serge,
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
This will rename your server, but you'll need to set up
the publications from fresh afterwards.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)