On Wednesday, December 4, 2002 at 5:01:42 AM UTC+11, Ted G Williams wrote:
You can create a linked server with ODBC, but it's pretty hideously
slow. Queries do not use any of the indexes. So get ready for table-scan-ville. If you are searching for a single match, you can
use the TOP clause to cut down the query time, but that doesn't always
help.
Following is some sample code you can use in Query Analyzer to create
an ODBC linked server to Pervasive.
EXEC sp_addlinkedserver
@server = 'SAMPLE',
@provider = 'MSDASQL',
@srvproduct='Pervasive ODBC Client Interface',
@datasrc = 'MyDSN'
--@Server is the name of the new linked server
--@datasrc is the name of a local ODBC DSN
exec sp_tables_ex 'SAMPLE'
--The above will list all of the table available
select * from [SAMPLE].[MyDatabase]..[MyTable]
--First, the name of the linked server
--Second, the Pervasive database name, not the ODBC DSN
--Third, Nothing
--Fourth, the table name.
I got this error:
OLE DB provider "MSDASQL" for linked server "PERVASIVESERVER" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "PERVASIVESERVER".
I use "timberline data" driver (32-bit) in System DSN setting
My SQL Server is 2014
Any idea how to fix this issue?
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)