are odbc drivers relevant when discussing a gateway migration?

[db042190]

hi, i'm pretty well versed in the role drivers have for our linked servers, etl,  etc to talk to erps/rdbms's etc.   We install them when necessary and we are happy.

But i saw a memo recently where one peer thinks they are relevant in our migration of the "purchased company's" tenant to our tenant, ie by adding their conns to our gateway (gw) .   I believe the peer believes odbc drivers for the purchased company's mysql instance etc have to be installed (probably if not already there) on the server where the gw service runs.   I guess it kind of makes sense but i never considered it before.  does the gateway need those drivers for reasons similar to the prereqs of our linked servers , etl etc?  ie installed on the same server whee the gw runs?

[lbendlin]

Not only do the drivers need to be installed on all gateway cluster members but the 64bit System DSNs need to be recreated as well.  One (fast) way is to export the registry entries from the old gateways and import them into the new gateway VM's  registries.  Don't forget that you also will need to provide the credentials again (unless they are stored in the registry - but that is not considered good practice)

[tayloramy · Accepted solution]

Hi @db042190, 

THe gateway will need drivers to be able to connect to datasources. For example, a gatewya cannot connect to oracle databases if the Oracle Client for Microsoft Tools is not instlled.  

I expect it will be similar for other database systems, the gateway needs to know how to connect and communicate with the database, and the driver is what tells the gateway these details. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.