Not able to migrate on-premises sql server to Azure SQL Server using Azure data migration Services

%3CLINGO-SUB%20id%3D%22lingo-sub-1407463%22%20slang%3D%22en-US%22%3ENot%20able%20to%20migrate%20on-premises%20sql%20server%20to%20Azure%20SQL%20Server%20using%20Azure%20data%20migration%20Services%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1407463%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20All!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20not%20able%20to%20connect%20to%20local%20SQL%20Server(On-premises)%20in%20Azure%20database%20migration%20service.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESteps%20that%20we%20followed%3A%3C%2FP%3E%3COL%3E%3CLI%3EFirst%2C%20we%20enable%20the%20TCP%2FIP%20protocol%20and%20set%20the%20port%20number.%3C%2FLI%3E%3CLI%3EThen%20we%20added%20that%20port%20to%20the%20inbound%20rule%20under%20Windows%20defender%20Firewall.%3C%2FLI%3E%3CLI%3EAfter%20this%20we%20restarted%20the%20SSMS%20services.%3C%2FLI%3E%3CLI%3EAfter%20this%20we%20created%20Azure%20Database%20migration%20services%20and%20during%20creation%20of%20this%20services%2C%20we%20have%20created%20new%20virtual%20network.%3C%2FLI%3E%3CLI%3EAfter%20creating%20new%20services%2C%20we%20created%20new%20project%20and%20source%20information%20is%20throwing%20error%20for%20Server%20instance%20name.%20In%20Server%20instance%20name%20I%20have%20given%20Public%20Ip%20address%20and%20aslo%20tried%20with%20port%20no.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EI%20have%20also%20attached%20error%20screenshots%20for%20your%20reference.%20Please%20let%20me%20know%20in%20case%20of%20any%20queries.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1407463%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnalysis%20Services%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EData%20Warehouse%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntegration%20Services%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1415668%22%20slang%3D%22en-US%22%3ERe%3A%20Not%20able%20to%20migrate%20on-premises%20sql%20server%20to%20Azure%20SQL%20Server%20using%20Azure%20data%20migration%20Servi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1415668%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F675213%22%20target%3D%22_blank%22%3E%40saurabh704%3C%2FA%3E%26nbsp%3Bnot%20sure%20if%20it%20is%20just%20me%20but%20I%20can't%20see%20your%20screenshots%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20check%20if%20you%20have%20a%C3%B1%20IP%20address%20that%20is%20visible%20from%20the%20outside%20and%20not%20just%20one%20of%20those%20internal%20ones%20like%20192.168....%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello All!

 

I am not able to connect to local SQL Server(On-premises) in Azure database migration service.

 

Steps that we followed:

  1. First, we enable the TCP/IP protocol and set the port number.
  2. Then we added that port to the inbound rule under Windows defender Firewall.
  3. After this we restarted the SSMS services.
  4. After this we created Azure Database migration services and during creation of this services, we have created new virtual network.
  5. After creating new services, we created new project and source information is throwing error for Server instance name. In Server instance name I have given Public Ip address and aslo tried with port no.

I have also attached error screenshots for your reference. Please let me know in case of any queries.

1 Reply

@saurabh704 not sure if it is just me but I can't see your screenshots?

 

Did you check if you have añ IP address that is visible from the outside and not just one of those internal ones like 192.168.... ?