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
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
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-28 (first published: 2020-12-16)
498 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
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
17 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers