Best Practice, CRM, Data integration, Dynamics 365, KingswaySoft, Scribe

Part 6: Data Integration – Return of the Best Practices

Recap Best Practices: Part 2

Welcome back!

My previous blog discussed the use of Staging Databases as part of integration design and some tips and pointers whilst building a staging database (if you decide to use one that is).

My background with data integration is using either out of the box/free tools or 3rd party data integration software (like Scribe or KingswaySoft) and the methods for designing and building data integration have evolved over time. This blog will detail the best practices when dealing with performance issues that I have encountered over the years.

You can apply some (if not all) of these principles for bespoke data integration tools, such as:

  • Web Services
  • Console Applications
  • Utilising a Service Bus (like Azure for integration messaging)

This will be my final* post when discussing best practices with data integration, most of which can be applied when using any tool to complete the integration.

*Star Wars did not end with a trilogy.

Part 3 : Performance Issues and Improving Performance

Performance Issues

Integrating with Dynamics 365 can be a painful learning curve, some of the issues (that I would see as performance related) I have encountered are:

  • Understand of Entity Relationships (I mean who loves integrating with the Activity and Pointer Entities??) which have lead to poor profile design operations being completed by the integration.
  • Data import speed (e.g. records per second or records/second) slowing over time.
  • Network Latency/Connection errors which can arise at any time during the integration.
  • SQL Timeouts due to high load/queries on the D365 database
  • Error exceptions such plugins/workflow failing due to lack of resource or Dynamics 365 providing us with as little detail as possible
  • Server Resources (source related)
  • Database Log File growth (staging database – source)
  • SQL Locks (source)
  • And the list goes on

Additionally, big factor to consider with data integrations and loading data directly into Dynamics 365 is that this can only be achieved via two supported methods:

  • Directly through the Dynamics 365 interface, manually entering though forms, bulk editing or uploading a file using the out of the box import tool.
  • Via the API using one of the many free, 3rd party or custom tools available which connect directly to one of the Dynamics 365 endpoints.

There is no supported method for loading data directly into the Dynamics 365 database, and if anyone asks you to do this, just say NO. So even if you are using a Staging DB no SQL – SQL transfers are NOT allowed.

JustSayNo

With Dynamics 365 Online, Microsoft have protected customers by this method of tomfoolery by restricting access (or even visibility) to the Dynamics 365 Database!

The API

All Dynamics 365 data integrations must be made through the API, which means they:

  • Adhere to the Security Model of the User connecting to Dynamics and performing data load operations via their Security Roles.
  • Trigger any system events or custom automation (bespoke) when record operations occur (e.g. create, update, delete etc.), such as:
    • createdon is populated
  • Back-end relationships are created in the database with other records in the system
    • When records are created, CRM populates the createdby, owner and so on.
  • Caching of data/sharing of records stored to the PoA table.
  • And all additional other magical things system operations Dynamics 365 completes (using the Force!) (such as creating an Audit logs trail etc.).

Performance Implications

Considering the above items, we can see:

  • Firstly why loading data has to be (and can only be) loaded through the API.
  • Why performance maybe slowed by the Dynamics 365 and flowing through the application Layer to the database layer.

Whilst investigating why performance is being impacted, it also makes sense that we investigate ways of improving the performance of data integrations with the aim of improving:

  • Data load times and record/second.
  • The quality and reliability of you integrations

I will walk though a common data load scenario which will highlight a few of the performance issues are listed above and are usually encountered when completing a data migration to Dynamics 365.

I will then review the migration and make suggestions/ list my best practices on how to overcome or help mitigate these issues.

Sales Load Example

For this example, I will walk through a very basic scenario of importing data without using any special tips or best practices; this also assumes that the the data integration tool is importing 1 record at a time (discussed later on). This is a direct source to target data import and all values are made up for the purposes of this example.

If you have the requirement to load a medium size data set (e.g. the last 5 years worth of data) for a customer, and say:

  • 15,000 Accounts
  • 100,000 Contacts
  • 6000 Opportunities
  • 12,500 Opportunity Products

Dynamics 365 Online data migration from a data source.

We will use the example Sales load highlighted in my first blog, the load order would be as follows:

  1. Accounts
  2. Contacts
  3. Opportunity with grouped Opportunity Products

SalesLoad2

Account Load

The loading of the Account data into Dynamics 365 will be relatively painless; it is a simple profile to just perform a Create operation into the CRM database. The Account data set is relatively small and this will probably complete within about 20-25 mins.

