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;








4















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?










share|improve this question









New contributor



djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



























    4















    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?










    share|improve this question









    New contributor



    djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      4












      4








      4








      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?










      share|improve this question









      New contributor



      djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      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






      share|improve this question









      New contributor



      djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share|improve this question









      New contributor



      djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share|improve this question




      share|improve this question








      edited 6 hours ago









      Learning_DBAdmin

      1,2453 silver badges20 bronze badges




      1,2453 silver badges20 bronze badges






      New contributor



      djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      asked 8 hours ago









      djohnson10djohnson10

      1234 bronze badges




      1234 bronze badges




      New contributor



      djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




      New contributor




      djohnson10 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.

























          1 Answer
          1






          active

          oldest

          votes


















          12
















          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







          share|improve this answer



























            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.









            draft saved

            draft discarded
















            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









            12
















            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







            share|improve this answer





























              12
















              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







              share|improve this answer



























                12














                12










                12









                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







                share|improve this answer













                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








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 8 hours ago









                scsimonscsimon

                2,3326 silver badges19 bronze badges




                2,3326 silver badges19 bronze badges
























                    djohnson10 is a new contributor. Be nice, and check out our Code of Conduct.









                    draft saved

                    draft discarded

















                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

                    Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

                    199年 目錄 大件事 到箇年出世嗰人 到箇年死嗰人 節慶、風俗習慣 導覽選單