2020-10-12
1,634 reads
Joe Celko
Stairway to Data, Level 4: Temporal Data
Joe Celko tackles the most difficult of all the types of data handled by SQL, temporal data, and explains how to avoid the commonest traps for the unwary programmer
2020-07-08 (first published: 2011-06-15)
10,749 reads
Stairway to Database Design Level 6: Procedure Bodies
Having covered the procedure headers in SQL Server in the previous level, Joe tackles the subject of the contents of stored procedures. In this level, he outlines limitations of TSQL as a procedural language, and what you need to bear in mind when deciding how to use them.
2019-04-03 (first published: 2011-09-21)
12,757 reads
Stairway to Data, Level 1: The Basics
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.
2019-02-06 (first published: 2011-05-12)
19,338 reads
Stairway to Database Design Level 9: Normalization
In the final step of Database Design, Joe Celko gives a simple but effective explanation of the normalization process and why it is important.
2018-02-21 (first published: 2011-11-11)
13,549 reads
Stairway to Database Design Level 7: Triggers
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.
2018-01-24 (first published: 2011-09-30)
11,302 reads
Stairway to Database Design Level 5: Procedures
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.
2017-10-25 (first published: 2010-08-25)
14,871 reads
Stairway to Database Design Level 2: Domains, Constraints and Defaults
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.
2016-06-01 (first published: 2010-05-04)
26,808 reads
Stairway to Database Design Level 4: Building a Schema
Having described tables, Joe Celko explains how to make them work together as a database and touches on what Entity Relationships and Views are.
2013-10-16 (first published: 2010-08-18)
18,199 reads
Stairway to Database Design Level 3: Building Tables
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.
2013-09-18 (first published: 2010-05-25)
20,586 reads
Blogs
The T-SQL Tuesday Corollary
T-SQL Tuesday is a fantastic series of blog posts derived from over 130 topics...
How to Import Perfmon Data into a SQL Server for Analysis
By kleegeek
If you followed the last video, I showed you how to set up windows...
How To Set Up Perfmon for 24×7 Collection
By kleegeek
I just released a new training video (one of many to be released in...
Forums
Always On Read-only routing
I was working on with requirement to load balance the traffic coming from application...
SQL Query Help - display records
Need help with Query. CREATE TABLE #tblTemp (IName varchar(50), ICategory varchar(20), IValues varchar(10)) insert...
Stored Procedures and Entity Framework not returning columns
I have a developer using Entity Framework and the metadata isn't returning for some...
Ask SSC