Jump to content

Recommended Posts

Posted

Other than different methodologies, are there any differences between the two? Does one work out to be faster or more reliable than the other when deployed at scale? I'm trying out both UDFs, was curious which method is preferred by the community.

Posted

Great question. Took me a while to understand.

DLL connections means that you control that connection. The DLL is deployed with the application and you can run everything through that connection. As DLLs vary, you will need a different one for each type of connection. And with changing DLLs you face the risk of changing your code, too.

ADO presents a uniform communication method that is largely controlled directly by Windows. See the ODBC items. You will need a suitable driver for your data source. But with ADO, the design is that even when you change the data source and data driver, you will not have to change your code.

So for example, using ADO, I can use the same script, same SQL and just change the "ADO.Connection" to switch between SQLite and PostGres.

I hope that helps. 

Skysnake

Skysnake

Why is the snake in the sky?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...