Stairway to Data, Level 5: Types of Scales – Part I
Joe Celko discusses Nominal, Categorical, Absolute, Ordinal and Rank scales. These are the weakest scales we can use, starting with the weakest.
2019-03-26 (first published: 2011-07-06)
6,677 reads
Joe Celko discusses Nominal, Categorical, Absolute, Ordinal and Rank scales. These are the weakest scales we can use, starting with the weakest.
2019-03-26 (first published: 2011-07-06)
6,677 reads
Joe Celko introduces more powerful scales such as Interval, Log interval and ratio scales; before moving on to conversions, punctuation and units. Finally he gives guidelines as to how best to use scales in a database.
2019-03-26 (first published: 2011-07-27)
4,725 reads
Joe discusses how to deal with the kinds of encoding schemes, how to use them and how to design them. He discusses Enumeration, Measurement, Abbreviation and Algorithmic categories
2019-03-26 (first published: 2011-08-10)
6,108 reads
Joe discusses Hierarchical, Vector and Concatenation encoding before rounding up with general guidelines for designing encoding schemes.
2019-03-26 (first published: 2011-08-31)
4,542 reads
Before you start to think about your database schema or tables, you need to consider your data: the type of data it is, the scale you use for values. It needs to be unique, precise and unambiguous. Then you need to name it in such a way that it can be generally understood. Joe Celko explains...
2019-03-26 (first published: 2010-04-27)
39,418 reads
A clear understanding of SQL Data Types and domains is a fundamental requirement for the Database Developer, but it is not elementary. If you select the most appropriate data type, it can sidestep a variety of errors. Furthermore, if you then define the data domains as exactly as possible via constraints, you can catch a variety of those problems that would otherwise bedevil the work of the application programmer.
2019-03-26 (first published: 2010-05-04)
28,114 reads
There are several types of tables, each with their special requirements for rules and integrity constraints. Whatever the requirement, table-level constraints will ensure that the rules are enforced and data integrity is maintained.
2019-03-26 (first published: 2010-05-25)
21,685 reads
Having described tables, Joe Celko explains how to make them work together as a database and touches on what Entity Relationships and Views are.
2019-03-26 (first published: 2010-08-18)
19,208 reads
Joe Celko tackles the subject of the Stored Procedure and its place in database design. What he writes is food for thought, even for experienced database developers.
2019-03-26 (first published: 2010-08-25)
15,810 reads
In levels one to four, we built the tables, base and virtual, of a schema. Levels five and six dealt with stored procedures. This level deals with a feature you need to avoid as much as possible; this is article is on Triggers.
2019-03-26 (first published: 2011-09-30)
12,361 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