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.
SSAS Maestro, SQL Server MVP and Business Intelligence Architect Bill Pearson introduces the MDX Head() function, which allows us to return, in order, a specified number of elements within a set.
Return, in order, a specified number of elements from the end of a set. SSAS Maestro, SQL Server MVP and Business Intelligence Architect Bill Pearson introduces the MDX Tail() function.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item Midjourney, Healthcare?
Comments posted to this topic are about the item Changes, Happiness, and a Few...
Comments posted to this topic are about the item BCP on Linux
When running bcp on Linux, what is the field terminator?
See possible answers