I would like to post this as answer what is point in upgrading to SQL server 2000 which is outdated completely without any support. Even it is not good for testing purpose. Its like using typewriter in era or super computers.
Dont uninstall personal edition first. Install enterprise move databses by backup restore method. If you restore master msdb databases you would not need to move logins and jobs.
Please refer to below link
https://www.barracudaware.com/files/docs/9.00/help/restoring_microsoft_sql_server_2000_master_database.html
As mentioned in the comments, it is not recommended to install any MySQL version (or anything else) that is not 'Generally Available (GA)' in production.
But whether you end up upgrading when it is GA depends on your product and your environment. At the current time, there is this summary of features and improvements introduced in 5.7. In general, if your product is running fine and is relatively static to the point of never needing those features, then you will likely never need to upgrade.
To address the question of how you would upgrade a replication topology from 5.6 to 5.7, there are two main documents to review and familiarize yourself with:
The content of these links will undoubtedly change before 5.7 is GA, but they are extremely important for understanding the incompatible changes and known issues of upgrading so you can avoid them.
I will highlight specifically a change in the way various SHOW commands are handled. The underlying tables for SHOW [GLOBAL|SESSION|LOCAL] STATUS, SHOW [GLOBAL|SESSION|LOCAL] VARIABLES, SHOW SLAVE STATUS are moving from information_schema to performance_schema.
In the current release candidate (5.7.8-rc), access to these performance_schema tables is not enabled by default, and would show an error such as this:
mysql> show global variables like 'hostname';
ERROR 1142 (42000): SELECT command denied to user 'normal_user'@'my_host' for table 'global_variables'
The workaround is to grant SELECT to performance_schema tables for your user. You can read more about the problem and the workaround in this blogpost from Shlomi Noach. This is fixed in 5.7.9, which is not out yet.
Best Answer
mysql_upgrade.