I develop a VB.Net application who use OLE DB Provider for DB2 to get and send data from/to distance DB2 database.
Do I have install SQL Server 2012 or 2008 R2 and OLE DB Provider for DB2 for each client machine for an executable application VB.Net. Is there any solution to avoid SQL Server 2008R2 or 2012 installation when I install the provider?
If not what is the necessary feature of SQL Server 2012 or 2008R2 to install and use DB2 V 4.0 version 9.0.1356.0?
Why not use the OLEDB provider from IBM?
You don't say what platform and version of DB2, that will make a difference in where you find the appropriate driver from IBM.
Related
I have a similar problem. I am trying to migrate an Access database to a SQL Server 2012 with the SQL Server Migration Assistant for Access (SSMA) v8.24. So I began by creating a project a carefully specifying a migration to a SQL Server 2012. But when i try to conect to SQL Server, I get the following error :
You cannot connect to an older version (SQL Server 2008) of target SQL Server from a higher version SSMA project (Project type = SQL Server 2012). Try creating another SSMA project of project type which matches the version of target SQL Server you are connecting to OR connect to a target SQL Server equal to SQL Server 2012.
I don't understand what is wrong since the version of the SQL server is supposed to be the same as the version specified for the migration project.
If I am run OLAP application in SQL installed machine (Machine A), it will work perfectly. But I need to run that application in another machine (Machine B) with Machine A's MSOLAP DLL.
Is it possible?
If yes how can I do that?
Update
I have fixed this issue by using Adomd connection instead of OleDb connection... :)
"MSOLAP.4" is the name of the OLE DB provider for Analysis Services as included with SQL Server 2008. This driver is included with the Feature Pack for SQL Server. The SQL Server 2008 Feature Pack is here. Expand the "Install instructions" header and download the correct "Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider" for your platform.
Since, typically, the latest versions can connect without problems to older versions, and SQL Server 2008 is no longer supported, I recommend installing the version from the SQL Server 2014 Feature Pack instead. Use "MSOLAP" as the provider name in the connection string to use the latest version rather than a specific one.
I have a legacy business application built on MS SQL Server 2000. I have some webbased utilities that access this database using PHP 5.2 with mssql extension.
I need to reinstall the web server, and I looked forward to upgrade to PHP 5.4. Unfortunately, the mssql extension is not supported on PHP 5.3 and newer. There is the sqlsrv extension available form Microsoft, but the description says that it is only supported for accessing SQL server 2005 and up.
How can I connect to my SQL Server 2000 from PHP 5.4 ? Did anyone already solve this issue ?
This is a really complicated issue. Here are the details of (in)compatibilities so someone else might spend less time searching and trying.
PHP extension sqlsrv from Microsoft
sqlsrv exists in two (+ an unofficial) versions, they are only compatible with 32-bit PHP. There is currently no version for 64-bit PHP.
sqlsrv version 2.0 is compatible with PHP 5.2.4 to 5.3.x and SQL Native client 2008 R2 to connect to Microsoft SQL Server 2000, 2005, or 2008.
sqlsrv version 3.0 is compatible with PHP 5.3.0 to 5.4.x and SQL Native client 2012 to connect to Microsoft SQL Server 2005, 2008, 2008 R2, and SQL Server 2012.
no official version currently supports PHP 5.5
There is an unofficial version of SQLSRV 3.0 on Rob's Area that does not require SQL Native client 2012 but should run with previous SQL Native clients. I didn't yet try this one.
ODBC extension of PHP
An other way to access SQL Server 2000 with PHP 5.4 is through the odbc extension. It is possible to connect using three ODBC drivers for SQL Server 2000:
SQL Server ODBC client version 6.00 that comes preinstalled with Windows 2008 R2
SQL Server Native Client 9.0 (SQL Server 2005 feature pack)
SQL Server Native Client 10.0 (SQL Server 2008 R2 feature pack)
The code for the connection for each of those ODBC Drivers:
$connection_string = 'DRIVER={SQL Server};SERVER=mbsql;DATABASE=vg1';
$connection_string = 'DRIVER={SQL Native Client};SERVER=mbsql;DATABASE=vg1';
$connection_string = 'DRIVER={SQL Server Native Client 10.0};SERVER=mbsql;DATABASE=vg1';
$connection = odbc_connect( $connection_string, $user, $pass );
These connections work with PHP 32 bit and 64 bit. I din't yet test which one is the best.
Am trying to connect SQL Server Analysis Services from PowerPivot for Excel. This was working fine and if I use existing connections it works fine. But when I try to create a new connection throw an error as below:
Failed to connect to the Server. Reason 'MSOLAP' provider is not registered on the local machine.
Version of SQL Sever am using is 2012.
Any clues?
Looks like you are missing "Microsoft® Analysis Services OLE DB Provider for Microsoft® SQL Server®"
You should be able to find the component if you search for "Microsoft® SQL Server® Feature Pack" (SQL 2012 version (MSOLAP.5) here) - you then need to expand the "Install Instructions" section to find the "Microsoft® Analysis Services OLE DB Provider for Microsoft® SQL Server®" section.
(For reference, MSOLAP.4 is in the SQL Server 2008 R2 feature pack)
We have a Windows 2008 server with SQL Server 2005 SP3 with a bunch of classic ASP sites that are using SQLOLEDB to connect.
We have a new application that requires SQL Server Native Client 2008 R2 installed because it is using the SQLSRV PHP Driver. SQL Server Native Client 2005 is already installed (as part of SQL Server install).
Are there any issues with installing SQL Server Native Client 2008 R2 and connecting using SQLOLEDB? I'm assuming that 2008 client is backward compatible with the 2005 client?
Can the 2008 client be uninstalled back to 2005 if we need to roll-back?
I'm concerned that installing this could cause issues for the sites already using OLEDB.
Any help or insight is greatly appreciated.
Thanks
Dave
You can install them side by side no problem.
Are there any issues with installing SQL Native Client 2008 R2 and
connecting using SQLOLEDB?
No (apart from the lower functionality set of SQLOLEDB)
I'm assuming that 2008 client is backward compatible with the 2005
client?
Yes.
Can the 2008 client be uninstalled back to 2005 if we need to
roll-back
Yes