Data Documents and Common Sense
What can be so difficult in creating a sensible standard for Structured Data Documents? To understand why they tend to get improved into unusable complexity, I’ll need to explain a bit of background.
2025-01-06
Design and Theory
2025-01-08 (first published: 2025-01-03)
509 reads
2024-12-20
1,671 reads
Department of Redundancy Department
Ever wonder all the reasons that we use databases instead of file systems? While we don’t think of it too much anymore, the first reason that databases came into existence was to remove redundancies.
2024-04-12
Getting Out of Character
In this article, Joe Celko gives us a history of the different character sets that are used in computing and how that can pertain to your usage in relational databases. Some of these you may have never heard of!
2023-05-17
The VALUES clause or building tables out of nothing
The VALUES clause makes inserting literal values into a table simple and easy. In this article, Joe Celko explains how to use the VALUES clause.
2022-07-01
Combinations, permutations, and derangements
Joe Celko explains how several mathematical concepts, combinations, permutations, and derangements, relate to databases.
2022-06-01
The problem with averages
Everyone learns to calculate an average in school, but, as Joe Celko shows, there are better ways to summarize data.
2022-03-25
Much Ado about nothing: missing data
Joe Celko explains how missing data is handled from the printing press to databases.
2021-07-26
Constraints and declarative referential integrity
Database systems have powerful features built right in that can ensure the integrity of data. In this article, Joe Celko discusses keys and constraints.
2021-05-28
Blogs
The Book of Redgate: We Value Teams
By Steve Jones
This value is something that I still hear today: our best work is done...
Troubleshooting TempDB Log Full Errors When SSMS Won’t Connect
By gbargsley
Have you ever received the dreaded error from SQL Server that the TempDB log...
Accelerating AI with Confidence: Why Microsoft Purview is Key to Responsible Innovation
By Chris Yates
Artificial intelligence is no longer a distant concept. It is here, embedded in the...
Forums
Planning for tomorrow, today - database migrations
Comments posted to this topic are about the item Planning for tomorrow, today -...
Bottlenecks on SQL Server performance
We have a BI-application that connects to input tables on a SQL Server 2022...
Is there some good routines for updating SQL Server database objects with GitHub
At work we've been getting better at writing what's known as GitHub Actions (workflows,...
Question of the Day
The Tightly Linked View
I try to run this code on SQL Server 2022. All the objects exist in the database.
CREATE OR ALTER VIEW OrderShipping
AS
SELECT cl.CityNameID,
cl.CityName,
o.OrderID,
o.Customer,
o.OrderDate,
o.CustomerID,
o.cityId
FROM dbo.CityList AS cl
INNER JOIN dbo.[Order] AS o ON o.cityId = cl.CityNameID
GO
CREATE OR ALTER FUNCTION GetShipCityForOrder
(
@OrderID INT
)
RETURNS VARCHAR(50)
WITH SCHEMABINDING
AS
BEGIN
DECLARE @city VARCHAR(50);
SELECT @city = os.CityName
FROM dbo.OrderShipping AS os
WHERE os.OrderID = @OrderID;
RETURN @city;
END;
go
What is the result? See possible answers