USQL Multi-Tier Client DSN s on Windows x64 editions

Transcription

1 USQL Multi-Tier Client DSN s on Windows x64 editions 64-Bit Windows editions permit both 32-Bit and 64-Bit ODBC applications to run on a 64-Bit platform. The type of ODBC application you run, determines which U/SQL multi-tier client you use, and what kind of data source definition (DSN s) you can use with your ODBC application. When you install the U/SQL client on a 64-Bit Windows machine, both the 32-Bit and 64-Bit U/SQL ODBC Client drivers will be installed, although in different places. Additionally, the 64-Bit U/SQL client driver requires a license be installed on the U/SQL client in order to use it. 32-Bit ODBC applications use the 32-Bit U/SQL Client driver, and access 32-bit DSN s. 64-Bit applications on the other hand, use the 64-Bit U/SQL Client driver and, can only access 64-Bit DSN s The administrative tools that are installed with the U/SQL client- the U/SQL Administrator, and U/SQL Manager, are currently all 32-bit applications and so they will only enable the administration of 32-bit DSNs. 64-bit DSNs must be defined and administrated from the Windows ODBC Manager accessed from the Control Panel. Depending upon your requirements, you may need to define the same data source DSN connections twice on the same machine, one for use with 32-bit ODBC applications, and another for use with 64-Bit ODBC applications. You must use different DSN names for each, even though they may be defined exactly the same in the U/SQL Server. By defining your DSN s twice, you can access U/SQL DSN s from both 64-Bit ODBC applications and 32-Bit ODBC applications on the same Windows machine. Installing U/SQL Multi-Tier Client on Windows x64 editions You use the U/SQL Client installation file USQLxxxCLIENT.exe to install the U/SQL Multi-Tier client. xxx indicates the release number of the U/SQL Client. You can obtain the ftp download for the multi-tier client from your U/SQL supplier. Normally, on 32-Bit Windows editions, the default installation location for the USQL Client files on Windows x32 is: C:\Program Files\USQLC For a USQL Client installation running under Windows x64 edition, this becomes: C:\Program Files (x86)\usqlc (For 32-bit programs, Windows x64 provides new default installation targets for Program Files and Common Program Files): Item Name Windows x64 Windows x32 Program Files C:\Program Files (x86) C:\Program Files Common Program Files C:\Program Files (x86)\common Files C:\Program Files\Common Files

2 Windows x64 Redirection The Windows x32 on Windows x64 (WOW64) platform provides 32-bit application services in a native 64-bit environment. To make sure that the 32-bit applications are kept separate from the 64-bit applications, WOW64 does some file and registry redirection. Filesystem Redirection Windows x64 editions use file redirection for 32-bit programs to ensure that they work correctly in the 64-bit Windows environment. The 32-Bit U/SQL Client driver, TSODBC32.dll is installed in the Windows\SysWOW64 folder. The 64-Bit U/SQL Client driver TSODBBC64.dll is installed in the Windows\SYSTEM32 folder.

3 Registry Redirection Windows x64 editions use registry redirection for 32-bit programs to ensure that they work correctly in the 64-bit Windows environment. For instance, any registry entries written by a 32-bit program to the HKEY_LOCAL_MACHINE\Software registry key will actually get redirected to the HKEY_LOCAL_MACHINE\Software\Wow6432Node registry key instead. When a 32-bit application attempts to read from HKEY_LOCAL_MACHINE\Software, it gets redirected to HKEY_LOCAL_MACHINE\Software\Wow6432Node instead. The 32-Bit U/SQL Client is registered in HKEY_Current_User\Software\Wow6432Node\Transoft and HKEY_LOCAL_MACHINE\Software\Wow6432Node\Transoft The 64-Bit U/SQL Client is installed under HKEY_LOCAL_MACHINE\Software\Transoft Windows x64 ODBC changes The Open Database Connectivity (ODBC) driver interface has been revised for Windows x64. A 64-bit version of the Microsoft Windows operating system includes the following versions of the Microsoft Open Database Connectivity (ODBC) Data Source Administrator tool (odbcad32.exe): The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\windows\syswow64 folder. The 64-bit version of the Odbcad32.exe file is located in the %systemdrive%\windows\system32 folder. (Where %WINDIR% is the folder Windows is installed in, - often C:\Windows or C:\WIN). The odbcad32.exe file displays the following types of data source names (DSNs): System DSNs User DSNs For further information regarding 32 and 64-bit versions of the ODBC Administrator please refer to following Microsoft page;

