Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DLTaylor
Posting Yak Master
136 Posts |
 Posted - 2009-07-16 : 08:04:49
|
| Hello,I have a server called PURPLE with an instance of SQL 2000 installed called PURPLESQL server Enterprise EditionVersion: 8.00.760 (SP3)Windows Server 2003The server is coming to the end of its life…and we are about to buy a brand new server.I am responsible for getting the new server up and running and I realise I have options to consider!!!!As I don’t do this as my day job I wanted to see if you can point me in the right direction…Note:I would like to upgrade the SQL version to SQL 2005 – during this upgradeThe server named PURPLE had 200+ JOBS & DTS packages along with ODBC drivers to connect to various other data sources, software is also installed that is executed during DTS runtime… and is very much an integral part of our business. (What I’m trying to say is that there are loads of things on the server that may influence my plan of action…)I realise I’m doing 2 things here; upgrading from 2000 to 2005 and changing ServerWhat are my options?• Build new server called PURPLE2 and install SQL 2005 and transfer – the mdf, log, DTS to SSIS, security and software installations etc…?• Upgrade the original PUPRLE server to SQL 2005 and then put an image on the new PURPLE2 server..• Can I create a new server called PURPLE and then ‘put all the old stuff on the new server’ – shutdown the old server and start up the new PURPLE server – and hopefully all the jobs \ DTS \ ODBC etc will run … and then do the upgrade to 2005 on the new server…I appreciate my options are vague – however I wanted to get the ball rolling – I’m not sure if there are any good articles that relate to my situation etc..You will realise I’m an accidental DBA in this situation … any help will be most welcomed! |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-07-16 : 08:48:55
|
| I think the first thing you need to do is run the databases through the upgrade advisor or if you have any third party apps, then contact the suppliers and get them to confirm your apps are 2005 compatible. |
 |
|
|
DLTaylor
Posting Yak Master
136 Posts |
Posted - 2009-07-16 : 08:59:20
|
| Thanks RickDI will run the upgrade advisor - lets assume i fix any issues...:-)Do you think i should upgrade to 2005 1st on current server...then migrate to new server…which is a different named server e.g. PURPLE2 ? Thanks |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-07-16 : 09:42:31
|
| If you want to detach..attach, you will need to. If you are restoring a backup, you do not. |
|
|
|
tosscrosby
Aged Yak Warrior
676 Posts |
Posted - 2009-07-16 : 10:08:17
|
| Ummm, I took my databases offline on SQL2000 (serverA), copied the mdf/ldf files to my new server (serverB) and did an attach of the files. Once I was satisifed that all was well, I moved the compatability level to 9.0, recreated my indexes, and off we went. Backup/restore works fine too but I took the fastest path, for me, to get my databases onto SQL2005.Terry-- Procrastinate now! |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-07-16 : 10:18:05
|
| hmm, I didn't think you could, but then again.. |
|
|
|
|
|
|
|
|
Options when upgrading SERVER and SQL 2000 to 2005