(I've removed the erroneous prior version of this ...
# cfml-general
d
(I've removed the erroneous prior version of this question.) Has anyone used SQL Server 2012, 2017, or 2019 with CF 2021? Any weirdnesses? I'm not asking if they're officially supported for CF 2021, I'm looking for actual experiences. Are there any specific concerns you'd have, beyond officially stated compatibility? For reasons not worth going into here, we may want to to that in the short term.
r
We use CF 2021 with SQL Sever 2016, 2017, and 2019. We have not had any issues with any of them.
t
Same. Haven't tried with 2012 though
d
Thanks folks, keep em coming. Yes 2012 is old 🙂 Still, I've literally never run into an issue I could definitively say was due to a CF/MSSQL version incompatibility. Running these weird combinations is a short term situation only, unfortunate, but probably necessary for a bit. Yes it'd be great if we had a reasonably comprehensive set of tests we could run in that environment, but that's way out of reach for now.
@evagoras Which MSSQL version did you use with CF 2021? Why did you use the MS driver? Did you see problems that that fixed, and if so, what were they?
t
I've never found a reason to use the ms driver. It doesn't work with the cross db
generaatedkey
. You have to use the MS SQL
generated_key
instead (or an
OUTPUT
statement. I've seen people insist that you need to use the MS SQL driver to support encrypted connections, but that is false. The adobe driver handles that just fine with some custom connection string options.
e
Used it against 2012 and 2016. We have found the jdbc way to be more stable and it does everything we would normally need, so no bad side effects.