- MICROSOFT ODBC DRIVER 11 FOR SQL SERVER 64 BIT 64 BIT
- MICROSOFT ODBC DRIVER 11 FOR SQL SERVER 64 BIT DRIVERS
- MICROSOFT ODBC DRIVER 11 FOR SQL SERVER 64 BIT WINDOWS
To work around this problem, use the appropriate version of the ODBC Administrator tool. To maintain backward compatibility, no resolution for this problem is currently available. Therefore, user DSNs are visible in both the 32-bit and 64-bit versions of the ODBC Administrator tool. Registry redirection is not enabled for this registry subkey. The user DSNs are stored under the following registry subkey: However, if you make a connection through this 32-bit user DSN, you receive the error message that is mentioned earlier in this section. The SQLDataSources function that is called in a 64-bit application returns this 32-bit user DSN. This driver does not have a corresponding 64-bit version. You create a user DSN for the 32-bit driver 'Microsoft Access Driver (*.mdb)'. Therefore, if the application makes a connection by using a user DSN that is returned from the SQLDataSources function, you may receive the following error message:ĭata source name not found and no default driver specifiedįor example, consider the following scenario.
MICROSOFT ODBC DRIVER 11 FOR SQL SERVER 64 BIT DRIVERS
Similarly, the SQLDataSources function that is called in a 64-bit application returns only system DSNs for 64-bit drivers but returns user DSNs for both 32-bit drivers and 64-bit drivers. The SQLDataSources function that is called in a 32-bit application returns only system DSNs for 32-bit drivers but returns user DSNs for both 32-bit drivers and 64-bit drivers. The SQLDataSources function returns all versions of user DSNs, regardless of the architecture of the application. The 64-bit version of the ODBC Administrator tool displays 64-bit system DSNs, 32-bit user DSNs, and 64-bit user DSNs. The 32-bit version of the ODBC Administrator tool displays 32-bit system DSNs, 32-bit user DSNs, and 64-bit user DSNs. The Odbcad32.exe file displays the following types of data source names (DSNs):
MICROSOFT ODBC DRIVER 11 FOR SQL SERVER 64 BIT WINDOWS
Original product version: SQL Server Original KB number: 942976 SymptomsĪ 64-bit version of the Microsoft Windows operating system includes the following versions of the ODBC Data Source Administrator tool (Odbcad32.exe):
MICROSOFT ODBC DRIVER 11 FOR SQL SERVER 64 BIT 64 BIT
Run64BitRuntime to true which select the 64 bit version of driver at run time due to both 32 bit and 64 bit version have the same id.This article provides workaround for the problem that occurs in the ODBC Data Source Administrator tool. So in brief you have to select the 32 bit driver at run time and set the Information about properties you can set on Integration Services projects, see Integration Services Considerations on 64-bit Computers and Integration Services in Business Intelligence Development Studio. If the Run64BitRuntime property is set to true, the runtime finds and uses the 64-bit provider if Run64BitRuntime is false, the runtime finds and uses the 32-bit provider. Run64BitRuntime property of the Integration Services project. To specify whether the Integration Services runtime uses an available 64-bit version of the provider, you set the
The 64-bit version of the provider can be run even if the package is run in Business Intelligence Development Studio.īoth versions of the provider have the same ID. However, some commonly used objects in SSIS don't have 64-bit counterparts, and will therefore cause your packages to fail.Īt run time, the correct version is used, and it does not matter that you specified the 32-bit version of the provider at design time. Of 32-bit or 64-bit operation - but the default on a 64-bit installation is to use 64-bit mode (obviously). When you're designing your package, you're using 32-bit facilities - and have no choice in the BIDS, matter When you execute your package using DTExec, you have the option
Business Intelligence Design Studio (BIDS) is a 32-bit application.
0 kommentar(er)
