Temporarily moving a SQL Server 2016 database to SQL Server 2017 and then moving back. Is it possible?SQL Server: Simple database restore with overwriteSQL Server 2016 Express restore size limitMoving Databases between Instances of different Versions of SQL ServergMSAs and SQL Server 2017Mixing SQL Server 2016 and 2017 in a distributed availability groupUpgrade to SQL Server 2017 FailsUpgrade SQL Server 2014 AG to SQL Server 2017 AG
The relationship of noch nicht and the passive voice
How should errors be reported in scientific libraries?
What is the origin of the "being immortal sucks" trope?
When is the earliest in Earth history when Grade 5 Titanium alloy could be made, assuming one knows the formula and has the feedstock?
Why was Java 8 left out from Debian Buster?
Paradox regarding phase transitions in relativistic systems
Should I inform my future product owner that there is a good chance that a team member will leave the company soon?
Is the name of an interval between two notes unique and absolute?
All numbers in a 5x5 Minesweeper grid
Can Brexit be undone in an emergency?
As an employer, can I compel my employees to vote?
How to influence manager to not schedule team meetings during lunch?
Is it possible that the shadow of The Moon is a single dot during solar eclipse?
Why are there two bearded faces wearing red hats on my stealth bomber icon?
Why do we need to use transistors when building an OR gate?
Manager manipulates my leaves, what's in it for him?
Is there a connection between IT and Ghostbusters?
Twelve Minesweeper mines that make twelve 4s
How is underwater propagation of sound possible?
I was cheated into a job and want to leave ASAP, what do I tell my interviewers?
What did the controller say during my approach to land (audio clip)?
Did HaShem ever command a Navi (Prophet) to break a law?
What are sources for Magic Items that are not adventure-specific?
US entry with tourist visa but past alcohol abuse
Temporarily moving a SQL Server 2016 database to SQL Server 2017 and then moving back. Is it possible?
SQL Server: Simple database restore with overwriteSQL Server 2016 Express restore size limitMoving Databases between Instances of different Versions of SQL ServergMSAs and SQL Server 2017Mixing SQL Server 2016 and 2017 in a distributed availability groupUpgrade to SQL Server 2017 FailsUpgrade SQL Server 2014 AG to SQL Server 2017 AG
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
If I take a backup of a database from a SQL Server 2016 instance and then restore it to a 2017 instance to do some work on it.
Can I then turn around and back up that database from the 2017 instance and use that to overwrite the original version on the 2016 instance?
sql-server backup sql-server-2016 restore sql-server-2017
New contributor
add a comment
|
If I take a backup of a database from a SQL Server 2016 instance and then restore it to a 2017 instance to do some work on it.
Can I then turn around and back up that database from the 2017 instance and use that to overwrite the original version on the 2016 instance?
sql-server backup sql-server-2016 restore sql-server-2017
New contributor
add a comment
|
If I take a backup of a database from a SQL Server 2016 instance and then restore it to a 2017 instance to do some work on it.
Can I then turn around and back up that database from the 2017 instance and use that to overwrite the original version on the 2016 instance?
sql-server backup sql-server-2016 restore sql-server-2017
New contributor
If I take a backup of a database from a SQL Server 2016 instance and then restore it to a 2017 instance to do some work on it.
Can I then turn around and back up that database from the 2017 instance and use that to overwrite the original version on the 2016 instance?
sql-server backup sql-server-2016 restore sql-server-2017
sql-server backup sql-server-2016 restore sql-server-2017
New contributor
New contributor
edited 6 hours ago
Learning_DBAdmin
1,2453 silver badges20 bronze badges
1,2453 silver badges20 bronze badges
New contributor
asked 8 hours ago
djohnson10djohnson10
1234 bronze badges
1234 bronze badges
New contributor
New contributor
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
No, this is not possible.SQL Server 2017 backups cannot be restored by any earlier version of SQL Server ref
Also, regarding detatching and reattaching per the docs:
After being attached to SQL Server 2017, the database is available
immediately and is automatically upgraded. This prevents the database
from being used with an older version of the Database Engine
Also, not sure you care about the compatibility level, but FYSA:
If the compatibility level of a user database is 100 or higher before
upgrade, it remains the same after upgrade. If the compatibility level
is 90 before upgrade in the upgraded database, the compatibility level
is set to 100, which is the lowest supported compatibility level in
SQL Server 2017.
Additionally, I believe you question is about a user database, but if it isn't:
Backups of master, model and msdb that were created by using an
earlier version of SQL Server cannot be restored by SQL Server 2017
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/4.0/"u003ecc by-sa 4.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
);
);
djohnson10 is a new contributor. Be nice, and check out our Code of Conduct.
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%2f248991%2ftemporarily-moving-a-sql-server-2016-database-to-sql-server-2017-and-then-moving%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
No, this is not possible.SQL Server 2017 backups cannot be restored by any earlier version of SQL Server ref
Also, regarding detatching and reattaching per the docs:
After being attached to SQL Server 2017, the database is available
immediately and is automatically upgraded. This prevents the database
from being used with an older version of the Database Engine
Also, not sure you care about the compatibility level, but FYSA:
If the compatibility level of a user database is 100 or higher before
upgrade, it remains the same after upgrade. If the compatibility level
is 90 before upgrade in the upgraded database, the compatibility level
is set to 100, which is the lowest supported compatibility level in
SQL Server 2017.
Additionally, I believe you question is about a user database, but if it isn't:
Backups of master, model and msdb that were created by using an
earlier version of SQL Server cannot be restored by SQL Server 2017
add a comment
|
No, this is not possible.SQL Server 2017 backups cannot be restored by any earlier version of SQL Server ref
Also, regarding detatching and reattaching per the docs:
After being attached to SQL Server 2017, the database is available
immediately and is automatically upgraded. This prevents the database
from being used with an older version of the Database Engine
Also, not sure you care about the compatibility level, but FYSA:
If the compatibility level of a user database is 100 or higher before
upgrade, it remains the same after upgrade. If the compatibility level
is 90 before upgrade in the upgraded database, the compatibility level
is set to 100, which is the lowest supported compatibility level in
SQL Server 2017.
Additionally, I believe you question is about a user database, but if it isn't:
Backups of master, model and msdb that were created by using an
earlier version of SQL Server cannot be restored by SQL Server 2017
add a comment
|
No, this is not possible.SQL Server 2017 backups cannot be restored by any earlier version of SQL Server ref
Also, regarding detatching and reattaching per the docs:
After being attached to SQL Server 2017, the database is available
immediately and is automatically upgraded. This prevents the database
from being used with an older version of the Database Engine
Also, not sure you care about the compatibility level, but FYSA:
If the compatibility level of a user database is 100 or higher before
upgrade, it remains the same after upgrade. If the compatibility level
is 90 before upgrade in the upgraded database, the compatibility level
is set to 100, which is the lowest supported compatibility level in
SQL Server 2017.
Additionally, I believe you question is about a user database, but if it isn't:
Backups of master, model and msdb that were created by using an
earlier version of SQL Server cannot be restored by SQL Server 2017
No, this is not possible.SQL Server 2017 backups cannot be restored by any earlier version of SQL Server ref
Also, regarding detatching and reattaching per the docs:
After being attached to SQL Server 2017, the database is available
immediately and is automatically upgraded. This prevents the database
from being used with an older version of the Database Engine
Also, not sure you care about the compatibility level, but FYSA:
If the compatibility level of a user database is 100 or higher before
upgrade, it remains the same after upgrade. If the compatibility level
is 90 before upgrade in the upgraded database, the compatibility level
is set to 100, which is the lowest supported compatibility level in
SQL Server 2017.
Additionally, I believe you question is about a user database, but if it isn't:
Backups of master, model and msdb that were created by using an
earlier version of SQL Server cannot be restored by SQL Server 2017
answered 8 hours ago
scsimonscsimon
2,3326 silver badges19 bronze badges
2,3326 silver badges19 bronze badges
add a comment
|
add a comment
|
djohnson10 is a new contributor. Be nice, and check out our Code of Conduct.
djohnson10 is a new contributor. Be nice, and check out our Code of Conduct.
djohnson10 is a new contributor. Be nice, and check out our Code of Conduct.
djohnson10 is a new contributor. Be nice, and check out our Code of Conduct.
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%2f248991%2ftemporarily-moving-a-sql-server-2016-database-to-sql-server-2017-and-then-moving%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