Hello,
My company's databases are both on premises and in the cloud. We have been using DCM with ODBC connections for the Azure SQL databases, but they are running very slow. We use DCM because we need to schedule these workflows on the server. It would be great for DCM to accept an OleDB connection.
However:
For the 2024.1 designer the DCM specifications say that OleDB is Not Needed for DCM. Does anyone know why it is not needed?
Also there was an idea post to add OleDB to DCM back from 2022. If you think you'd use this functionality plus upvote this:
For our infrastructure, OleDB is much much faster. A query pulling 3 million records sometimes takes 45 minutes using ODBC, but OleDB connections do the same in 2 minutes. As I try to talk up Alteryx around my company, one of the main users is going to switch their workflows to manually execution so they can use the OleDB connection to Azure SQL Db. It is not winning over minds for this one.
Thanks,
Ken
Hey @MarqueeCrew ,
Sorry to blast you here, but wanted to get your thoughts on this. I've been an Alteryx user for a long time and you even came to our user group once driving all the way to Ohio!
Anyway, we have data on an Azure sql database and it is painfully slow using Data Connection Manager ("DCM") with ODBC. We use DCM because we need to schedule it on the server. If the server was on premises then I would use an OleDB connection which cuts down workflow time significantly.
Do you have any insight on why the documentation says OleDB is "Not Needed" for DCM? Do you know of another way to schedule workflows against Azure datasources without using DCM?
Thanks and hope you're doing well,
Ken