Marketo and DataDirect Cloud Reference for Developers: Handling this matrix of data models and objects across all SaaS sources was certainly a challenge.
AQUA DATA STUDIO EXPORT CONNECTIONS HOW TO
How to handle data models? Is it static or dynamic? How are changes detected and communicated to the client? Each SaaS data source is different and in the case of Marketo, certain objects are better queried through views and others through tables.Leverage the superior bandwidth between DataDirect Cloud and Marketo where pre-joined datasets get exchanged.Faster performance and use fewer memory/CPU resources on the client application server or desktop.Therefore, deployment of the data access layer to an elastic cloud service such as DataDirect Cloud makes a lot of sense for two reasons: When joining two very large objects, the data access layer may use up considerable resources on the application server or desktop. This requires a translation from SQL to efficiently call Marketo APIs to return the minimal amount of data prior to performing the join. In cases where the SaaS APIs do not support a query language with JOIN capability, the engineering team has to perform that operation. It required a significant effort to provide a standard experience querying across the entire data model. Each object may be exposed with a different API with unique rules for invoking, searching filtering, etc. In those cases, the engineering team looks at each object individually. Not all SaaS APIs expose a standard query language.R&D challenges building SQL connectivity across cloud sources such as Marketo Here are other DataDirect Cloud tutorials that apply to Marketo: Here’s a video example of connecting using the DataDirect Cloud ODBC client.
AQUA DATA STUDIO EXPORT CONNECTIONS DRIVER
Click on “SQL Testing” if you want to inspect the Marketo schema exposed or issue basic SQL queries from within the UI.Note there is an OData tab to produce OData from Marketo and we will discuss in a future blog post. You can check with your Marketo administrator or login to find connection information for SOAP integration. Select “Marketo” and enter the connection information.Click “Data Sources” and then “+New Data Source” button.DataDirect Cloud Service abstracts the Marketo API such that end users do not have to worry about API version changes, or using SOAP versus REST.ĭataDirect has been building this style of connectivity to SaaS data sources since 2006 starting with the first Salesforce ODBC driver built on top of its web service APIs.DataDirect Cloud connectivity is direct and real-time without any duplication of data.DataDirect Cloud processes SQL requests from lightweight ODBC or JDBC clients using an elastic real-time query engine on data fetched from the Marketo APIs.DataDirect Cloud creates a logical schema for data exposed by Marketo’s integration APIs.
Data Preparation (Alteryx, Trifecta, Paxata).Ad Hoc Query (Microsoft Office, DB Visualizer, Aqua Data Studio).Data Federation (SQL Server Linked Server, SAP Hana SDA, Oracle Database Gateway).Data Integration (SQL Server Integration Services – SSIS, Oracle Data Integrator – ODI, Informatica).Enterprise Reporting (SAP Business Objects, Microstrategy, Cognos).Data Discovery and Visualization (Qlik, Tableau, SAP Lumira).Below are some popular use cases for connecting Marketo data out-of-box using DataDirect Cloud: DataDirect Cloud is a data connectivity service that exposes Marketo data through open industry standards for SQL access across ODBC (“Open Database Connectivity”) or JDBC (“Java Database Connectivity”) and REST with OData (“Open Data Protocol”). We are seeing the lines blur at Marketo shops between Marketing and IT which is increasing the demand for standards based SQL connectivity.ĭirect SQL connectors to Marketo are available through Progress DataDirect Cloud. However, sometimes organizations need direct SQL access. Marketo has well documented APIs for accessing data. This is a guest post from Sumit Sarkar of Progress, Inc.
0 kommentar(er)