4 Defining 64-Bit U/SQL ODBC DSN s The ODBC Data Source Administrator has remained visually unchanged but, being a native 64-bit application, only defines native 64-bit ODBC Drivers. Use the 64-Bit ODBC Data Source Administrator from your system s Control Panel to define a U/SQL data source as a System DSN in order to access a U/SQL Server from a 64-Bit ODBC Application.

5

6 Note: The 64-bit and 32-bit ODBC Administrator programs are visually identical, and both show ODBC Data Source Administrator on their Window title bars. 64-Bit U/SQL Data Source Definition issues Since a File Data Source DSN name cannot be shared between 32-Bit and 64-Bit ODBC applications, you may need to configure a 64-Bit Data Source definition in your U/SQL Server, and define it exactly as you would the existing 32-Bit data source definition.

7 If you will be running both 32-bit and 64-Bit ODBC applications from a 64-Bit system, and you use a System DSN definition, then define your DSN s twice with different names, once as a 32-Bit DSN that a 32-Bit ODBC application uses, and again as a 64-Bit DSN that your 64-Bit ODBC applications will use. Defining 32-Bit U/SQL ODBC DSN s Use the 32-Bit ODBC Data Source Administrator, or the U/SQL Client Administrator to define a U/SQL data source as a System DSN in order to access a U/SQL Server from a 32-Bit ODBC Application even if you run the 32-Bit application on a 64- Bit Windows Edition.

8 32bit User Data Source issues As previously discussed, Windows x64 redirects registry reads and writes by 32-bit programs to ensure compatibility. Because WOW64 s redirection of HKEY_LOCAL_MACHINE\Software registry key, the 32-bit ODBC Administrator will only display 32-bit System Data Source names, and the 64-bit ODBC Administrator will only display 64-bit System Data Source Names. However, data sources created in the User DSN tab of the ODBC Administrator are created in the HKEY_CURRENT_User\Software key, which is shared for 64-bit and 32-bit programs. This means that any User Data Source created from either the 64-bit or 32-bit ODBC Administrator will display on both ODBC Administrator screens..

9 When you click Configure or Remove on any 32-bit User Data Source from the 64-bit ODBC Administrator, or vice versa, you will see errors, for instance: 1. Create a User Data Source from the 32-bit ODBC Data Source Administrator, 2. View the 64-bit ODBC Data Source Administrator: 3. Click Configure or Remove : The message above is only an example, - depending on what data source driver type you use, you may see a different message. For Transoft Data Source Names, it is recommended that you can use the USQL Administrator, from which you can add / remove and configure Transoft Data Sources. For all other data source types, you must use the correct ODBC Data Source Administrator to Add / Remove and Configure Data Sources, which will stop these messages from occurring. Since a File Data Source DSN name cannot be shared between 32-Bit and 64-Bit ODBC applications, you may need to configure a 64-Bit Data Source definition in your U/SQL Server, and define it exactly as you would the existing 32-Bit data source definition.

10 Testing 64-Bit U/SQL DSN Connections You can use the Microsoft OLE DB Provider for ODBC Drivers to test your 64-Bit connections to a U/SQL Server on 64-Bit Windows editions. Do not attempt to use the U/SQL Client Administrator program to test connections with a 64-Bit DSN, because the U/SQL Client Administrator is a 32-Bit Application. You can test your 64-Bit DSN connection by creating a Microsoft Data Link (.udl) file on your desktop, then use it to test the connection using the U/SQL 64-Bit Client driver. Perform the following steps: 1. Right Cick anywhere on your desktop and select New Text Document 2. Name your document any name you wish, then rename it and replace the file extension as.udl.

11 3. Right Click this newly created.udl file and select Properties On the Provider tab, select Microsoft OLE DB Provider for ODBC Drivers and push the Next button.

12 4. On the Connection Tab, use the Data Source Name selector to select the name of your 64-Bit DSN definition, then push the apply button. 5. Finally, push the Test Connection button to test the connection to the U/SQL Server.