locked
sqlpackage.exe target platform may experience compatibility issues with SQL Azure RRS feed

  • Question

  • Hi,

    I have used sqlpackage.exe to create a bacpac file from command prompt

    Below command i used for export

    .\sqlpackage.exe /a:Export /ssn:. /sdn:"sgtest" /su:myuser /sp:mypassword /tf:"D:\Scripts\6\backup2.bacpac"

    And Below command to import the bacpac to sql azure

    .\sqlpackage.exe /a:Import /tdn:"sgtest" /tp:mypassword /tsn:"hcjl0di9rw.database.windows.net" /tu:myuser /sf:"D:\Scripts\6\backup1.bacpac"

    The import successfully happens with the warning message

    "A project which specifies SQL Server 2012 as the target platform may experience compatibility issues with SQL Azure."

    What should i do in order to fix this issue

    I am using SQL Server 2012 DAC (C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\sqlpackage.exe)

    Thanks

    Sunday, February 10, 2013 4:11 PM

Answers

  • You can get all available options using sqlpackage /a:<action> /? so sqlpackage /a:publish /? will give you all publishing options

    You cannot retarget a package, all you can do is ignore the target plaform using

    /p:AllowIncompatiblePlatform=(BOOLEAN)
         Specifies whether to attempt the action despite incompatible SQL Server platforms.


    -GertD @ www.sqlproj.com

    • Marked as answer by Saravanan G Tuesday, February 12, 2013 7:20 AM
    Monday, February 11, 2013 5:15 PM
    Answerer
  • Hi Sarvanan

    If project contains entities (for example, a Sequence object) that are introduced in Microsoft SQL Server 2012, the publishing operation will fail.

    The deployment will fail if object predicates use CONTAINS or FREETEXT over a newly created full-text index and transactional scripts are used. If the option to include transactional scripts is enabled during deployment, then procedures and views are defined inside a transaction while a full-text index is defined outside of a transaction at the end of the deploy script. Because of this ordering in the script, procedures or views using CONTAINS or FREETEXT will not be resolved against the full-text index, resulting in a deployment error.

    Refrence : Change Target Platform and Publish a Database Project

    Thanks

    Saurabh Sinha

    http://saurabhsinhainblogs.blogspot.in/

     

    • Marked as answer by Saravanan G Tuesday, February 12, 2013 7:20 AM
    Sunday, February 10, 2013 5:53 PM

All replies

  • Hi Sarvanan

    If project contains entities (for example, a Sequence object) that are introduced in Microsoft SQL Server 2012, the publishing operation will fail.

    The deployment will fail if object predicates use CONTAINS or FREETEXT over a newly created full-text index and transactional scripts are used. If the option to include transactional scripts is enabled during deployment, then procedures and views are defined inside a transaction while a full-text index is defined outside of a transaction at the end of the deploy script. Because of this ordering in the script, procedures or views using CONTAINS or FREETEXT will not be resolved against the full-text index, resulting in a deployment error.

    Refrence : Change Target Platform and Publish a Database Project

    Thanks

    Saurabh Sinha

    http://saurabhsinhainblogs.blogspot.in/

     

    • Marked as answer by Saravanan G Tuesday, February 12, 2013 7:20 AM
    Sunday, February 10, 2013 5:53 PM
  • Additionally bacpac's are only supporting SQL Azure functionality.

    -GertD @ www.sqlproj.com

    Monday, February 11, 2013 1:09 AM
    Answerer
  • Thanks Saurabh,

    Will look this.

    Is there any option to change the Target platform via sqlpackage.exe commands

    Regards

    Saravanan G

    Monday, February 11, 2013 5:51 AM
  • You can get all available options using sqlpackage /a:<action> /? so sqlpackage /a:publish /? will give you all publishing options

    You cannot retarget a package, all you can do is ignore the target plaform using

    /p:AllowIncompatiblePlatform=(BOOLEAN)
         Specifies whether to attempt the action despite incompatible SQL Server platforms.


    -GertD @ www.sqlproj.com

    • Marked as answer by Saravanan G Tuesday, February 12, 2013 7:20 AM
    Monday, February 11, 2013 5:15 PM
    Answerer