You've got an engineer looking to rollout a new piece of software across the entire frontend fleet of serves late Sunday afternoon. Not only that, it's to add a

You've got an engineer looking to rollout a new piece of software across the entire frontend fleet of serves late Sunday afternoon. Not only that, it's to add a new transport (network protocol) to a new database, both of which have not been through any sort of analysis to determine if they were ready or how they behaved when things went bad. All to support a production launch for the next day. That should make you squirm. It's the stuff that the company might get away with once, but once you get enough size, it will never work again. The Risk/Reward equation just doesn't match. When these things go bad they go _really_ bad _really_ fast. Think the machine is down, you can't connect to it and it stays up for a minimal amount of time after you reboot it and then you find out you don't know how to rollback and the person who does is at a football game enjoying many beers. ODBC is a client API which allows devs to write to a fixed API. Then you have a ODBC driver that connects to the database, each database has their own network transport.