In my last post in the ETL Antipatterns series, I wrote about the common antipattern of ingesting or loading more data than necessary. This brief post covers one specific...
2020-12-14
37 reads
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...
2020-12-13
11 reads
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...
2020-12-12
27 reads
We’re rounding the corner to the second half of December, which means it’s time for my favorite holiday: Festivus! Like many of you, I enjoy gathering around the Festivus...
2020-12-12
4 reads
Azure Data Factory has grown in both popularity and utility in the past several years. It has evolved beyond its significant limitations in its initial version, and is quickly...
2020-09-08 (first published: 2020-08-28)
500 reads
Those of us who write technical articles and deliver technical presentations are always on the lookout for the perfect data set for demonstration and testing. Microsoft has done a...
2020-08-17 (first published: 2020-08-06)
657 reads
When moving data in an extraction, transformation, and loading (ETL) process, the most efficient design pattern is to touch only the data you must, copying just the data that...
2020-08-05 (first published: 2020-07-23)
560 reads
A few years back, I wrote a blog post about using an SSIS object variable as a data flow source. In that post, I described how you could load...
2020-07-30
251 reads
For the better part of 15 years, SQL Server Integration Services (SSIS) has been the go-to enterprise extract-transform-load (ETL) tool for shops running on Microsoft SQL Server. More recently,...
2020-07-28 (first published: 2020-07-16)
724 reads
SSIS parameters help to ease the process of passing runtime values to SSIS packages. For values that can change over time, using parameters in SSIS is an ideal means...
2020-07-14 (first published: 2020-07-02)
479 reads
By DataOnWheels
When I created the website on WordPress, I was expecting all the features I...
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
By Kevin3NF
The terminology around reliability is a mess If you’ve ever said, “We’re covered, it’s...
I changed my email address in Edit Profile page, but it has no effect...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers