locked
MSSQLMS 2014 Deploy Database to Windows Azure Database: Various sign on configuration errors RRS feed

  • Question

  • When conducting  Deploy Database to Windows Azure Database for the first time, it works fine with a simple database.

    But when deploying with a slightly more complex database then receive the following errors.

    I have searched around and thought it more direct if I asked in the forum.

    The quotes below capture the error.

    "TITLE: Microsoft SQL Server Management Studio

    ------------------------------

    One or more unsupported elements were found in the schema used as part of a data package.

    Error SQL71564: The element User: [NT Service\MSSQLSERVER] has property AuthenticationType set to a value that is not supported in Microsoft Azure SQL Database v12.

    Error SQL71564: The element User: [NT SERVICE\SQLSERVERAGENT] has property AuthenticationType set to a value that is not supported in Microsoft Azure SQL Database v12.

    Error SQL71564: The element User: [NT AUTHORITY\NETWORK SERVICE] has property AuthenticationType set to a value that is not supported in Microsoft Azure SQL Database v12.

    Error SQL71564: The element User: [AHDB\AHDB-PB037BWW$] has property AuthenticationType set to a value that is not supported in Microsoft Azure SQL Database v12.

    Error SQL71564: The element Login: [NT Service\MSSQLSERVER] has property IsMappedToWindowsLogin set to a value that is not supported in Microsoft Azure SQL Database v12.

    Error SQL71564: The element Login: [NT SERVICE\SQLSERVERAGENT] has property IsMappedToWindowsLogin set to a value that is not supported in Microsoft Azure SQL Database v12.

     (Microsoft.SqlServer.Dac)

    "

    Always on the look out for simplicity. If only complexity didn't hide simplicity.

    • Changed type pituachMVP Saturday, November 7, 2015 3:16 PM it is a question
    Saturday, November 7, 2015 12:45 PM

Answers

  • Those database users can't be migrated to Azure SQL DB because they are Windows users. You'll need to drop those users before you deploy this database to Azure SQL DB.

    You can always backup and restore a copy of this database, remove the users, and then deploy that one to Azure SQL Db.

    David


    David http://blogs.msdn.com/b/dbrowne/

    • Proposed as answer by pituachMVP Saturday, November 7, 2015 3:18 PM
    • Marked as answer by Stewa11 Monday, November 9, 2015 9:49 AM
    Saturday, November 7, 2015 2:27 PM
  • Is your Azure SQL Database Server on V12?  If not, go to portal.windowsazure.com and upgrade it.

    David


    David http://blogs.msdn.com/b/dbrowne/

    • Marked as answer by Stewa11 Monday, November 9, 2015 9:49 AM
    Sunday, November 8, 2015 4:29 PM

All replies

  • Those database users can't be migrated to Azure SQL DB because they are Windows users. You'll need to drop those users before you deploy this database to Azure SQL DB.

    You can always backup and restore a copy of this database, remove the users, and then deploy that one to Azure SQL Db.

    David


    David http://blogs.msdn.com/b/dbrowne/

    • Proposed as answer by pituachMVP Saturday, November 7, 2015 3:18 PM
    • Marked as answer by Stewa11 Monday, November 9, 2015 9:49 AM
    Saturday, November 7, 2015 2:27 PM
  • That worked then this error popped up:

    (Please help me to create a thread that will help others)

    TITLE: Microsoft SQL Server Management Studio
    ------------------------------

    An error occurred during deployment plan generation. Deployment cannot continue. (Microsoft.SqlServer.Dac)

    ------------------------------
    ADDITIONAL INFORMATION:

    A project which specifies Microsoft Azure SQL Database v12 as the target platform cannot be published to Microsoft Azure SQL Database. (Microsoft.Data.Tools.Schema.Sql)

    ------------------------------
    BUTTONS:

    OK
    ------------------------------


    Always on the look out for simplicity. If only complexity didn't hide simplicity.

    Sunday, November 8, 2015 11:05 AM
  • Is your Azure SQL Database Server on V12?  If not, go to portal.windowsazure.com and upgrade it.

    David


    David http://blogs.msdn.com/b/dbrowne/

    • Marked as answer by Stewa11 Monday, November 9, 2015 9:49 AM
    Sunday, November 8, 2015 4:29 PM