Log in
Maria was hired as a consultant by a large financial institution. The institution had a large pile of ETL scripts, reports, analytics dashboards, and the like, which needed to be supported. The challenge is that everyone who wasn't a developer had built the system. Due to the vagaries of internal billing, hiring IT staff to do the work would have put it under a charge code which would have drained the wrong budget, so they just did their best.
The quality of the system wasn't particularly good, and it required a lot of manual support to actually ensure that it kept working. It was several hundred tables, with no referential integrity constraints on them, no validation rules, no concept of normalization (or de-normalization- it was strictly abnormalied tables) and mostly stringly typed data. It all sat in an MS SQL Server, and required daily manual runs of stored procedures to actually function.
Maria spent a lot of time exploring the data, trying to understand the various scripts, stored procedures, manual processes, and just the layout of the data. As part of this, she ran SELECT queries directly from the SQL Server Management Studio (SSMS), based on the various ETL and reporting jobs.
One reporting step queried the "BusinessValue" column from a table. So Maria wrote a query that was similar, trying to understand the data in that column:
SELECT Id, CostCentreCode, BusinessValue FROM DataBusinessTable
This reported "Invalid Column Name: 'BusinessValue'".
Maria re-read the query she was copying. She opened the definition of the table in the SSMS UI. There was a column clearly labeled "BusinessValue". She read it carefully, ensuring that there wasn't a typo or spelling error, either in her query or the table definition.
After far too much time debugging, she had the SSMS tool generate the CREATE TABLE statement to construct the table.
CREATE TABLE DataBusinessTable
([Id] Number IDENTITY,
ā¦,
[BusinessValue ] TEXT
)
Maria felt like she'd fallen for the worst troll in the history of trolling. The column name had a space at the end.
According to Maria, this has since been "fixed" in SQL Server- you can now run queries which omit trailing whitespace from names, but at the time she was working on this project, that's clearly not how things worked.
The fact that this trailing whitespace problem was common enough that the database engine added a feature to avoid it is in fact, the real WTF.
