We use cookies, including third-party cookies from Google to serve personalized ads through AdSense, to operate this site and understand how it is used. By continuing to browse, you accept this use. See our Privacy Policy and Terms of Use for details, including how to opt out of personalized advertising.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    Flat editorial illustration: The article is about joining public web signals with internal business metrics so BI teams can inter
    Alternative Data in BI: Bringing Public Web Data Into Your Dashboards
    23 Min Read
    Flat editorial illustration: The article is about automating the collection, preparation, and delivery of marketing data across p
    From Data to Dashboards: 5 Marketing Reporting Automation Software Picks
    12 Min Read
    Flat editorial illustration: The article contrasts passive follower totals with a behavioral path from attention and trust to cli
    Creator Analytics Beyond Follower Count: Seven Metrics That Measure Audience Behavior
    11 Min Read
    Flat editorial illustration: The article connects AI and marketing analytics with managerial judgment grounded in consumer behavi
    How an Online MBA in Marketing Connects AI and Data Analytics
    11 Min Read
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers -- AI-generated illustration
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers
    7 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: My take on why ETL has not always kept up with the integration workload
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Warehousing > My take on why ETL has not always kept up with the integration workload
Business IntelligenceData Warehousing

My take on why ETL has not always kept up with the integration workload

RickSherman
RickSherman
4 Min Read
My take on why ETL has not always kept up with the integration workload
Photo by Christina Morillo on Pexels (https://www.pexels.com/photo/person-with-silver-macbook-on-lap-surrounded-by-books-1181573/)
SHARE

Why are companies reaching the limits on the workhouse ETL? Here are some thoughts that occurred to me as I was snowblowing 20+ inches of snow today. I’ll be discussing this further in the Thursday DM Radio broadcast.

The main reason why ETL is not keeping up is that demand is significantly increasing:

  • The number of data sources, data volumes, update frequencies, need for data consistency (cleansing, conforming, MDM, CDI, PIM, etc.) are all on the rise.
  • Data architecure and workflows have become more extensive and sophisticated to meet business needs.
  • Companies are using ETL for more than data warehousing
  • ETL is not just batch-oriented nightly loads, but rather data integration using various data transports and supporting various data currencies

ETL or data integration tool capabilties have expanded and there are many techniques that have been around forever that still work today but people aren’t taking advantage of these solutions. There are several issues:

First, there is still too much ETL hand-coding. Although most large corporations use ETL tools to load the data warehouse,  departments or functions within the same companies often hand-code data marts, OLAP cubes or other databases used for business intelligence and analytics. In addition many midsize and smaller firms hand code because they think all ETL tools are expensive.

More Read

Defining Business Intelligence 3.0
Defining Business Intelligence 3.0
Tough Analytics? Watson to the Rescue
Wielding Analytics to Conquer the Customer Experience Battle
5 Types of Business Technology Every Entrepreneur Should be Using
How Business Analytics Can Lead to That ‘Aha’ Moment

(They’re wrong. There are plenty of cost-effective and capable ETL tools in the marketplace today.)

Second, people don’t use ETL tools properly. Many ETL developers are either using their ETL tools as if they hand-coded, or they are simply using ETL tools to run hand coded SQL scripts or stored procedures. This approach does not use any of the ETL tool capabilities nor leverage ETL best practices. The result: less efficient, less productive data integration.

Third, people don’t understand data integration. Even when ETL developers do attempt to use ETL tool capabilities they often do not really understand data integration processes.  If they have any training it is only tool specific; they haven’t learned basic data integration processes. In this scenario ETL productivity and performance suffers. The real solution would involve learning the skills necessary to leverage the tools more effectively.

Fourth, people don’t know ETL’s secrets. There are many “old” tried and true techniques and utilities that greatly improve the performance and productivity of ETL processes. But ETL develpers don’t know they exist – probably because they’re not sexy enough to be touted in industry literature.  The classic example is extracting data from a source system into a file and then cleansing, transforming and sorting the file prior to loading into a data warehouse. Although this technique is old-school, it’s a very cost-effective and productive way to significantly improve load performance.

Some steps in the right direction

BI vendors have built many of the best practices in data warehousing, such as various slowly changing dimensions (SCD) and change data capture (CDC) techniques, into their data integration products as ETL transforms.  These transforms significantly improve developer productivity and system performance, and are quite cost-effective.

Another positive note is that, finally, there are many advances in ETL processing that can significantly improve performance. You’ve heard about the benefits of in-memory analytics. In-memory ETL processing results in referential integrity checking and faster lookups,  and improves overall load time.

There are many other capabilities that can likewise improve ETL performance. I will be discussing these points and others during the broadcast.

TAGGED:information extraction
Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

b2b payment data tells supplier about its customers
What B2B Payment Data Tells a Supplier About Its Customers
Business Intelligence
Flat editorial illustration: The article connects downstream report failures, data-quality gaps, and conflicting metric definitio
Signs Your Data Architecture Needs an Outside Review
Big Data Exclusive
Data-Driven Pultrusion: Best GFRP Rebar Machines & ROI
Data-Driven Pultrusion: Best GFRP Rebar Machines & ROI
Big Data Exclusive
Flat editorial illustration: The article contrasts tools for gathering fresh interviews with tools for analyzing existing qualita
10 AI Market Research Tools That Turn Qualitative Data into Insights
Artificial Intelligence Big Data Exclusive

Stay Connected

1.2KFollowersLike
33.7KFollowersFollow
222FollowersPin

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
Chatbots
Artificial Intelligence for eCommerce: A Closer Look
Artificial Intelligence for eCommerce: A Closer Look
Artificial Intelligence

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-26 SmartData Collective. All Rights Reserved.
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?