2012-08-17
3,546 reads
2012-08-17
3,546 reads
2012-08-16
3,013 reads
2012-08-15
3,019 reads
2012-08-14
2,672 reads
2012-08-13
2,843 reads
Referential integrity is a very important thing to consider when designing a database. In my years as a DBA I've seen database designs that sit on both ends of the spectrum, none at all and cases where every table is linked to multiple tables. While the later certainly can be a little more difficult to work with it ensures the integrity of your data stays intact. The other end provides much more flexibility when it comes to updating and deleting data from your database, whether it's being done through the application or directly on the backend, but has the issue of possible orphan records if things are not done properly. This tip will look at the DELETE CASCADE option when creating foreign key constraints and how it helps keep the referential integrity of your database intact.
2012-08-13
3,973 reads
Generate a per-schema, per-procedure ordered list of all stored procedures for the current database, together with their parameters, datatypes and nullability.
2012-08-14 (first published: 2012-08-08)
2,246 reads
2012-08-08
3,017 reads
2012-08-07
2,839 reads
2012-08-03
2,640 reads
By John
Today is Christmas and while I do not expect anybody to actual be reading...
By Bert Wagner
Until recently, my family's 90,000+ photos have been hidden away in the depths of...
By Kamil
Managing Microsoft Fabric at scale quickly becomes painful if you rely only on the...
Comments posted to this topic are about the item UNISTR Escape
Comments posted to this topic are about the item Celebrating Tomorrow
Comments posted to this topic are about the item SQL Art: I Made a...
In SQL Server 2025, I run this command:
SELECT UNISTR('*3041*308A*304C\3068 and good night', '*') as "A Classic";
What is returned? (assume the database has an appropriate collation)
A:
B:
C:
See possible answers