Visual Studio 2005 Professional Edition.SQL Server 2005 Standard/Enterprise Edition with SQL Integration Service Installed.Here I would like to share with all of you on what I have learned so that you can leverage it on your next CRM integration projects.īefore we get started, here’s the list of requirements: I was able to successfully integrate CRM 4.0 using SSIS. Thanks again to Darren Hubert and his friends, who showed me a work around using a CRM proxy class in my last project. SSIS replaces the existing Data Transformation Services (DTS), which was introduced to the market as a component of SQL Server 7.0, and runs a unique package which stores the design of an ETL (Extraction -> Transformation -> Load) process.īecause SSIS in SQL 2005 was difficult to connect to Web Services by default, I did not spend much time into my research for my previous integration projects. SSIS is a platform for building data integration solutions and it is a service that runs on the SQL Server. When I think of integrations between systems, the common approaches pop up immediately in my mind are BizTalk, Scribe or to write a custom integration framework using the CRM Software Development Kit (SDK).īy working with Darren Hubert, Solution Architect from the Microsoft National Service Pursuit Team in my last project, I have discovered another approach that I encourage you to consider in the your integration project which involves using SQL Integration Services (SSIS) to integrate with Microsoft Dynamics CRM. Many Microsoft Dynamics CRM (MSCRM) implementations involved integration with other systems. Today we welcome our guest blogger CRM MVP Darren Liu from the Crowe company.

Microsoft dynamics crm tutorials