June 7, 2009 at 5:41 pm
Hi All,
I'm trying to install 32-bit SQL Server Standard on 64-bit Vista Ultimate, I need to do this because I want access to the 32-bit ODBC drivers and I understand from reading numerous posts that this can be done. However, going through the setup routines there seems to be no option for selecting which os platforms should be targeted. Am I missing something? Can anyone advise of the appropriate steps to get this installation done? Also, assuming I can get it installed, are there any special steps needed to get Microsoft.ACE.OLEDB.12.0 installed for use int eh 32 bit SQL instance.
Ta.
June 7, 2009 at 7:30 pm
Ok, I figured this out myself. On the first page of the SQL Server 2008 setup routine there is an Options option which allows setting the architecture, once this is set to x86 it will install SQL in the wow environment. I also believe there was an issue with the initial SQL Server 2008 distributable packages int hat there was some issue with them missing some required folders, this has been resolved with later releases, certainly the current sql server 2008 standard x86,x64 download seems to be installing fine.
June 7, 2009 at 8:04 pm
I am just seeing your post but the SQL Server 2008 binaries are AnyCPU that is it can install as both x86 and x64 and you don't need to install x86 to use x86 ODBC drivers because both are in all x64 operating systems. And you should be able to access your ACE driver through the x86 ODBC. Now dependning on your needs you may need to manually reference MDAC in code because Vista and Win2008 comes with new data access.
Kind regards,
Gift Peddie
June 7, 2009 at 10:36 pm
Hi there,
Thanks for you reply, however I'm pretty sure the ACE drivers are only 32 bit and won't load into a 64 bit installation of SQL. To access say a CSV file or an excel spreadsheet using OPENROWSET I use the Microsoft.ACE.OLEDB.12.0 driver and this will anly load into a 32 bit installation. So I'm setting up a 32 bit instance to do all the extranal data reading and a linked server from my 64bit to the 32bit to make this available to my application. I don't use SSIS as data importing and scheduling etc. is handled by my app. Having said all that I'm more than happy to be proven wrong as I for one, can;t believe Microsoft have not released a 64 bit version of ACE.
June 8, 2009 at 7:56 am
I am just seeing your post but the SQL Server 2008 binaries are AnyCPU that is it can install as both x86 and x64 and you don't need to install x86 to use x86 ODBC drivers because both are in all x64 operating systems. And you should be able to access your ACE driver through the x86 ODBC.
I did not say there are x64 ACE drivers I rather said you can use the x86 ODBC driver in the WOW64 directory of your x64 Vista to load on the x86 directory of your x64 SQL Server 2008. That is the application must build x86, you only get issues when you try to load it as x64 or AnyCPU if you are in managed code. So I am trying to save you the extra hop to the x86 SQL Server because everything x64 in the Microsoft platform also loads the x86 version of that dll.
Kind regards,
Gift Peddie
June 8, 2009 at 4:00 pm
Sorry, I must be having a bit of a thick moment.
Are you saying that the ACE drivers can be used in an openrowset query in a x64 installation of SQL. If this is the case do you have some instructions on how to do this please? Everything I've read on the web seems to indicate that this is not possible and I have some clients that would be very pleased to see this functionality without having to have an additional x86 instance of SQL.
June 8, 2009 at 4:31 pm
The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\SysWoW64 folder.
Look for the above folder in the WOW64 directory to configure your connection to the ACE OLE DB driver for Access 2007 and you should also look for the x86 SQL Server directory the only requirement your application must build x86. That includes SSIS packages because when you are using x86 with x64 you build lower.
Kind regards,
Gift Peddie
June 9, 2009 at 2:53 am
If you have a 64-bit installation of SQL Server 2008 available, it is definitely worth trying to connect to it with your 32-bit application. There are very few issues with using 32-bit applications connecting to 64-bit SQL Server 2008.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
June 9, 2009 at 3:25 am
My application has no problems connecting and using 64 SQL Server apart from the inability to use ACE drivers. My application created views which use OPENROWSET to access external data. These OPENROWSET vqueries use the ACE drivers which don't work in this environment because (I guess) the views are running under the 64 bit SQL Server instance. Sure, my application (the actual executable) could open connections directly on the external data source using ACE but thats not the way it works. It uses SQL views with OPENROWSET, it is this situation that requires a separate 32 bit instance of SQL, the 32 bit instance holds the views which because the instance is 32 bit can reference and use the 32 bit ACE drivers. The 64 bit instance uses a linked server to ref0erence the data in the external files via the OPENROWSET views on the 32 bit instance.
June 9, 2009 at 3:47 am
Can I suggest you open a case for this with Microsoft. There should be a better solution than installing a 32-bit version of SQL Server 2008 on a 64-bit box.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
June 9, 2009 at 5:37 am
Yes, one would think there should be a better solution however, Microsoft have not released 64-bit versions of ACE and their suggestion is to use SSIS when accessing external data. Which is not appropirate for my app, in the mean time the 32-bit / 64-bit solution... while clunky works fine.
June 10, 2009 at 7:13 am
I just had a case open with them on this issue and their solution was to install a 32 bit instance of SQL and via linked server call a proc to run the openrowset.
I guess I should know better, but I was shocked M.S. pulled this one.
After I questioned the suport staff a bit they researched and said that their would be 64 bit text/excel drivers at some point. The next version of Office is supposed to come in both 32 and 64 bit flavors, so I guess we should get 64 bit drivers as it approaches or at least when it is released.
FisherDad
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply