A great deal of the confusion that occurs when a database application is developed comes from a poor understanding of the basics of data. Here, Joe Celko gives a broad coverage of the difficulties you're likely to meet when handling data in databases.
A confusion about the nature of numbers can lead to a number of problems in database applications. Joe Celko gives a simple guide to the subject
Character-handling in SQL is not particularly straightforward, and confusion about collation and character encoding is a common cause of problems with searching, joining, and sorting.
Joe Celko discusses Nominal, Categorical, Absolute, Ordinal and Rank scales. These are the weakest scales we can use, starting with the weakest.
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.
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
Joe discusses Hierarchical, Vector and Concatenation encoding before rounding up with general guidelines for designing encoding schemes.
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...
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.
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.
By Steve Jones
Prompt AI released recently and I decided to try a few things with the...
By gbargsley
Recently, I was in a technical interview where the topic of running PowerShell at...
By alevyinroc
I don’t recall where this came up (probably in SQLSlack), but I had a...
i have sqlexpress on rds, is there any way i can get notifacation that...
Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation
Comments posted to this topic are about the item Stairway to Azure SQL Hyperscale...
A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?
See possible answers