Thursday, 26 May 2016

Fallback for non-installed SQL Server Native Clients

- or how to survive in a world where you are not in control of everything.

Today I did deploy a small application that did connect to a MS SQL Server, so a driver was needed, and I do prefer to follow the recommendations on using the latest native drivers - and I also try and avoid ODBC as the plague.

What had slipped my mind until the first test user got an error - was that in a plain Windows installation only the "old" ODBC SQL Server driver exists - and since I really didn't want to involve the whole IT support/operation/packaging scenario - to get the SQL Server Native Client 11.0 client pushed out to some users around the world - who also would be lacking admin rights, so that they would not be able to install the drivers themselves - I had to include a fallback option.

I refuse still to understand why the newer Windows versions keep only having the old "SQL Server" ODBC driver and not also include a "native" one, when that is what is been recommended over and over again.