Fazer uma PerguntaFazer uma Pergunta
 

RespondidoImport Database Objects and Settings not enabled

  • terça-feira, 30 de junho de 2009 13:52Luis Esteban Valencia Muñoz Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    After I imported a database this option is not enabled, I guess that I should import the latest version database and in the project properties, I select the version the Client has, in that way when I deploy it will generated the SCRIPT with the differences only, right?


    MCPD ENTERPRISE APPLICATIONS DEVELOPER http://wantmvp.blogspot.com/

Respostas

  • terça-feira, 30 de junho de 2009 15:53JoyceWang_MSFTMSFTMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     Respondido

    Luis,

    We only allow to import a live database into an empty database project, so this option won't be enabled if you've imported once, or you have existing schema objects in the project. 

    When you deploy, you have to specify the target server and database (connection) in the project properties. Depending on the status of your project and the target database, the deployment engine compares these two, and generates the diff script for you.  If the target database does not exist on the server at the time of your deployment, the deployment engine will generate the script to create the database. There are also numerous options you can set in the project properties that could affect the actual deployment scripts.

    Let us know if you have another other question.

    -- Joyce 

Todas as Respostas

  • terça-feira, 30 de junho de 2009 15:53JoyceWang_MSFTMSFTMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     Respondido

    Luis,

    We only allow to import a live database into an empty database project, so this option won't be enabled if you've imported once, or you have existing schema objects in the project. 

    When you deploy, you have to specify the target server and database (connection) in the project properties. Depending on the status of your project and the target database, the deployment engine compares these two, and generates the diff script for you.  If the target database does not exist on the server at the time of your deployment, the deployment engine will generate the script to create the database. There are also numerous options you can set in the project properties that could affect the actual deployment scripts.

    Let us know if you have another other question.

    -- Joyce 

  • terça-feira, 30 de junho de 2009 16:09Luis Esteban Valencia Muñoz Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    what about if there are new objects I need to import to the project, what should I do? so far, today in the morning I have had to create 5 different databse projects cause I havent find how to

    thx
    MCPD ENTERPRISE APPLICATIONS DEVELOPER http://wantmvp.blogspot.com/
  • terça-feira, 30 de junho de 2009 16:19JoyceWang_MSFTMSFTMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    Yes, you can do it by importing into a new database project. Or, you can script out your new objects from SQL Server side, and use Import Scripts... although this is not a recommended way.  I assume you are still trying to establish your baseline project.

    Ideally once you get your baseline project ready, you will do all your database development on the project side, and deploy your changes back to the server, not the other way around. 
  • terça-feira, 30 de junho de 2009 16:21Luis Esteban Valencia Muñoz Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    Got It.  Thats a very good idea we were using sql management studio to alter procedures, etc

    Thanks

    MCPD ENTERPRISE APPLICATIONS DEVELOPER http://wantmvp.blogspot.com/