ETL Antipattern: Ignore the Logging
In my last ETL Antipatterns post, I wrote about the unexciting but very necessary work of documenting ETL processes. The logging of ETL operations is just as (un)captivating as...
2020-12-21
5 reads
Tim Mitchell
- Interests: SQL Server, Data Warehousing, ETL, Data Architecture, Python, Dbt
- Website: https://www.TimMitchell.net
- Bluesky: tmitch.net
ETL Antipattern: Skipping The Documentation
Documentation is an asset that is both loathed and loved. Creating technical and business documentation is often looked upon as a tedious chore, something that really ought to be...
2020-12-20
13 reads
ETL Antipattern: Skipping The Documentation
Documentation is an asset that is both loathed and loved. Creating technical and business documentation is often looked upon as a tedious chore, something that really ought to be...
2020-12-20
5 reads
ETL Antipattern: Load Processes that Don’t Scale
One of the most significant design considerations in ETL process development is the volume of data to be processed. Most ETL processes have time constraints that require them to...
2020-12-19
260 reads
ETL Antipattern: Load Processes that Don’t Scale
One of the most significant design considerations in ETL process development is the volume of data to be processed. Most ETL processes have time constraints that require them to...
2020-12-19
5 reads
ETL Antipattern: Failure to Test and Validate
“If it compiles, it works.” – An unemployed developer Building ETL processes is quite easy. Building ETL processes that deliver accurate results as quickly as possible is substantially more...
2020-12-18
13 reads
ETL Antipattern: Failure to Test and Validate
“If it compiles, it works.” – An unemployed developer Building ETL processes is quite easy. Building ETL processes that deliver accurate results as quickly as possible is substantially more...
2020-12-18
6 reads
ETL Antipattern: Failing to Treat ETL Logic as Source Code
In most data projects, building the extract-transform-load (ETL) logic takes a significant amount of time. Enterprise ETL processes must do several things well: retrieve enough data to satisfy the...
2020-12-17
18 reads
ETL Antipattern: Failing to Treat ETL Logic as Source Code
In most data projects, building the extract-transform-load (ETL) logic takes a significant amount of time. Enterprise ETL processes must do several things well: retrieve enough data to satisfy the...
2020-12-17
9 reads
ETL Antipattern: No Error Handling Logic
I usually avoid talking about technology in absolutes, but here’s one that I can share without reservation: On a long enough timeline, every single ETL process will eventually fail....
2020-12-16
14 reads
Blogs
Learning from Mistakes: T-SQL Tuesday #194
By Steve Jones
We’re a week late, once again my fault. I was still coming out of...
Stupid Things I Did With AI: ASCII Art
By Steve Jones
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...
Simple Talks Podcasting in 2026
By Steve Jones
I’m in the UK today, having arrived this morning in London. Hopefully, by this...
Forums
Learning From Breakage
Comments posted to this topic are about the item Learning From Breakage
Python in Action to Auto-Generate an Optimized PostgreSQL Index Strategy
Comments posted to this topic are about the item Python in Action to Auto-Generate...
Adding and Dropping Columns I
Comments posted to this topic are about the item Adding and Dropping Columns I
Question of the Day
Adding and Dropping Columns I
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ) ON [PRIMARY] GOI decide to add two new columns for the StateProvince and Country. What code should I use? See possible answers