When measuring import speed, you will probably hear people talking about records/second (which a 3rd party tool will calculate for you). The average Account import speed here is about 10-15 records/second.

Contact Load

The next step is to load the Contact data into Dynamics 365, this profile is slightly more complicated in the fact that we have to also search for an existing Account to firstly set as the Parent Account ID and also update it with the Primary Contact value.

So instead of the one load operation to Dynamics 365, we have 3 operations with each operation requiring round trips to and from  Dynamics 365 to the data integration tool:

  • Create (Contact)
  • Search and Update (Account and Contact)
  • Update (Account)

Because of the additional work the profile has to do, the import speed may go down to an average of 3-4 records/second as the profile is having to do more work (roughly 3 times). This will take approximately 7 hours to import 100,000 Contact records.

Opportunity Load

This process is actually grouping and loading Opportunities and child Opportunity Product records together and loading these in the same data profile and contains 4 primary operations:

  • Search (Account)
  • Create (Opportunity)
  • Search (Product)
  • Create (Opportunity Product)

With the added complexity of grouping related data together (Opportunity and Opportunity Products) at the source, the profile may only achieve an average maximum of 1-2 records/second; with a maximum of 6000 rows the load time will be around 50 minutes.

Opps

Example Review

Reviewing the Sale Process load example it can seen that increasing the complexity of a data profile can reduce the performance of the import speed.

For low-volume data loads, the time differences can be in minutes or hours which do not impact project timelines too much.

But, consider the impact to projects where the data sets contain millions of rows (i.e. high-volume); the potential increase in project timelines can be calculated in either days or weeks which your customers will not be happy with.

Identifying performance gains will be critical in these scenarios to reduce the time it takes to integrate the data.

Improving Performance

So, how can we go about ways of improving data integration performance?

  1. Environment Optimisation – manipulating the environments around the data such as:
    • Storage location
    • Server Specs (On Premise only)
    • Network Performance
  2. Data Profile Optimisation – breaking down the steps with your data profiles.
  3. Matching Optimisation – increasing the efficiency when matching to records in Dynamics 365.
  4. Record Ownership – assigning record owners in Dynamics 365.
  5. Record Status – Saving your record statuses until last.

Environment Optimisation

There will be different environments for every single data integration, and there will be different things you can try to help improve performance without touching the data integration itself. The changes could be either hardware (e.g. increase Server Memory) or software configuration (e.g. creating a database index) optimisations.

So lets look at the environmental changes we can complete to increase performance when integrating data with Dynamics 365 – first we can split out the environments as follows:

  • Source – You may have one or more source systems if merging from multiple systems; if you have a staging database this will be your source system for your data profiles when loading data into Dynamics 365.
  • Integration Tool Resource – this maybe under your control (i.e. On-premise server)
  • Transit – Network connection between Source, Target and the Integration Tool
  • Target – Dynamics 365 (Online or On Premise).

DataFlow

Source

I will use the Staging Database approach with data integrations to provide the context of the environment, if using a file then there is not too much you can do except clear down erroneous rows or the 63000 extra blank rows that Excel sometimes like to add.

