I am trying to setup replication from SQL Server 2008 R2 (publisher and distributor) to Azure SQL database (subscriber). I configured the subscription on the SQL Server 2008 side (push) with a SQL Server User.
In the replication job I see the following error:
2018-10-15 13:53:11.381 Agent message code 20084. The process could not connect to Subscriber ''.
On the subscriber (Azure SQL DB) I see the following in the audit log:
additional_information <login_information><error_code>18456</error_code><error_state>132</error_state></login_information>
database_principal_name (is empty)
succeeded False
From this site I understand that error state 132 means AAD error. This is something I don't understand as I am using a SQL Server user.
I am able to connect to the Azure SQL DB from the publisher server using management studio and logging in with the SQL Server account.
Johan
When configuring replication between Azure SQL Database and SQL Server on-premises, SQL Server 2008 R2 is not supported as publisher or distributor as explained on this documentation.
Related
I have a question, I do not know how to solve it yet. Perhaps someone here has faced a similar issue.
We have a PostgreSQL DB hosted on Gcloud. We usually use a cloud proxy to connect with the database. It usually works very well!! In a nutshell the proxy connect a port from local host, to the actual DB host.
However this time, we want to connect it with Microsoft SSMS. We have not find an option where we can connect Microsoft SSMS with a DB running locally (this means connecting to a database on a port in local host).
The ultimate goal is to connect the database with Power BI. So if someone know how to connect a PostgreSQL DB hosted in GCloud to power BI that would also be very helpful!!
We have followed this tutorial:
https://www.anibalum.com.ar/2020/06/creating-linked-server-with-postgres.html
However we get the following error:
The linked server has been created but failed a connection test. Do you want to keep the linked server?
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "PAPERFLOWDB".
OLE DB provider "MSDASQL" for linked server "PAPERFLOWDB" returned message "[Microsoft][ODBC Driver Manager] Invalid connection string attribute".
OLE DB provider "MSDASQL" for linked server "PAPERFLOWDB" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)
We are using Microsoft SSMS v18.9.1
My application server (say 192.168.100.1) and database server (say 192.168.100.2) both are on the same domain. I'm trying to create an ODBC connection from the application server to a SQL Server database on the database server, but at the time of login it generates this error:
Microsoft SQL Server Login
Connection failed:
SQL State: 'HYT00'
SQL Sever Error: 0
[Microsoft][ODBC SQL Server Driver]Login timeout expired
I've checked all configuration for SQL Server and tried possible solutions without resolving this issue.
Important:
A DSN can be successfully created from my own PC but when attempting this server to server as described above, ODBC is facing this problem.
OK, I have got the solution. Sometimes, if SQL Server can't be found on network by its name while creating DSN in windows, the logging in takes time more than usual which tells ODBC manager that Database Server we are looking for is not responding or responding too late.
Solution.
Instead of selecting server from the list while making dsn, use 'server-ip\SQLExpress'.
e.g 192.168.100.2\SQLExpress.
Thats All.
I am having an issue while connecting to SQL Server 2012 Express edition running on my PC using Oracle SQL Developer v4.1. I downloaded JDBC 3rd-party database driver. I have the TCP/IP enabled and am using port 1433. My SQL Server browser is also enabled. I am getting this error message:
Status : Failure -The syntax of the connection URL 'jdbc:jtds:sqlserver://my-pc\SQL2012:port:1433/dbname;instance=SQL2012' is invalid.
I have installed the SQL server 2008 R2 on windows 7, when i want to connect database engine it give the following error message
TITLE: Connect to Server
Cannot connect to (local).
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
I tried both window and SQL Server authentication but no success.
please help.
First Check whether any SQL Server Instance is running and exists.
You can check list of instances as per below:
Go to command prompt and type in “osql -L” or “sqlcmd -L”.
If instance is showing in list then check your credentials.
Start the sqlserver service. Nothing to do in stackoverflow. Move question to serverfault.
I am using SQL SERVER MANAGEMENT STUDIO 2008 R2. I have used my pc's name(For example, MY-PC) as a server name to make databases. Now how can I get the database I created in my pc's named server, when I select .\sqlexpress as a server.
The error it shows when I tried to restore in .\sqlexpress from .bak file:
Restore failed for Server 'MY-PC\SQLEXPRESS'. (Microsoft.SqlServer.SmoExtended)
Additional Information:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.2531. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.Smo)
You can't restore the database in the above scenario - as per the error, the backup was taken on a SQL Server 2008R2 instance, and you are trying to restore it on a SQL Server 2008 instance - backup files are not backwards compatible.
You can see this from the error message:
10.50.1600 is SQL Server 2008 R2 RTM
10.00.2531 is SQL Server 2008 Service Pack 1
See the following Microsoft article for details on SQL Server version numbers:
http://support.microsoft.com/kb/321185