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
98 reads
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
98 reads
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
91 reads
Steve has a few thoughts on the names we choose for tables, columns, files, and more.
2025-11-07
132 reads
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 SQL DDL statement that Steve never knew about is the subject of today's editorial.
2025-04-04
122 reads
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
Steve has a few thoughts on natural keys, which often turn out not to be as unique as we expect.
2025-03-03
155 reads
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
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
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
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
By Steve Jones
One of the things that I like about the SQL Server docs (MS Learn...
By Brian Kelley
For a number of years I have subscribed to Randy Franklin Smith's Patch Tuesday...
is there a no code way to limit an ssis extract from excel to...
Hello Need help in pivoting this data set, the Pivot takes MIN/MAX on a...
hi we have to replace talend which generally was used to move files. talend's...
In SQL Server 2025, what does this return?
CREATE TABLE Numbers ( n INT) GO INSERT dbo.Numbers ( n ) VALUES (1), (2), (3) GO SELECT PRODUCT(n) FROM dbo.NumbersSee possible answers