humor

External Article

The Concept of Cardinal Reciprocity- A Primer

  • Article

Too many authors in the field of relational theory have neglected the concept of Cardinal Reciprocity. This can cause a number of subtle problems with database design in terms of its derivability, redundancy, and consistency. . Increasingly, this little-understood aspect of relational theory, that emphasises the cardinality of the attributes of tuples in a relation and the reciprocity with isomorphic foreign key restraints, is becoming a hot forum topic.

2009-04-01

2,846 reads

External Article

A Halloween Tale

  • Article

A while back, in a Simple-Talk editorial meeting, someone bet Phil that he couldn't come up with a Halloween story. To our surprise he said he could, as long as he didn't have to keep to the strict literal truth.

2008-10-31

3,002 reads

Blogs

Trace Flag 1448 – Lessons from a Technical Interview

By

In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...

Disable the sa login in SQL Server (and sleep better)

By

Disable the sa login in SQL Server (and sleep better)If you run SQL Server...

Leadership in Times of Change: Guiding Teams Through Uncertainty, Disruption, and Transformation

By

Change is inevitable. What separates thriving organizations from those that falter is not the...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

Be Wary of Data

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Be Wary of Data

Locking Hierarchies

By Uwe Ricken

Comments posted to this topic are about the item Locking Hierarchies

Visit the forum

Question of the Day

Locking Hierarchies

You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level: 

SELECTo_orderdate,
        o_orderkey,
        o_custkey,
        o_storekey
FROMdbo.orders
WHEREo_orderkey = 3877;

What locking hierarchy will Microsoft SQL Server use?

 

See possible answers