March 29, 2016 at 5:41 am
Hi there
I have updated our server to 2012 SP3, which should include the ability to replicate to Azure?
I have tried setting up a push subscriber (transactional replication), but when I add the sql server name "oursqlserver.databases.windows.net", I get an error:
Sql Server replication requires the actual server name to make a connection to the server
I can connect directly to the instance in SSMS using exactly the same credentials?
I am following the instructions as is from this article: https://channel9.msdn.com/Shows/Data-Exposed/Azure-SQL-DB-Transactional-Replication
I have setup the replication to other on-premise servers, so I know it "should" work
Any ideas and is this even available with SQL Server 2012 SP3?
Thank you very much.
Kind Regards
March 29, 2016 at 8:48 am
I have not done this, but according to this web site[/url], you may not be on the right cumulative update. Make sure you've got that set, then try again.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 30, 2016 at 12:30 am
I have installed the CU2 for SP3 released 2nd of March 2016 and it still doesn't work.
Surely the latest SP3 will have the same features as SP2 CU8?
March 30, 2016 at 3:44 am
Hmmm.... yeah, you'd think. As I say, I haven't tried setting that up, so I don't have a good suggestion. What is the error message that you get? Be sure that the ip address for the distribution server has access through the Azure firewall.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 30, 2016 at 4:03 am
Hi Grant
I get the following: sql server replication requires the actual server name to make a connection to the server
So what I did was to create an alias in the Network Configuration of SQL, this allowed me to connect to the server using AzureServer as the host, but now it doesn't accept the username: sqladmin@azure-db it gives the same erorr for the "@azure-db" part of the username.
If try to connect with the @azure-db it doesn't seem to pick up the account while using AzureServer as host. Strangely enough I can connect with AzureServer and sqladmin@azure-db via the normal SSMS DB engine connection.
I have given up to be honest and busy writing some custom ETL using SSIS.
March 30, 2016 at 4:14 am
Reading through "all" the documentation, the suggestion is that the URL should just work. I guess the question would be is the distribution server up to the same service pack as all the other servers? If so, I'm flummoxed.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 30, 2016 at 4:31 am
that is what is baffling me as well.
I am using the same server as Distributor for now, all up to date, but for some reason it is refusing to accept the URL as the host name.
Only thing I can think of is that it was either not included for 2012 SP3 or it is a bug?
March 30, 2016 at 5:59 am
Right there with you. If it's not acknowledging the URL as a name, it's likely an error.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply