locked
SQL Server to Azure Migration Tool RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi, we are trying to use the Data Migration assistant to migrate our on prem SQL Server Database to Azure SQL Database.  However when we try and connect to the on prem server, it's failing because the SQL Server instance is running on port 4657 and not the default 1433.  Is there any way we can specify or change the port number somehow in the migration tool or the Azure Migration portal?  Many thanks.
    Friday, July 17, 2020 10:11 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    I managed to stumble across the solution myself in case anyone else has the same issue:

    Server name: server_example.com\SQL6,{portnumber}

    • Proposed as answer by Naomi N Friday, July 17, 2020 1:50 PM
    Friday, July 17, 2020 11:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    In the Data Migration Assistant, select the New (+) icon, and then select the Assessment project type.

    Specify a project name, in the Source server type text box, select SQL Server, in the Target server type text box, select Azure SQL Database, and then select Create to create the project.

    When you're assessing the source SQL Server database migrating to a single database or pooled database in Azure SQL Database, you can choose one or both of the following assessment report types:

    Check database compatibility
    Check feature parity
    Both report types are selected by default.

    In the Data Migration Assistant, on the Options screen, select Next.

    On the Select sources screen, in the Connect to a server dialog box, provide the connection details to your SQL Server, and then select Connect.

    In the Add sources dialog box, select AdventureWorks2012, select Add, and then select Start Assessment.
    • Edited by Max-44 Friday, July 17, 2020 2:33 PM
    Friday, July 17, 2020 1:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi icePhalanx,

    I am glad to hear that you have solved your problem. In order to close this thread, please kindly mark your solution as answer. By doing so, it will benefit all community members who are having this similar issue.  Your contribution is highly appreciated.

    Best Regards,
    Cris

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, July 20, 2020 5:39 AM