Microsoft Access DSN - CF9 vs. CF10
Hey everyone, I'm hoping I can get some advice from others who may have had similar struggles as me in this regard. I am running a Windows Server 2008 R2 with IIS 7.5, along with a 32-Bit CF10 installation. I have followed all instructions in setting up CF10 32-bit, and have successfully connected to a Microsoft Access data source. Everything appears to run fine.
My issue has to do with a particular report that we are creating where we have to do a lot of data mining to gather information from the Access DSN into a simplified results table for formatting into a report. It is admittedly a rather heavy process, which requires digging up recordset totals from the DSN thousands of times. I understand the disadvantages of using Access in this way, but there are other requirements on the data that have us hemmed into using Access as the backend in the near future.
Running this report on CF9 we have success. Its a slow process, but it does complete the task and doesn't interfere with the rest of the server's duties (serving CF content that is accessing different pages reading from the same DSN).
Running with CF10, (same code, same data, same server) just cannot get the job done. Often times, the server locks up and times out on the process. When this process is ran, CF response times for browsing the site is noticeably slower. The SWSOC.exe and ColdFusion.exe processes do not monopolize their processors though, if it wasn't for the slow responses navigating the site, and a CFLog that fills with server errors, just watching the server's task manager, there would be no way to recognize the process is frozen.
So, I'm wondering if anyone has any other suggestions or tricks to help me optimize the connectivity between CF10 and Access DSN's - as I feel there is something different in CF10 compared to CF9.
