Remove antipatterns
article thumbnail

ETL Antipattern: Performing Full Loads Instead of Incremental Loads

Tim Mitchell

In my last post in the ETL Antipatterns series, I wrote about the common antipattern of ingesting or loading more data than necessary. ETL Antipattern: performing full loads instead of incremental loads Earlier this. ETL Antipattern: performing full loads instead of incremental loads Earlier this.

246
246
article thumbnail

ETL Antipattern: Ignore the Logging

Tim Mitchell

In my last ETL Antipatterns post, I wrote about the unexciting but very necessary work of documenting ETL processes. The post ETL Antipattern: Ignore the Logging appeared first on Tim Mitchell. In this post, I’ll discuss a common misstep in ETL process management: ignoring the logs.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

ETL Antipattern: Start With Writing Code

Tim Mitchell

In this first post in my series on ETL Antipatterns, I’m going to discuss one of the most common missteps when building an extract-transform-load (ETL) process: jumping straight into writing code as a first step. ETL Antipattern: start with writing code Most data architects and developers are intensely curious folks.

130
130
article thumbnail

ETL Antipattern: Ignoring the “Why?”

Tim Mitchell

In this final post in my ETL Antipatterns series, I’ll talk about a common big-picture mistake when building ETL processes: ignoring the fundamental question, “why are we doing this?” ” ETL Antipattern: ignoring the “why?” The post ETL Antipattern: Ignoring the “Why?”

130
130
article thumbnail

ETL Antipattern: Lazy Metadata

Tim Mitchell

The post ETL Antipattern: Lazy Metadata appeared first on Tim Mitchell. A good metadata definition in ETL processes will help to ensure that the flow of the data is predictable, robust, and is properly constrained to avoid errors. However, many ETL processes take a hands-off approach when it comes to metadata.

130
130
article thumbnail

ETL Antipattern: Processing Too Much Data

Tim Mitchell

In my continuing series on ETL Antipatterns, I’ll discuss the problem of loading too much data in extract-transform-load processes. ETL Antipattern: processing too much data A common design flaw in enterprise ETL processes is that they are processing too much data.

130
130
article thumbnail

ETL Antipattern: Skipping The Documentation

Tim Mitchell

The post ETL Antipattern: Skipping The Documentation appeared first on Tim Mitchell. Creating technical and business documentation is often looked upon as a tedious chore, something that really ought to be done for every project but is often an easy candidate to push until later (or skip entirely).