Go to your SQL 2000 server and backup your ePO database… If not then it is your own fault if you lose data.
Once backed up, right click on your ePO database and choose Properties.
Choose the Data Files tab and notate the location of the database.
Choose the Transaction Log tab and notate the location of the log files.
Press cancel to close the window.
Right click on your ePO database and choose All Tasks and then Take Offline.
If you receive an error about having connection open then press ok to the error. Re-right click on the ePO database and choose All Tasks and then select Detach database. Under database status, press the clear button. That will clear all the connections to the database. Press cancel to close the window and then repeat step 7.
Open explorer and go to the folder that you notated in step 4.
Copy the MDF and LDF files that are assigned to your ePO database and paste to your new SQL2005 location. DO NOT CUT & PASTE.
Within Microsoft SQL Server Management Studio (SQL 2005) right click on Databases and then choose Attach.
Press the Add button and then locate your MDF file attached to your ePO database. Make sure it is the location that you pasted in step 10.
Once the database has been attached, then go back to SQL2000 server and put your ePO database back online.
Go to your ePO server and restart the McAfee ePO services.
Once re-started, open ePO console on your ePO server. If you get an error make sure that services and databases are online.
Re: Migrating ePO from 4.0 to 4.6 on a server running SQL2000 and SQL2005
After step 11 I would also recommend putting the database in 2005 mode (attaching a SQL 2000 database will set the mode to 2000 compatibility by default). Otherwise it could be that your ePO 4.5 install will fail (no SQL 2000 support).