VOOZH about

URL: https://www.cdata.com/kb/tech/dynamics365-ado-ssistask.rst

⇱ Back Up Dynamics 365 data to SQL Server through SSIS

Back Up Dynamics 365 data to SQL Server through SSIS

👁 Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Effortlessly backup data to SQL Server by utilizing the CData ADO.NET Provider for Dynamics 365. In this article, we will employ an SSIS workflow to populate a database with Dynamics 365 data data.

This article illustrates using the Dynamics 365 ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Dynamics 365 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.

About Dynamics 365 Data Integration

CData simplifies access and integration of live Microsoft Dynamics 365 data. Our customers leverage CData connectivity to:

  • Read and write data in the full Dynamics 365 ecosystem: Sales, Customer Service, Finance & Operations, Marketing, and more.
  • Extend the native features of Dynamics CRM with customizable caching and intelligent query aggregation and separation.
  • Authenticate securely with Dynamics 365 in a variety of ways, including Azure Active Directory, Azure Managed Service Identity credentials, and Azure Service Principal using either a client secret or a certificate.
  • Use SQL stored procedures to manage their Dynamics 365 entities - listing, creating, and removing associations between entities.

CData customers use our Dynamics 365 connectivity solutions for a variety of reasons, whether they're looking to replicate their data into a data warehouse (alongside other data sources) or analyze live Dynamics 365 data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).


Getting Started


  1. Open Visual Studio and create a new Integration Services project.
  2. Add a new Data Flow task from the toolbox onto the Control Flow screen.

  3. 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.
  4. Add a new connection and select .NET Providers\CData ADO.NET Provider for Dynamics 365.

  5. In the connection manager, enter the connection details for Dynamics 365 data.

    Edition and OrganizationUrl are required connection properties. The Dynamics 365 connector supports connecting to the following editions: CustomerService, FieldService, FinOpsOnline, FinOpsOnPremise, HumanResources, Marketing, ProjectOperations and Sales.

    For Dynamics 365 Business Central, use the separate Dynamics 365 Business Central driver.

    OrganizationUrl is the URL to your Dynamics 365 organization. For instance, https://orgcb42e1d0.crm.dynamics.com

    👁 Connection properties in the Connection Manager dialog. (Salesforce is shown.)

  6. Open the DataReader editor and set the following information:

    • ADO.NET connection manager: In the Connection Managers menu, select the Data Connection you just created.
    • Data access mode: Select 'SQL command'.
    • SQL command text: In the DataReader Source editor, open the Component Properties tab and enter a SELECT command, such as the one below:
      SELECT GoalHeadingId, Name FROM GoalHeadings WHERE Name = 'MyAccount'
    👁 The connection and query specified in the source component properties. (Salesforce is shown.)
  7. Close the DataReader editor and drag the arrow below the DataReader Source to connect it to the OLE DB Destination.

  8. Open the OLE DB Destination and enter the following information in the Destination Component Editor.

    • Connection manager: Add a new connection. Enter your server and database information here. In this example, SQLExpress is running on a separate machine.
    • Data access mode: Set your data access mode to "table or view" and select the table or view to populate in your database.

  9. Configure any properties you wish on the Mappings screen.

    👁 Input and destination columns in the OLE DB Destination Editor.
  10. Close the OLE DB Destination Editor and run the project. After the SSIS task has finished executing, your database will be populated with data obtained from Dynamics 365 data.
CodeProject

Ready to get started?

Download a free trial of the Dynamics 365 Data Provider to get started:

 Download Now

Learn more:

👁 Dynamics 365 Icon
Dynamics 365 ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with Dynamics 365.