I found myself in a position today where I had to update the JDBC drivers on our CFMX servers. You can find out more about the fixes when applying the driver and download here.

First things first, to check what version you are running add the following lines to a .cfm template and run it:

<cfscript>
jdbcDriver = CreateObject(“java”, “macromedia.jdbc.sqlserver.SQLServerDriver”);
writeoutput(jdbcDriver.getMajorVersion() & “.” & jdbcDriver.getMinorVersion());
</cfscript>
<!— just for the hell of it dump all the methods —>
<cfdump var=”#jdbcDriver#” />

This should return 3.2 (if you are running 6.1 anyway). Now back up your copy of macromedia_drivers.jar, stop your instance and copy the new macromedia_drivers.jar file over. Now if you have CFMX running as an instance of JRun (or as Macromedia call it: the J2EE configuration), you?ll need to copy the drivers over to instance cfusion\lib folder. Simply copying it into JRun\lib will only affect JRun.

{your install path}\JRun4\servers\{your instance}\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\

Then remember to restart the CFMX instance and the re-run the script and see if the version number has increased to 3.3. If not consider stopping and restarting your JRun server and all the instance associated with it.

One thing I noticed and this was purely coincidental was that if I checked the version of jdbc driver currently loaded after copying the new drivers over and not restarting the instance, the version number returned was: -1.-1!