So with Staging Databases, I will make the assumption that this is a SQL database (but same tips will apply to additional database types like MySQL.

Firstly I recommend you look standard best practices for optimising a database; I will list out a few of the key ones that you can actually perform yourself.

  • Create Useful Indexes.
  • Shrinking the database – often (if using Full Recovery mode).
  • Keep on top of Database maintenance plans.
  • Make sure the following routines do not interrupt/occur when your data integration is under heavy load as this will negatively impact the read speed and queries being executed against tables with the potential of generating SQL Timeouts:
    • Backup
    • Shrink
    • Index rebuild

The following tasks may require an Customer System Administrator to complete:

  • Limit your SQL Instance Memory to 1/2 or 3/4 of the SQL Server the instance is located on, leaving the rest available for the Operating System to use.
  • Log Files on separate hard drives
  • Increase the SQL Server allocated memory (to enable the above!
Integration Tool Resource

Some integration tools (like Scribe Insight) require their own Server with its own set of resources (and SQL database); I recommend using the following as a guide when choosing a location for your data integration tool:

  • Take the recommended System Requirements, and then double them.

For bespoke solutions e.g. console apps or web services, make sure they have:

  • Decent connection to Dynamics 365.
  • Adequate memory and processing power to function under extremely high load.
  • A Service Account with appropriate security privileges and access to Dynamics 365.

If these are hosted in Azure and connecting to Dynamics 365 Online, how about moving to the same data center as where your Dynamics 365 instance is located? This will reduce network latency by reducing the number of connections it needs to make to Dynamics 365 via other servers.

Transit

For all tools and bespoke solutions console apps or web services – make sure they have a decent connection to Dynamics 365 (as stated above).

  • Ensure that you are using a secure and encrypted HTTPS connection (applies to On Premise only).
  • Make sure all IP ranges have been authorised through your Firewall for Dynamics 365
Target

Loading data into Dynamics 365 can be affected by any number of items once the connection to D365 has been established. There are several tips I recommend completing whilst loading data into Dynamics 365:

  • Disable any automation such as Workflows and Plugin or SLA which maybe triggered on import create/update.
  • Turn off Email Synchronisation (just in case any get created and sent out).
  • Postpone some of the out of the box internal maintenance schedules in Dynamics 365 (e.g. bulk deletion tasks).
  • For On-Premise deployments, standard Database practices should be completed regularly.
  • Add more resources to the CRM and SQL servers, and split out the Front and Back End server roles onto different Servers with load balancing.

Data Profile Optimisation

We have looked at my recommended best practices from an environmental point of view, next we can look at tweaking the way your data profiles operate and suggesting improvements in logic.

Profile Load Order

The first item to think about is your profile load order, each data integration will require a profile order where the data should be ordered based on the required data to create that record type. The following diagram shows an example scenario for a typical data migration.

ProfileLoad
Example profile order for importing data into Dynamics 365

The decision could be made to either start with Leads or start with the Product Catalog (Products and Price Lists).

My best practices when planning a data integration and the profiles ordering logic are:

  • Understanding the essential “must-have” data for production go-live and build a import plan accordingly.
  • Identifying independent data sets and/or configuration data and focusing on these areas first unless it is not required for go -live or flagged as  “nice to have”.
  • Determining your key data sets which are prerequisites for other data sets (e.g. Accounts are required before you can import Opportunities or Cases).
  • Import smaller data-sets first for quick wins; if you encounter issues with a larger load and are required to be restarted/fixed then at least you have got some data in and you can concentrate of fixing the larger data-set.
  • Finish with Activities/Notes and Attachments; these are often the most complicated and difficult tasks to complete; Activities can also be related to any of the proceeding data (e.g. via the Regarding field) and so I will tackle the hardest items until last. Also – Historic Activities are most likely never going to change; these could also be imported after (not part of any critical path) production go-live.
Select Columns

When querying source data, only select the exact columns you need to process as part of your data integration. Any additional Columns queried, but are not used become a waste of resource and can impact the performance of data profiles.

So in an example source Contact SQL Query:

SELECT [FirstName], [SurName], [Email], [PostCode], [Status]

FROM

CUSTOMER

WHERE [STATUS] = ‘Active’

Instead of the below query which returns all Columns.

SELECT * FROM CUSTOMER

WHERE [STATUS] = ‘Active’

Pre-populate lookups

Populating Lookup fields often requires some element of validation to ensure that the record GUID exists; e.g:

  • Profile will first check to see if the record exists
  • Retrieves the record GUID
  • Sets the GUID in the create/update operation.

This means that for every lookup value that is set requires as part of the data integration, an extra query to and from Dynamics 365 is required before the Create/Update operation would occur. This will slow down the time it takes to complete the transaction for this row (e.g. the record/second would decrease).

On the Case Entity, you may have several lookup GUIDs to query before the Case can be created:

Lookup

If we had these GUIDS before we started the import (as we should have imported the prerequisite data beforehand), then we could populate these fields without having to perform the additional query.

This would reduce the number of steps the profile has to complete to just a single Create Case step and improve the performance of data integration import speed (records/second).

For smaller data-sets, this may not be required as the data does not take much time to load; but for the larger data-sets we can see that improvements to import speed can have a positive impact on the total time it takes to load the entire data set.

To record the GUIDS of the pre-requisite data (especially configuration/Account/Contact data) I will always write back to the source data row in my staging database with the record GUID in the original profile. Or, I will build a separate profile which query Dynamics 365 (as the source) and targets the staging database. This will literally just write the GUID back to the Staging database source row.

So back to my Case import example, assuming I had captured the record GUIDS of each lookup, I could either:

  • Join to the Account,Contact and Product Tables to include the GUID columns in my Case query.
  • Perform a simple SQL Update Script to populate these values (this will take seconds).
Larger Volume Data-sets

Identify your largest data sets, some of these may be simple but some of them maybe complex. The aim is to improve the import speed (record/second) and the larger data-sets will gain the most from performance improvements.

The downside is, importing large volumes of data will eventually slow down table performance in Dynamics 365, which also will have a negative effect when trying to match to records as part of data profiles.

Reduce the number of steps in the profile by completing additional ETL transformations on the Staging Database (if available) – like pre-populating lookup fields; aim for straight inserts or straight update.

Bulk Operations

For simple – high volume profiles, many tools (even bespoke Console Apps/Web Services_ can take advantage of the Bulk methods (ExecuteMultiple) provided by Dynamics 365 where you can submit data in blocks as part of a single transaction. These are designed to increase the throughput of your data to Dynamics 365.

Matching Optimisation

Nearly all data integrations will involve some sort of matching criteria, whether this is to return related record ID’s to populate lookup fields on import or when matching for either create new or update existing records.

Matching to records will often involve matching on key fields (in most cases a single field or key, in others the matching criteria may involve multiple field values.

Single key matching example – matching to Orders:

  • OrderNumber exact match

SingleMatch

Multiple key matching example – matching to Contacts:

  • First Name AND
  • Last Name AND
  • Email Address AND
  • Postcode all exact matches

MultipleMatch

Indexes

Whilst matching to these values may be required and cannot be changed. we can actually create indexes on these columns quite easily. In Dynamics 365, you can directly add these to the Quick Find View – Find Columns for that Entity;  Dynamic 365 will create a database index for you automatically, this is extremely useful for Online environments where you can directly affect the database without touching it.

Additionally – it may be useful to also create indexes on the source columns used for matching over larger data-sets.

Alternate Keys

Where unique records are required to be matched, it may be worth considering creating an Alternate Key in Dynamics 365. Ben Hosking has written a very good article on alternate keys here. This will also create an index in the CRM database which improves lookup times.

Record Ownership

Assigning records to User or Team can take a while even through the web interface, and this may be additionally impacted by cascading relationships to the records children (if applicable) where is child is also assigned to the User or Team. So this may have a negative impact on the data import speed

Where the requirement for records to be have their ownership during a data migration/integration, I considered it best practice on larger data sets or records where cascading relationship exists (e.g. Accounts and Opportunities) to either:

  • Recommended – Split out the record assignment into a completely separate profile after the data has been integrated with Dynamics 365. This will increase the performance of data integration initially creating or updating the record; the Assign action can then be completed post load.
  • Or have an additional relationship to the User Entity (i.e. Assign Owner), populate that during the migration and then have Workflow post Migration/Integration set the Owner to that of the Assign Owner field.

Assign

Tip: Ensure Users:

  • Have been created
  • Assigned the correct Product License (if Online)
  • Security Roles have been assigned which allows them to own the record type you are integrating with.

Record Status

Completing Activities or setting record Statuses can have the same impact that assigning record ownership can have (e.g. cascade behavior). Also, depending on when the profile sets the status, further updates cannot (should not be in most scenarios) be made to those records through the data integration; especially with Activities – you will receive a hard Dynamics 365 error.

So my recommended approach is to consider having a separate record status profile as this will increase the performance of data integration initially creating or updating the record; then a profile to set the record Status executed post load (assuming no further record updates are required).

RecordStatus

Summary

This completes the final blog*: Performance Best Practices blog for the data integration series, I hope you can start incorporating some of these principles into your data integration designs.

Thanks for reading,

MW

*I lied, there is another post to come with more best practices!

Data integration, Uncategorized

Part 2: Data Integration Tools

Recap

In my previous blog – I briefly talked about data and the types of data integration. To recap – the three main types of data integration are:

  • Data Migration
  • Data Integration
  • Data Replication

Data import methods

Data can be imported into CRM via many different ways and either in a supported or an unsupported manner.

Unsupported data import

The main unsupported way some people get data into CRM is by direct database manipulation – Microsoft warns against direct insert/update/deletes directly database by using the phrase “Unsupported operation” (https://msdn.microsoft.com/en-us/library/gg328350.aspx#Unsupported ) i.e. they will not support your CRM system if you decide to play with the database.

Data imported into CRM via this method would not adhere to any security considerations (such as data restricted access for the users) and would not trigger any business logic (such as plugins, workflows etc.); basically the data skips the entire application layer of CRM.

In CRM Online – the SQL database is not even accessible so you are restricted to using the CRM Web services and this is the recommended approach (and the only approach I will ever use for data import*) for CRM on premise data integrations.

*the only exception maybe when I just need to read data out of CRM as a source data system where no update is needed

Supported data import

So when choosing a data integration tool – you will need to choose a tool that can import data into CRM in a supported manner (i.e. either through the UI or through the CRM API using custom application/web services or third-party data integration tools).

Data Integration Types vs Tools

Initially with CRM Projects choosing the correct Data Integration Tool to meet the Data Integration requirements (as these are not always known at this stage in the project), through the Diagnostics/ Analysis stages of a project the initial requirements will surface and the type of data integration will be known (i.e. Migration, Integration and/or Replication).

There are many data integration tools out there – but not all data integration tools can be used across the different types of data integration. For example, if a data integration tool is built to load data into CRM but not extract it from CRM then the tool is only really useful for data migrations/unidirectional (one-way data transfer) data integrations into CRM.

Data Integration Tools – what are available to me?

Firstly – there are many Data Integration Tools which I currently use to meet the data integration requirements of my customers; primarily these can be split into two high level categories:

  • ‘Free’ Tools
  • Cost-associated Tools (such as bespoke development or third-party data integration Products)

‘Free’ Data Integration Tools

The term ‘Free’ should be used loosely – mainly because they are free for everyone to use, but the customer is ultimately paying for your time (I hope!) to complete the data integration requirement.

There are many free data integration tools out there which can be used to aid you in meeting your data integration requirements; here are a few I used:

Config

Microsoft has released the following tool which are included as part of an Office 365 subscription (and will only apply to CRM Online Organisations) and is currently only in preview in certain geographic locations (so I have not used it yet)

Additionally – Microsoft has released some very interesting tools that can be used as effective data integration tools (subject to cost and licensing over the next coming months):

Flow.PNG

I will endeavor to explore these tools over the next few months to gain a better understanding of them; undoubtedly some of you will already be familiar with these already!

Cost-associated Tools

Cost associated Tools are data integration tools where this is an initial outlying cost that must be covered to use the tool – such as purchasing a third-party data integration tool or designing and building a custom data integration application (such as a console app, web service, SSIS package etc.) which your company will need to allocate the required resource to build the application.

Third Party Data Integration Tools

As part of my Job function involves Data Integration – I have become certified in both Scribe Insight and Scribe Online which are developed by Scribe Software (I will do a separate blog on these products at a later date describing each product and how they compare against each other).They are my go to Data Integration tools of choice – my biggest challenge of late is deciding which tool to use! (again more of this another day).

  • Scribe Insight is a powerful data integration platform that is provided as an on premise data integration tool
  • Scribe Online is one of the market leading Cloud based data integration platform (or iPaaS – Integration Platform as a Service) which can provide a complete cloud based data integration between cloud data systems (such as CRM Online and SalesForce)

There are other tools out there; I just have not used any really so I cannot comment on their strengths and weaknesses and where they can be used to meet certain requirements as I lack knowledge.

Custom Data Integration Applications

There have been times where the purchase of a data integration tool may not meet the requirements of the type of data integration (such as a web service being called to retrieve data from CRM and transfer it to a target data source) as the data integration tool may be too slow for this type of request. This is where CRM developers are required to build custom applications to act as a data integration tool.

Examples of custom applications are:

  • Web Services – these sit in between two data systems and communicate through each others API’s
  • Console Applications – applications which sit on computer services
  • Plugins, Custom Workflow Activities calling CRM Actions
  • SSIS Jobs/packages

To summarise

In this blog I have identified some of (the many) data integration tools available for you to use (but not told you how to use them – that I will leave up to you); in my next blog – I will highlight the types of data integration and which tools (listed above) can be used to help meet the data integration requirements of your projects.

Thanks for reading! MW

Data integration, Uncategorized

Defining Data Integration Types

Overview

Over the next few weeks I will write a series of blogs relating to data (based on my personal experience) – this will involve the following topics (from the outset – I may add more!):

  • Defining Data Integration Types
  • Identifying the correct Data Integration tool for the project
  • How to plan and manage Data Integrations as part of a CRM project (including my best practices)

Data

How many of your CRM projects have the vague Requirement of “Data”? I am willing to bet that 99% of your projects will have at least the basic requirement “Data Integration” such as importing Contacts or Account data at some point in your project (there is always that one customer who wants a vanilla system and will start afresh).

Every CRM project I have worked on in the last three years has involved an element of “data integration” – my role varies from (on a project by project basis and sometimes I perform all three roles in a single project):

  • Solution Architect/Lead Consultant
  • Functional consultant
  • Data Integration Consultant

Whichever role I am involved with in the project – my mind always considers the data requirements, the CRM solution being designed not only needs to match the business requirement and processes of the end-user – but the underlying data model should be designed to allow any historic or integrated data to be mapped correctly and maintain key existing information (such as relationships to other data). This means you need to involve data analysis early on in your project to make sure that the data can be imported into a suitable format.

Data Analysis

Analysis of source data (or data systems) early on will help you identify any potential tables and related attributes (fields and data types) early on in the project that you made need to custom build; it can also aid in mapping this data so you know what to expect further on down the line. The opposite side would allow you to see which areas of CRM have no concept in existing systems (such as Emails or Appointments etc.) and you can eliminate these areas early on.

The main output from data analysis will determine the type of Data Integration required.

Types of Integration?

The term Data Integration is loosely used when a project is incepted – what we need to define when we talk about Data Integration relating to a CRM Project is that we can split this term up into three main types:

  • Data Migration
  • Data Integration
  • Data Replication

Defining the type of Data Integration is key to determining the Data Integration tool we can use.

Data Migration

To put it simply – Data Migration is the process of transferring data from one or more data source systems or storage locations (such as a SQL Database, Spreadsheets or other files types, formats, or IT systems) into a single target data system. Once the data has been transferred from the source system to the target system, the source system is usually archived off and will no longer be used after Go-Live of a CRM project.

Some examples of a data migration:

  • Goldmine to Microsoft Dynamics CRM
  • Microsoft Dynamics CRM 2011 to Microsoft Dynamics CRM Online
  • Excel Spreadsheets to Microsoft Dynamics CRM
  • And So on…

mig

Data Integration

Data Integration is a little more complicated and covers a broader method of data transfer – in its simplest form it might be one of the same scenarios as mentioned in the data migration section but a continuous one-way data flow from the source system to a target system (and the source system is still used). This is known as a Unidirectional Data Integration (One Way Data flow).

Some examples of a Unidirectional Data Integration (One-way data flow):

  • Back office ERP System to Microsoft Dynamics CRM
  • Website Lead Generation Microsoft Dynamics CRM Online
  • Microsoft Dynamics CRM Online to Microsoft Dynamics CRM Online (where development/UAT organisations maintain up to date data for testing and training purposes)

1way

A Bi-directional (two-way data flow) Data Integration can be defined a data transfer between two data systems where data from each system is required to be transferred to each other.

Some examples of a Bi-Directional Data Integration:

  • Back Office ERP to Microsoft Dynamics CRM (and Vice versa)
  • Microsoft Dynamics CRM Online to Microsoft Dynamics CRM Online (where configuration data is kept up to date in all organisations – Dev or UAT and Live)

2way

Omni-Directional Data Integrations

The same as a Bi directional data integration but where data is transferred across more than two data systems.

Some examples of an Omni-Directional Data Integration:

  • Multiple Back Office ERP systems to Microsoft Dynamics CRM to SQL Staging Database to Front End Website Database
  • Microsoft Dynamics CRM Online to Microsoft Dynamics CRM Online (where configuration data is kept up to date in across all organisations – Dev, UAT and Live)

Omni

Data Replication

What is Data Replication? Well in the CRM Online world – a customer does not have direct access to the CRM database like an On Premise customer would have access to (because – you know, CRM sits on top of a big shiny SQL DB!) – so this makes writing SQL based reports impossible (restricted to Fetch based XML SSRS reports) or can they effectively control the back up of their live database. So the term Data Replication is the process of making a copy of a target data system either into a replica database or data system. (Such as CRM Online being replicated to a SQL DB for reporting or local backup purposes).

RS

Data Integration Tools

In my next blog – I will discuss the various data integration tools that I have used with my projects and I will mention other tools that I know of; but before we can talk about deciding which data integration tool to use – the type of data integration must be clearly defined as not all data integration tools can be used for each type of data integration.

Thanks for reading! MW