Don't Let Corner Cases Drive Your Design
When we design a database or system, we often do so with corner cases in mind. We don't have to do this.
2025-12-01
110 reads
Database Design and Implementation
Being Mindful of Design Time
Do you take the time to model and design your database? Steve thinks this is important, even while trying to make changes quicker to adapt to changing requirements.
2025-11-14
94 reads
Poor Name Choice
Steve has a few thoughts on the names we choose for tables, columns, files, and more.
2025-11-07
137 reads
Data Encoding Schemes
Your choice of how you encode data can be significant. With computers and databases, you have a wide range of options. As a programmer, you will likely be called upon at some time in your career to design and coding scheme for particular application. It would really help if you at least avoided designing a bad one.
2025-06-30
A Domain for Data
A SQL DDL statement that Steve never knew about is the subject of today's editorial.
2025-04-04
126 reads
Scales & Measurements
If you’re going to work with databases, you probably ought to know something about data. In particular, we don’t put data directly into a database; we have to encode it and represent it in a format which a machine can handle.
2025-04-02
A Poor Data Model
Steve has a few thoughts on natural keys, which often turn out not to be as unique as we expect.
2025-03-03
163 reads
Database Sharding: Strategies for Seamless Scaling and Performance Optimization
Companies of all sizes and across industries are struggling to cope with an explosion of data never before seen in the short history of computing. As applications reach new levels of sophistication and become deeply interconnected, these companies find themselves increasingly overworked, overheated, and at their wits’ end, desperately trying to squeeze just a bit more performance and availability out of their aging database architectures.
2024-10-11
Uniqueness, Keys, and Identity
If you’ve ever had a traditional logic course, you’ll have run into “The Law of Identity” as the founding principle of all Western thought. It says that: “To be is to be something in particular; to be nothing in particular or anything in general, is to be nothing at all.”
2024-10-07
Storing and Retrieving the Initialization and Configuration Data for Applications
All developers hit the problem of how and where to store and set their configuration, profile, or initial data. A long time ago, it was generally decided that simple text files containing key/values were best, stored with the application. After all, you are relying on being able to entice busy people to get the permanent settings right for their requirements, folks who are generally not interested in your elegant computer science constructs. Not only that, but the settings must be parsed very quickly and efficiently, otherwise a process that uses the tool will slow to a crawl.
2024-10-04
Blogs
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Advice I Like: In 100 Years
By Steve Jones
In 100 years a lot of what we take to be true now will...
dataMinds Saturday 2026 – Slides
At Saturday the 21st of February I’m presenting an introduction to dimensional modelling at...
Forums
AllocationType as ROW_OVERFLOW_DATA
Hello, I inherited a number of tables with like 20-30 column using nvarchar(256) in...
is it true we cant debug c# scripts in ssis anymore under vs
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
Question of the Day
Missing the Jaro Winkler Distance
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers