I've currently had a SQL Server 2008 server, which we now need to migrate to a newer edition.
We have a couple of linked servers which I have not set up personally which utilizes a provider called IBMDASQL
in SSMS
. It appears as if the previous collegue responsible for this set up has used the link here in order to set up these connections.
However, when I try to run the Setup.exe
from the installation I get an immediate error telling me that I have a Standard
edition which is not supported, and I can see from the documentation that only SQL Server 2008
is supported.
How can I set up a OLE DB Provider for IBMDASQL
(I need to get this working with a ISerie Connection)?
EDIT
I've tried to install OleDB provider for DB2
from Microsoft, and it installed successfully. It was even included in my Providers
list in Management Studio, but when I tried to set up a Connection using the same name for provider etc. as the previous Connection had, I got the error that The OLD DB provider "DB2OLEDB" for linked server abc reported an error. [....] cannot initialize data source object of OLE DB provider DB2OLEDB for linked server abc
. The same server used IBMDASQL
earlier. I thought it was "included" in the DB2 OLE DB provider
On my previous installation I had the following settings:
Provider: IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider
Product name: ISeries
Data Source: [an IP number]
Provider string:
Location:
Catalog: foo
the only difference I have in the new Connection is that
Provider: Microsoft OLE DB Provider for DB2
is used instead. Do I miss any steps?
OleDB provider for DB2
from Microsoft, and it installed successfully. It was even included in myProviders
list in Management Studio, but when I tried to set up a Connection using the same name for provider etc. as the previous Connection had, I got the error thatThe OLD DB provider "DB2OLEDB" for linked server abc reported an error. [....] cannot initialize data source object of OLE DB provider DB2OLEDB for linked server abc
. The same server usedIBMDASQL
earlier. I thought it was "included" in the DB2 OLE DB providerMicrosoft Access
in order to get this to work? I've seen some links implying that.