|Subject:||Using WinSQL on a 64-bit OS|
|Creation date:||7/29/09 4:57 PM|
|Last modified on:||10/25/21 10:12 AM|
WinSQL is a 32-bit application, which can run on a 64-bit OS as well. There are two ODBC managers on a 64-bit Windows machine:
ODBC drivers are built as DLLs on Windows. A 32-bit DLL can only be
loaded by a 32-bit EXE file. Similarly, a 64-bit DLL can only be loaded
by a 64-bit application. Therefore, you can only use 32-bit ODBC
drivers with WinSQL.
Question: I don't see DSN created from ODBC Manager in WinSQL, why?
Answer: You will only see those DSN that are created using the 32-bit version of the ODBC manager.
Question: Can I convert existing 32-bit DSNs to 64-bit DSNs or visa-versa?
Answer: Theoretically speaking, you can convert the DSN entries, which are specified in the registry. However, this conversion will most likely won't work. The DSN entries are tied to the ODBC driver DLL. Since the driver for 32-bit data sources is different from 64-bit, manually changing the registry entries won't work.
Question: Will I be able to access a database running on a 64-bit machine from WinSQL?
Answer: Yes. Accessing a database running on a 64-bit machine is not a problem at all.
Question: Are there any plans to port WinSQL to a 64-bit architecture? Answer: Yes. WinSQL is written using Borland C++ compiler. As soon as a compiler is available for 64-bit, we will make it available for that platform.
Question: Are there any disadvantages of using a 32-bit application on a 64-bit machine?
Answer: Not really. The most significant advantage of running on a 64-bit OS is the use of more memory. A 32-bit process on Windows can only use up to 2 GB of memory space, where as the theoretical limits on a 64-bit Windows OS is around 128 GB
WinSQL's memory footprint hardly goes above 100 MB, which is far less than the limits on a 32-bit machine. Therefore, using WinSQL on a 64-bit machine does not change anything.
Do you have a helpful tip related to this document that you'd like to share with other users?