Marketo: Difference between revisions

From Starfish ETL
Jump to navigation Jump to search
Line 13: Line 13:
SELECT * FROM Leads WHERE Sugarcrm_id = 'b7e70c80-20cd-9209-24bf-57ae4b05b711'
SELECT * FROM Leads WHERE Sugarcrm_id = 'b7e70c80-20cd-9209-24bf-57ae4b05b711'
</source>
</source>
The same is true for using some fields in ORDER BY.  I'm unsure why this is.  The developers guess is that the Marketo API doesn't actually support some fields in these operations so the CData connector downloads all of the data and does the WHERE or ORDER BY locally, thus taking a very long time.
The same is true for using some fields in ORDER BY.  This is because the Marketo API doesn't actually support some fields in these operations so the CData connector downloads all of the data and does the WHERE or ORDER BY locally, thus taking a very long time. See: http://cdn.cdata.com/help/DKE/ado/RSBMarketo_p_SupportEnhancedSQL.htm

Revision as of 03:36, 1 August 2019

Connector Setup

I used this guide, https://developers.marketo.com/blog/quick-start-guide-for-marketo-rest-api/, to setup an API Role, User and Service and then get the Client ID and Client Secret for that Service.

Origin

The CData website has a help page for the Marketo Connector: http://cdn.cdata.com/help/DKE/ado/default.htm. The SQL examples are helpful.

I've found that I can use some fields in a where clause quickly and others are extremely slow. Id runs in a few seconds.

SELECT * FROM Leads WHERE Id = '104'

Sugarcrm_id runs in 283 seconds.

SELECT * FROM Leads WHERE Sugarcrm_id = 'b7e70c80-20cd-9209-24bf-57ae4b05b711'

The same is true for using some fields in ORDER BY. This is because the Marketo API doesn't actually support some fields in these operations so the CData connector downloads all of the data and does the WHERE or ORDER BY locally, thus taking a very long time. See: http://cdn.cdata.com/help/DKE/ado/RSBMarketo_p_SupportEnhancedSQL.htm