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,252 reads
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,145 reads
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,342 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.
2018-01-24 (first published: 2011-09-30)
11,188 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.
2017-10-25 (first published: 2010-08-25)
14,750 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.
2016-06-01 (first published: 2010-05-04)
26,647 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.
2013-10-16 (first published: 2010-08-18)
18,102 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.
2013-09-18 (first published: 2010-05-25)
20,455 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...
2013-07-03 (first published: 2010-04-27)
36,773 reads
As part of the LAMP stack, MySQL is incredibly important for providing a reliable and platform-agnostic database platform for web development. This level looks at the syntax of MySQL and how to best port SQL code to a MySQL environment.
2012-12-05
4,159 reads
Sometimes in life you have to do things you really don’t like to do....
By HamishWatson
Welcome to the first April edition of T-SQL Tuesday. I’m honoured to be hosting...
By Steve Jones
Last week went a little crazy, and I learned something: don’t post a Zoom...
Hi, I need to include a very simple schema in all of my database...
This is my first time dealing with CLR assemblies and we have setup some...
Hi, I have a requirement to convert a date value like '7th March 2020' ...
Ask SSC