![]() |
VOOZH | about |
This article illustrates using the QuickBooks ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of QuickBooks data to a Microsoft SQL Server database. It's worth noting that the identical process detailed below is applicable to any CData ADO.NET Data Providers, enabling the direct connection of SQL Server with remote data through SSIS.
CData simplifies access and integration of live QuickBooks data. Our customers leverage CData connectivity to:
Customers regularly integrate their QuickBooks data with preferred tools, like Power BI, Tableau, or Excel, and integrate QuickBooks data into their database or data warehouse.
In the Data Flow screen, add an ADO.NET Source and an OLE DB Destination from the toolbox.
๐ The components used in the data task in this example.In the connection manager, enter the connection details for QuickBooks data.
When you are connecting to a local QuickBooks instance, you do not need to set any connection properties.
Requests are made to QuickBooks through the Remote Connector. The Remote Connector runs on the same machine as QuickBooks and accepts connections through a lightweight, embedded Web server. The server supports SSL/TLS, enabling users to connect securely from remote machines.
The first time you connect, authorize the Remote Connector with QuickBooks. See the "Getting Started" chapter of the help documentation for a guide.
๐ Connection properties in the Connection Manager dialog. (Salesforce is shown.)Open the DataReader editor and set the following information:
SELECT Name, CustomerBalance FROM Customers
Open the OLE DB Destination and enter the following information in the Destination Component Editor.
Configure any properties you wish on the Mappings screen.
๐ Input and destination columns in the OLE DB Destination Editor.Download a free trial of the QuickBooks Data Provider to get started:
Download NowLearn more:
๐ QuickBooks IconComplete read-write access to QuickBooks enables developers to search (Customers, Transactions, Invoices, Sales Receipts, etc.), update items, edit customers, and more, from any .NET application.