Created DNS and installed ODBC Drivers followed same steps from below URL
https://snowflakecommunity.force.com/s/article/how-to-set-up-a-linked-server-from-sql-server-to-snowflake
Once creating testing connection at last step it shows error like
OLE DB provider "MSDASQL" for linked server "SNOWFLAKEDATA" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)
But DNS created and used followed same way in URL. Can i know where I made mistake?
Please ensure to create the linked server to Snowflake with the following information:
Provider: This should be "Microsoft OLE DB Provider for ODBC Drivers."
Data Source: This should match the ODBC system/user DSN name that was previously configured
Under the Security Tab on left panel, make sure to add a local login (your local machine's login including your host name) associated to a remote user (snowflake username) and its matching password.
Related
I'm attempting to follow the guide here which shows how to link an azure cosmos-db as a linked server via ODBC. I have created the ODBC links to the remote cosmos-db in both x64 and x86 flavours. These appear to connect without issue when checking from within the ODBC Admin console and I can even see the data when setting up a schema, however I am unable to create a working linked server as I get the following error when testing the connection ..
"[microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
I Believe this is maybe because I have SQL Express installed and the "Providers" folder is missing from the "Linked Server" folder. I am therefore assuming that I do not have the necessary providers installed on the SQL Server Instance running locally.
I have attempted to install both the OLE DB Driver and the ODBC Driver, however these have not helped.
I am trying to connect from my SSAS server to SQL through SSMS and the connection works fine when I test it. But when I am processing the cube, I am getting the below error message.
OLE DB error: OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.
I have looked the other similar error message that was posted and tried the below options as per the suggestions.
SSAS - OLE DB error in establishing a connection
1. Restart SSAS Service
2. Restart SSAS using local system
3. Trying to change the Provider to Native OLE DB\Microsoft OLE DB Provider for SQL server, but still I am getting the below error
OLE DB error: OLE DB or ODBC error.
I am stuck with this for more than 3 days and not able to progress anything beyond. I tried all other Providers as well and still it doesn't work.
Additionally I made sure that the Windows account I am using in data source of SSAS server is having db_owner on the SQL data base.
Any help would be really appreciated to get me out of this.
I was able to get a solution for this upon trial and error method for selecting the below changes. I have tried to set the
1. Provider as "Native OLE DB/Microsoft OLE DB Provider for SQL Server"
2. Changed the connection from Windows Authentication to SQL connection.
3. The type of Impersonate Account from Windows Authentication to Authenticate by Service Account.
Once the above settings were done, I was able to process the Cube.
I am currently configuring a linked server connection between Microsoft SQL-Server and a Microsoft Access database in our network. To make things easy, I saved the Access db locally and tried to configure the linked server.
First I created a system-DSN named "BADEN32" (32 bit)
This DSN refers to my Access database (located C:\Users\xxx\Desktop\Baden.accdb)
For this DSN, I used the Microsoft Access Driver (.mdb .accdb)
When I try to create a new linked server, I keep getting the following error: Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "BADEN32"
I have already checked the MSDASQL provider if allow inprocess was true, but it was.
What am I doing wrong here?
You're linking to the SQL server from the Access Database? You would need to set up an ODBC connection to the SQL server and test it. Once it is working, go to the Access Database, External Data Tab, then ODBC Database to set up.
If this isn't what you mean, could I get more information?
This is not a question, but this post may be useful for community because I could not find the answer on the Internet.
Tested on
Windows 2008 R2 x64 and Windows 2003 x64
SQL Server 2008 SP3 x64
Provider Microsoft.ACE.OLEDB.12.0 x64
SQL Server is running under domain account that is not admin of local machine.
SQL Server connection authentication is Windows.
The issue is:
when creating and using a linked server or adhoc querying using this provider, you may receive errors like these:
OLE DB provider "MSDASQL" for linked server "xxx" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed"
OLE DB provider "MSDASQL" for linked server "xxx" returned message "[Microsoft][ODBC dBASE Driver] Your network access was interrupted. To continue, close the database, and then open it again.
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "xxx"
Could not find installable ISAM
OLE DB provider "MSDASQL" for linked server "xxx" returned message "[Microsoft][ODBC dBASE Driver]General error Unable to open registry key Temporary (volatile) Ace DSN for process 0x16f4 Thread 0x2728 DBC 0x1ce64ae8 Xbase'
The reason is that the provider creates a temporary file in SQL Server's domain account's temporary folder, using user connect's credentials. Ordinary users does not have such permissions.
The solution is
grant "Modify" permission to sql server users on Sql Server's domain account's temporary folder.
This folder ordinarily is
Windows 2003: "c:\Documents and
Settings\sql_server_account_name\Local Settings\Temp\"
Windows 2008: "C:\Users\sql_server_account_name\AppData\Local\Temp\"
Can anyone guide me around to linking a server to another in SQL Server 2008 R2? I am getting the following error when trying to do so in Management Studio.
The linked server has been created but
failed a connection test. Do you want
to keep the linked server?
ADDITIONAL INFORMATION:
An exception occurred while executing
a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The OLE DB provider "SQLNCLI" for
linked server "CDSPM1" reported an
error. Authentication failed. Cannot
initialize the data source object of
OLE DB provider "SQLNCLI" for linked
server "CDSPM1". OLE DB provider
"SQLNCLI" for linked server "CDSPM1"
returned message "Invalid
authorization specification".
(Microsoft SQL Server, Error: 7399)
Seems like Authentication problem.
Test by creating the linked Server using "Server Type" as "Sql Server". Then go into "Security" and set your user mapping. As a test, create a SQL login on the remote system and specify that on the "Be made using this security context"
Be sure that you can PING the "Linked Server" name first. HTH
Use drop down and choose
SQL Server Native Client
instead of
SQL Server
Use below link to view the screenshots of connecting the linked server with SQL Server
To solve "Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server" problem
Connect MS Access to SQL server 2008 via linked server
Then use below query to get more information about the linked server
select * from openquery("owner_pc\sqlserver2008",'select * from Testing.dbo.test')
This was driving me round the bend. And the fact you can't edit a Linked server after you entered it is just bananas.
Anyway, just leave most of the boxes empty on the linked server dialogue! Use "SQL Server Native Client" like #abatishchev mentioned then..
Check Kamran's article here for the settings. Only Datasource was filled in for me as IP hostname, after I'd give the server a friendly name in "Linked server", and on the second tab didn't need to bother with any logins just radio button the bottom one and used the SA login on the remote box.
In the general page of New Linked Server, type the sql-server instance name in the [Linked Server] box. Click on the [SQL Server] check box when selecting [Server Type]. Type remote username and password atfer selecting [Be made using this security context] of Security tab.
Select top 10 * from [LINKEDSERVERNAME].[DATABASENAME].[SCHEMANAME].[TABLENAME]
Best of luck.
for more details information http://msdn.microsoft.com/en-us/library/ff772782.aspx
A possible cause, if you have clustered service , and has recently been balanced , it is likely that a connection has been blocked pointing to old resource.
Try moving again resource to another node and reopening the Management studio, try again linked server connection.