Cold Fusion 11 MIcrosoft SQL Drivers and Azure SQL
I know that folks are using the JDBC connectors (with some gymnastics) to attach ColdFusion X to Azure SQL. I had previously done this in coldFusion 9 but found that under a load, it was less than desirable (allowing timeouts and conection refusals in the connection pool).
So in coldFusion 10 I came across being able to use the Microsoft SQL driver by simply adding this line to make it use SSL:
EncryptionMethod=SSL;
(in the connection string box)
I can't find the chatter on this, but it makes more sense to me to use the built in sql driver instead of JDBC with some JAR updating and restarting.. (feels 3rd party to me!)
All was well, for over a year. These work very nicely and perfectly. Impressive, even.
So I now do the EXACT SAME on ColdFusion 11 and I get:
|
Like nothing is answering. Using Telnet to go to the server via port 1433 reveals an answer, so I know its (the azure DB) answering on port 1433 as expected. I will install management studio and verify I can actually connect as well..
What would be different between the coldFusion 10 Microsoft SQL driver and the cold fusion 11 Microsoft SQL driver that would cause this? Do I need more nuggets in my connection string? I really want to avoid the JDBC hack I see here if I can:
jdbc - ColdFusion 11 and Azure Database - Stack Overflow
Or, is JDBC better for some reason???
I'd like to sell the powers that be on upgrading our CF servers, but this is currently a deal stopper!
I updated CF to the latest, greatest (5 I think), no change.
