1

Hello I am facing one issue during snapshot replication between SQl servers reside in Windows Azure Virtual Machine.

I had 2 VM with below configuration 1) Windows server 2012 (Installed sql server 2012 with msdn licence) 2) SQL server 2008 R2 (Databases reside on this server, on this i had created publisher for replication)

Now when i creating subscriber over target sql server (1st server) then while selecting publisher connection it shows me error in connecting as shown below image.

Is there any need to create virtual network? in future target server would be on premises server instead of Azure VM.

Note : For both VM i had opened 1433 port and enabled Mixed Mode Authentication.

enter image description here

Arun Rana
  • 8,426
  • 14
  • 67
  • 107
  • Faced this problem once in a non Azure environment and got it solved with this: http://stackoverflow.com/questions/8212032/sql-server-replication-requires-the-actual-server-name-to-make-a-connection-to-t maybe it helps – larrydahooster Jun 20 '13 at 13:59
  • @larrydahooster I had already looked with that before but that was not an issue. – Arun Rana Jun 20 '13 at 14:43

3 Answers3

3

Create an alias in SQL Server Configuration Manager and give it the name the replication component expects. The alias contains the cloupapp url and port. Now reconnect using the simple alias. Just did this for my cloudapp.net VM.

Roland Schoofs
  • 31
  • 1
  • 3
0

I got solution by adding alias entry in host file on VM (C:\Windows\System32\drivers\etc)

[IP Here instead of cloudapp.net URL]   [SQL server instance name]

Arun Rana
  • 8,426
  • 14
  • 67
  • 107
0

So for clarification, using the example above, the solution as I've experienced it, is to create a SQL Server alias for the server name shown in the error message. In this case, the alias name should be SQL-AZURE and the server should be the server name as shown at the top of the error message dialog:

catalysttg.cloudapp.net, port no 1433, protocol tcp/ip
Draken
  • 3,134
  • 13
  • 34
  • 54
Tony
  • 1