Executing EF Code First migration script on remote database












0















I'm using EF Code First migrations when developing software on Visual Studio 2017. The development work and database migrations are performed on the local database.



When it is time to deploy the new database version to the production environment, I don't have direct access to the production database from the Visual Studio environment.



Is it technically correct to use the following procedure for updating remote production databases (that support EF Code First migrations):



1) generate schema-only db script from PRODUCTION db, say "prod_v1.sql"



2) create new database called "PROD_V1" on LOCAL db, using "prod_v1.sql"



3) on LOCAL machine, use "update-database -script" against PROD_V1 to generate the migration script "migrate_v1_to_v2.sql"



4) on PRODUCTION machine, use SQL Server Management Studio and execute the migration script "migrate_v1_to_v2.sql" in the query window.



The only thing that makes me wonder if this works is the "INSERT INTO __MigrationHistory" statement in the migration script. Is the migration script "portable", i.e. is it OK to run it against any database instance that already has the migration history enabled?










share|improve this question



























    0















    I'm using EF Code First migrations when developing software on Visual Studio 2017. The development work and database migrations are performed on the local database.



    When it is time to deploy the new database version to the production environment, I don't have direct access to the production database from the Visual Studio environment.



    Is it technically correct to use the following procedure for updating remote production databases (that support EF Code First migrations):



    1) generate schema-only db script from PRODUCTION db, say "prod_v1.sql"



    2) create new database called "PROD_V1" on LOCAL db, using "prod_v1.sql"



    3) on LOCAL machine, use "update-database -script" against PROD_V1 to generate the migration script "migrate_v1_to_v2.sql"



    4) on PRODUCTION machine, use SQL Server Management Studio and execute the migration script "migrate_v1_to_v2.sql" in the query window.



    The only thing that makes me wonder if this works is the "INSERT INTO __MigrationHistory" statement in the migration script. Is the migration script "portable", i.e. is it OK to run it against any database instance that already has the migration history enabled?










    share|improve this question

























      0












      0








      0








      I'm using EF Code First migrations when developing software on Visual Studio 2017. The development work and database migrations are performed on the local database.



      When it is time to deploy the new database version to the production environment, I don't have direct access to the production database from the Visual Studio environment.



      Is it technically correct to use the following procedure for updating remote production databases (that support EF Code First migrations):



      1) generate schema-only db script from PRODUCTION db, say "prod_v1.sql"



      2) create new database called "PROD_V1" on LOCAL db, using "prod_v1.sql"



      3) on LOCAL machine, use "update-database -script" against PROD_V1 to generate the migration script "migrate_v1_to_v2.sql"



      4) on PRODUCTION machine, use SQL Server Management Studio and execute the migration script "migrate_v1_to_v2.sql" in the query window.



      The only thing that makes me wonder if this works is the "INSERT INTO __MigrationHistory" statement in the migration script. Is the migration script "portable", i.e. is it OK to run it against any database instance that already has the migration history enabled?










      share|improve this question














      I'm using EF Code First migrations when developing software on Visual Studio 2017. The development work and database migrations are performed on the local database.



      When it is time to deploy the new database version to the production environment, I don't have direct access to the production database from the Visual Studio environment.



      Is it technically correct to use the following procedure for updating remote production databases (that support EF Code First migrations):



      1) generate schema-only db script from PRODUCTION db, say "prod_v1.sql"



      2) create new database called "PROD_V1" on LOCAL db, using "prod_v1.sql"



      3) on LOCAL machine, use "update-database -script" against PROD_V1 to generate the migration script "migrate_v1_to_v2.sql"



      4) on PRODUCTION machine, use SQL Server Management Studio and execute the migration script "migrate_v1_to_v2.sql" in the query window.



      The only thing that makes me wonder if this works is the "INSERT INTO __MigrationHistory" statement in the migration script. Is the migration script "portable", i.e. is it OK to run it against any database instance that already has the migration history enabled?







      sql-server entity-framework ef-code-first ef-migrations






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 15 '18 at 14:57









      user2025829user2025829

      11




      11
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322183%2fexecuting-ef-code-first-migration-script-on-remote-database%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f53322183%2fexecuting-ef-code-first-migration-script-on-remote-database%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

          Xamarin.iOS Cant Deploy on Iphone

          Glorious Revolution

          Dulmage-Mendelsohn matrix decomposition in Python