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
6 reads
Tim Mitchell
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
261 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
6 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
14 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
7 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
19 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
10 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-28 (first published: 2020-12-16)
499 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
15 reads
ETL Antipattern: Lazy Metadata
If data is a train, then metadata is the track on which it travels. A good metadata definition in ETL processes will help to ensure that the flow of...
2020-12-15
18 reads
Blogs
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Forums
how to write this query?
Hi everyone I asked this earlier but the desired outcome is a bit different...
Windows logins for users migrated from DomainA to DomainB
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Multiple Deployment Processes
Comments posted to this topic are about the item Multiple Deployment Processes
Question of the Day
Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers