You will have to excuse my lack of knowledge with SQL but I have been tasked with retirting some of our oldest servers which are currently still used in production. Most of them are fine but I have hit an Windows 2000 Server with SQL 2000 and one of the databases is for our intraserver. I need to devise a plan to move this database over to an SQL 2005 or 2008 server.
Any ideas on where I should start.
Also as its a really old server I think there could be other db running on there. Does anyone know how I can find out what other databases are running on that server. If I go to SQL server enterprise manager, go to databases they are absolutely loads of db's but I have been told that most of them have been migrated over to other servers since.
I went to current activity and checked the locks/object section and this I think is showing me what databases are currently used because I am assuming if they are locked it means that they are in use.
Does anyone know of a better way?
Any sites/books others would recommend for a newbie DB administrator it would be greatly appreciated. BTW these servers are VM's on a VMware ESX4 cluster.
Am not a SQL guru, but as i understood it works like this: As for the databases you could back them up using SQL and restore them to the SQL 2005/2008 server. The logins are a pain, because only the database is restored, not the logins on the server.
An easier method is to replicate the databases to the newer servers. The logins are then created automatically.
'People who think they know everything are a great annoyance to those of us who do. ' Quote by Isaac Asimov
You can then detach and attach all the databases you move. You could rename the new server to match the old server's name during the cutover, if it is difficult to update the configuration of the applications in question.
Michael D'Angelo (former)MVP-MIIS, Pace University Senior Systems Administrator (Windows)(MS)NMDANGE PhoeniX WorX Systems Administrator. If you play Total Annihilation, please join us. http://www.phoenixworx.org