Drop support for DBServer

[cavagnaro]

Hi guys
Wondering what do you think on the fact that now in eServices IXN (so far have seen it there) there is no more support for DBServer and must go with ODBC?



"Support for DB Server is dropped and existing environments must migrate to using ODBC connections."

[catanirex]

Personally I see no problem.
We ran IxnSrv 8.5 without DBServer as soon as it was supported. Good to have less applications. Also ODBC is needed in order to get UTF-8 support on Oracle at least.

Have now upgrade to IxnSrv 9 and latest MS-SQL server driver and installation was easy. (Not using DSN - specifying driver name on DAP directly)

[cavagnaro]

Good point on the UTF-8
About less apps, well, I liked the fact that was a unique app that was able to connect to any DB without much problems. And hardly remember having an issue with DBservers at all...but yeah, the sake of native support is also good.

[Kubig]

We've also deployed ODBC connection per few customers and did not encounter any blocker/critical issue regarding architecture change. But, personally I would like more the DBServer architecture mode due to the same reasons as Cav mentioned.
I am not aware of ODBC is mandatory for UTF-8 on Oracle - can you explain that in detail? We got several customers using UTF-8 entirely on G-platform, but there is no ODBC at all.

[hsujdik]

I liked DB Server model better too, in a way that you could have a set of servers that have the DB Driver and restrict firewall rules only to those servers. But well.. if it works fine, why not change it?

[catanirex]

Hi, Regarding ODBC and utf-8 support in Interaction Server:

From release notes when we upgraded from 8.1 to 8.5 and switched to utf-8 support using -codepage option:
8.5.100.18 (Nov 2014): Support for UTF-8 on Windows as well as on other platforms. On Windows,this support requires Interaction Server to connect to its database using ODBC (not DB Server).