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 Drive Letters

I am new to SQL server so any guidance is much appreciated.
We have two logical drives for our SQL server.We are upgrading from a
smaller driver to a bigger one. We have copied everything from one drive to
the other after doing so we decided the easiest thing to do would be to
change the drive letter to what the old drive used to be. We went into disk
management and tried to do it from there but had no luck with getting the
cluster or the services restarted and back up. This seems like such an easy
thing to do but I can not seem to get it right! Again, if anyone has any
advice it would be greatly appreciated.
Changing a drive letter "under the covers" works, but you have to do a few
tweaks to make it work on a cluster. Make sure you have created the new
disk as a cluster resource. Put it in the SQL server group and make the SQL
service dependant on the new disk. If that doesn't fix it, check the
application and system logs to see what SQL and/or the cluster service is
complaining about.
Geoff N. Hiten
"Mel" <Mel@.discussions.microsoft.com> wrote in message
news:8B9A7516-D136-4044-9284-3F5E4590D197@.microsoft.com...
>I am new to SQL server so any guidance is much appreciated.
> We have two logical drives for our SQL server.We are upgrading from a
> smaller driver to a bigger one. We have copied everything from one drive
> to
> the other after doing so we decided the easiest thing to do would be to
> change the drive letter to what the old drive used to be. We went into
> disk
> management and tried to do it from there but had no luck with getting the
> cluster or the services restarted and back up. This seems like such an
> easy
> thing to do but I can not seem to get it right! Again, if anyone has any
> advice it would be greatly appreciated.
|||Mel
Check out the ClusterRecovery.exe from
http://www.microsoft.com/downloads/d...displaylang=en
If your new to clustering and want to swap disks, this might be a little
more user friendly for you. This will take care of the dependancy issue as
well.
Good Luck
Regards
CT
"Mel" wrote:

> I am new to SQL server so any guidance is much appreciated.
> We have two logical drives for our SQL server.We are upgrading from a
> smaller driver to a bigger one. We have copied everything from one drive to
> the other after doing so we decided the easiest thing to do would be to
> change the drive letter to what the old drive used to be. We went into disk
> management and tried to do it from there but had no luck with getting the
> cluster or the services restarted and back up. This seems like such an easy
> thing to do but I can not seem to get it right! Again, if anyone has any
> advice it would be greatly appreciated.