import to mysql5.7.17 old version mysql5.1 mysqldump
http://mysqlserverteam.com/upgrading-directly-from-mysql-5-0-to-5-7-with-
I think no matter there import old dump to new version 5.7.17 and do mysql_upgrade. That also safety method .
The article was written 2 years ago.
I wonder if even now I must do like that upgrade step by step?
mysql
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
migrated from stackoverflow.com Nov 3 '17 at 20:49
This question came from our site for professional and enthusiast programmers.
add a comment |
http://mysqlserverteam.com/upgrading-directly-from-mysql-5-0-to-5-7-with-
I think no matter there import old dump to new version 5.7.17 and do mysql_upgrade. That also safety method .
The article was written 2 years ago.
I wonder if even now I must do like that upgrade step by step?
mysql
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
migrated from stackoverflow.com Nov 3 '17 at 20:49
This question came from our site for professional and enthusiast programmers.
1
Maybe? Possibly? Try it on a test server and find out. It normally depends on what database features you've made use of. I've had migrations that were painless, others that were a pain in the butt.
– tadman
Nov 2 '17 at 16:48
so ,do you mean not enough mysql_upgrade
– void
Nov 3 '17 at 2:37
I mean if you're using features that were removed or fundamentally changed you will have problems, but if it's just basic table data you're probably fine.
– tadman
Nov 3 '17 at 16:02
add a comment |
http://mysqlserverteam.com/upgrading-directly-from-mysql-5-0-to-5-7-with-
I think no matter there import old dump to new version 5.7.17 and do mysql_upgrade. That also safety method .
The article was written 2 years ago.
I wonder if even now I must do like that upgrade step by step?
mysql
http://mysqlserverteam.com/upgrading-directly-from-mysql-5-0-to-5-7-with-
I think no matter there import old dump to new version 5.7.17 and do mysql_upgrade. That also safety method .
The article was written 2 years ago.
I wonder if even now I must do like that upgrade step by step?
mysql
mysql
asked Nov 2 '17 at 16:41
void
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 20 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
migrated from stackoverflow.com Nov 3 '17 at 20:49
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Nov 3 '17 at 20:49
This question came from our site for professional and enthusiast programmers.
1
Maybe? Possibly? Try it on a test server and find out. It normally depends on what database features you've made use of. I've had migrations that were painless, others that were a pain in the butt.
– tadman
Nov 2 '17 at 16:48
so ,do you mean not enough mysql_upgrade
– void
Nov 3 '17 at 2:37
I mean if you're using features that were removed or fundamentally changed you will have problems, but if it's just basic table data you're probably fine.
– tadman
Nov 3 '17 at 16:02
add a comment |
1
Maybe? Possibly? Try it on a test server and find out. It normally depends on what database features you've made use of. I've had migrations that were painless, others that were a pain in the butt.
– tadman
Nov 2 '17 at 16:48
so ,do you mean not enough mysql_upgrade
– void
Nov 3 '17 at 2:37
I mean if you're using features that were removed or fundamentally changed you will have problems, but if it's just basic table data you're probably fine.
– tadman
Nov 3 '17 at 16:02
1
1
Maybe? Possibly? Try it on a test server and find out. It normally depends on what database features you've made use of. I've had migrations that were painless, others that were a pain in the butt.
– tadman
Nov 2 '17 at 16:48
Maybe? Possibly? Try it on a test server and find out. It normally depends on what database features you've made use of. I've had migrations that were painless, others that were a pain in the butt.
– tadman
Nov 2 '17 at 16:48
so ,do you mean not enough mysql_upgrade
– void
Nov 3 '17 at 2:37
so ,do you mean not enough mysql_upgrade
– void
Nov 3 '17 at 2:37
I mean if you're using features that were removed or fundamentally changed you will have problems, but if it's just basic table data you're probably fine.
– tadman
Nov 3 '17 at 16:02
I mean if you're using features that were removed or fundamentally changed you will have problems, but if it's just basic table data you're probably fine.
– tadman
Nov 3 '17 at 16:02
add a comment |
1 Answer
1
active
oldest
votes
Plan A: Take a dump of 5.1 data (with a new mysqldump if practical). Then load it onto a freshly installed 5.7.
Plan B: Upgrade in place 5.5, run its mysql_upgrade, and test. Repeat to get to 5.6. Repeat again to 5.7. Each time you would be running a new mysql_upgrade.
Since there are 3 "major" upgrades, there are many things that might cause hiccups (with either Plan). Or it might go smoothly.
The article is an old one, and the advice had not changed substantively in perhaps 15 years.
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f190082%2fimport-to-mysql5-7-17-old-version-mysql5-1-mysqldump%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Plan A: Take a dump of 5.1 data (with a new mysqldump if practical). Then load it onto a freshly installed 5.7.
Plan B: Upgrade in place 5.5, run its mysql_upgrade, and test. Repeat to get to 5.6. Repeat again to 5.7. Each time you would be running a new mysql_upgrade.
Since there are 3 "major" upgrades, there are many things that might cause hiccups (with either Plan). Or it might go smoothly.
The article is an old one, and the advice had not changed substantively in perhaps 15 years.
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
add a comment |
Plan A: Take a dump of 5.1 data (with a new mysqldump if practical). Then load it onto a freshly installed 5.7.
Plan B: Upgrade in place 5.5, run its mysql_upgrade, and test. Repeat to get to 5.6. Repeat again to 5.7. Each time you would be running a new mysql_upgrade.
Since there are 3 "major" upgrades, there are many things that might cause hiccups (with either Plan). Or it might go smoothly.
The article is an old one, and the advice had not changed substantively in perhaps 15 years.
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
add a comment |
Plan A: Take a dump of 5.1 data (with a new mysqldump if practical). Then load it onto a freshly installed 5.7.
Plan B: Upgrade in place 5.5, run its mysql_upgrade, and test. Repeat to get to 5.6. Repeat again to 5.7. Each time you would be running a new mysql_upgrade.
Since there are 3 "major" upgrades, there are many things that might cause hiccups (with either Plan). Or it might go smoothly.
The article is an old one, and the advice had not changed substantively in perhaps 15 years.
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
Plan A: Take a dump of 5.1 data (with a new mysqldump if practical). Then load it onto a freshly installed 5.7.
Plan B: Upgrade in place 5.5, run its mysql_upgrade, and test. Repeat to get to 5.6. Repeat again to 5.7. Each time you would be running a new mysql_upgrade.
Since there are 3 "major" upgrades, there are many things that might cause hiccups (with either Plan). Or it might go smoothly.
The article is an old one, and the advice had not changed substantively in perhaps 15 years.
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
answered Nov 4 '17 at 2:03
Rick JamesRick James
42.9k22259
42.9k22259
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f190082%2fimport-to-mysql5-7-17-old-version-mysql5-1-mysqldump%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Maybe? Possibly? Try it on a test server and find out. It normally depends on what database features you've made use of. I've had migrations that were painless, others that were a pain in the butt.
– tadman
Nov 2 '17 at 16:48
so ,do you mean not enough mysql_upgrade
– void
Nov 3 '17 at 2:37
I mean if you're using features that were removed or fundamentally changed you will have problems, but if it's just basic table data you're probably fine.
– tadman
Nov 3 '17 at 16:02