SQL Server: are backups between same major/minor version but different build compatible among them?
For example a backup executed on SQL Server 10.50.6000.34 can always be restored on SQL Server 10.50.4000.0
or 10.50.2500.0
. All of them indicates an SQL Server 2008 R2 (10.50.xxxx.xx) but different build (service pack 2,3 etc).
From some tests that I did seems that there are no problems but I want to know if this is always possible.
sql-server backup restore
add a comment |
For example a backup executed on SQL Server 10.50.6000.34 can always be restored on SQL Server 10.50.4000.0
or 10.50.2500.0
. All of them indicates an SQL Server 2008 R2 (10.50.xxxx.xx) but different build (service pack 2,3 etc).
From some tests that I did seems that there are no problems but I want to know if this is always possible.
sql-server backup restore
add a comment |
For example a backup executed on SQL Server 10.50.6000.34 can always be restored on SQL Server 10.50.4000.0
or 10.50.2500.0
. All of them indicates an SQL Server 2008 R2 (10.50.xxxx.xx) but different build (service pack 2,3 etc).
From some tests that I did seems that there are no problems but I want to know if this is always possible.
sql-server backup restore
For example a backup executed on SQL Server 10.50.6000.34 can always be restored on SQL Server 10.50.4000.0
or 10.50.2500.0
. All of them indicates an SQL Server 2008 R2 (10.50.xxxx.xx) but different build (service pack 2,3 etc).
From some tests that I did seems that there are no problems but I want to know if this is always possible.
sql-server backup restore
sql-server backup restore
edited Feb 15 at 8:50
Glorfindel
1,0111816
1,0111816
asked Feb 15 at 8:20
res1res1
1234
1234
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It should always be possible to restore within the same version, irrespective of service packs and other updates. Having said that, it is also recommend that you keep up with service releases so in an ideal world this won't be an issue.
One thing to note that throws some people off is that 2008 and 2008R2 are considered different versions (not one being a service release of the other) so you can't restore a backup from the latter with the former.
1
This is almost, but not completely true -- notably, SQL Server 2005 SP2 introduced vardecimal storage, giving a version (612) that cannot be restored on earlier versions of 2005 (which use 611). This is a rare situation, though, and I don't see MS repeating it any time soon. List of internal database versions.
– Jeroen Mostert
Feb 15 at 12:48
Ah yes, I'd forgotten that niggle. Though if you did explicitly enablevardecimal
in 2005sp2, as it isn't available by default, you are hopefully aware of the implications. 2005 is out of its support lifetime (as of 2016-04-12) anyway, though soon (2019-07-09) 2008 and 2008r2 will be too.
– David Spillett
Feb 15 at 13:00
A caution here you cannot restore backup system databases of higher version no (like 10.50.6000) on lower version like(10.50.4000).
– Shanky
Feb 15 at 15:21
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%2f229824%2fsql-server-are-backups-between-same-major-minor-version-but-different-build-com%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
It should always be possible to restore within the same version, irrespective of service packs and other updates. Having said that, it is also recommend that you keep up with service releases so in an ideal world this won't be an issue.
One thing to note that throws some people off is that 2008 and 2008R2 are considered different versions (not one being a service release of the other) so you can't restore a backup from the latter with the former.
1
This is almost, but not completely true -- notably, SQL Server 2005 SP2 introduced vardecimal storage, giving a version (612) that cannot be restored on earlier versions of 2005 (which use 611). This is a rare situation, though, and I don't see MS repeating it any time soon. List of internal database versions.
– Jeroen Mostert
Feb 15 at 12:48
Ah yes, I'd forgotten that niggle. Though if you did explicitly enablevardecimal
in 2005sp2, as it isn't available by default, you are hopefully aware of the implications. 2005 is out of its support lifetime (as of 2016-04-12) anyway, though soon (2019-07-09) 2008 and 2008r2 will be too.
– David Spillett
Feb 15 at 13:00
A caution here you cannot restore backup system databases of higher version no (like 10.50.6000) on lower version like(10.50.4000).
– Shanky
Feb 15 at 15:21
add a comment |
It should always be possible to restore within the same version, irrespective of service packs and other updates. Having said that, it is also recommend that you keep up with service releases so in an ideal world this won't be an issue.
One thing to note that throws some people off is that 2008 and 2008R2 are considered different versions (not one being a service release of the other) so you can't restore a backup from the latter with the former.
1
This is almost, but not completely true -- notably, SQL Server 2005 SP2 introduced vardecimal storage, giving a version (612) that cannot be restored on earlier versions of 2005 (which use 611). This is a rare situation, though, and I don't see MS repeating it any time soon. List of internal database versions.
– Jeroen Mostert
Feb 15 at 12:48
Ah yes, I'd forgotten that niggle. Though if you did explicitly enablevardecimal
in 2005sp2, as it isn't available by default, you are hopefully aware of the implications. 2005 is out of its support lifetime (as of 2016-04-12) anyway, though soon (2019-07-09) 2008 and 2008r2 will be too.
– David Spillett
Feb 15 at 13:00
A caution here you cannot restore backup system databases of higher version no (like 10.50.6000) on lower version like(10.50.4000).
– Shanky
Feb 15 at 15:21
add a comment |
It should always be possible to restore within the same version, irrespective of service packs and other updates. Having said that, it is also recommend that you keep up with service releases so in an ideal world this won't be an issue.
One thing to note that throws some people off is that 2008 and 2008R2 are considered different versions (not one being a service release of the other) so you can't restore a backup from the latter with the former.
It should always be possible to restore within the same version, irrespective of service packs and other updates. Having said that, it is also recommend that you keep up with service releases so in an ideal world this won't be an issue.
One thing to note that throws some people off is that 2008 and 2008R2 are considered different versions (not one being a service release of the other) so you can't restore a backup from the latter with the former.
edited Feb 15 at 11:00
answered Feb 15 at 8:59
David SpillettDavid Spillett
22.9k23267
22.9k23267
1
This is almost, but not completely true -- notably, SQL Server 2005 SP2 introduced vardecimal storage, giving a version (612) that cannot be restored on earlier versions of 2005 (which use 611). This is a rare situation, though, and I don't see MS repeating it any time soon. List of internal database versions.
– Jeroen Mostert
Feb 15 at 12:48
Ah yes, I'd forgotten that niggle. Though if you did explicitly enablevardecimal
in 2005sp2, as it isn't available by default, you are hopefully aware of the implications. 2005 is out of its support lifetime (as of 2016-04-12) anyway, though soon (2019-07-09) 2008 and 2008r2 will be too.
– David Spillett
Feb 15 at 13:00
A caution here you cannot restore backup system databases of higher version no (like 10.50.6000) on lower version like(10.50.4000).
– Shanky
Feb 15 at 15:21
add a comment |
1
This is almost, but not completely true -- notably, SQL Server 2005 SP2 introduced vardecimal storage, giving a version (612) that cannot be restored on earlier versions of 2005 (which use 611). This is a rare situation, though, and I don't see MS repeating it any time soon. List of internal database versions.
– Jeroen Mostert
Feb 15 at 12:48
Ah yes, I'd forgotten that niggle. Though if you did explicitly enablevardecimal
in 2005sp2, as it isn't available by default, you are hopefully aware of the implications. 2005 is out of its support lifetime (as of 2016-04-12) anyway, though soon (2019-07-09) 2008 and 2008r2 will be too.
– David Spillett
Feb 15 at 13:00
A caution here you cannot restore backup system databases of higher version no (like 10.50.6000) on lower version like(10.50.4000).
– Shanky
Feb 15 at 15:21
1
1
This is almost, but not completely true -- notably, SQL Server 2005 SP2 introduced vardecimal storage, giving a version (612) that cannot be restored on earlier versions of 2005 (which use 611). This is a rare situation, though, and I don't see MS repeating it any time soon. List of internal database versions.
– Jeroen Mostert
Feb 15 at 12:48
This is almost, but not completely true -- notably, SQL Server 2005 SP2 introduced vardecimal storage, giving a version (612) that cannot be restored on earlier versions of 2005 (which use 611). This is a rare situation, though, and I don't see MS repeating it any time soon. List of internal database versions.
– Jeroen Mostert
Feb 15 at 12:48
Ah yes, I'd forgotten that niggle. Though if you did explicitly enable
vardecimal
in 2005sp2, as it isn't available by default, you are hopefully aware of the implications. 2005 is out of its support lifetime (as of 2016-04-12) anyway, though soon (2019-07-09) 2008 and 2008r2 will be too.– David Spillett
Feb 15 at 13:00
Ah yes, I'd forgotten that niggle. Though if you did explicitly enable
vardecimal
in 2005sp2, as it isn't available by default, you are hopefully aware of the implications. 2005 is out of its support lifetime (as of 2016-04-12) anyway, though soon (2019-07-09) 2008 and 2008r2 will be too.– David Spillett
Feb 15 at 13:00
A caution here you cannot restore backup system databases of higher version no (like 10.50.6000) on lower version like(10.50.4000).
– Shanky
Feb 15 at 15:21
A caution here you cannot restore backup system databases of higher version no (like 10.50.6000) on lower version like(10.50.4000).
– Shanky
Feb 15 at 15:21
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%2f229824%2fsql-server-are-backups-between-same-major-minor-version-but-different-build-com%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