Stairway to Data, Level 7: Data Encoding Schemes - Part I
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 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.
Having described tables, Joe Celko explains how to make them work together as a database and touches on what Entity Relationships and Views are.
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.
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.
In the final step of Database Design, Joe Celko gives a simple but effective explanation of the normalization process and why it is important.
To learn MDX, there is really no alternative to installing the system and trying out the statements, and experimenting. William Pearson, the well-known expert on MDX, kicks off a stairway series on this important topic by getting you running from a standing start.
By Steve Jones
Don’t reserve your kindest praise for a person until their eulogy. Tell them while...
I wanted to try out the new JSON index which is for the moment...
By Brian Kelley
I thought it would be good to put my thoughts down on how to...
Comments posted to this topic are about the item Learning a New Language
Hi, we have a few people who like to experiment on our prod sql...
Comments posted to this topic are about the item Guidelines and Requirements
If I use DBCC CLONEDATABASE, can I remove some of the information from the copy?
See possible answers