Articles

External Article

Contiguous Time Periods

It is always more efficient to maintain referential integrity by using constraints rather than triggers. Sometimes it isn't obvious how to do this. Until a recent idea by Alex Kuznetsov, the history table presented problems for checking data that were difficult to solve with constraints. Joe Celko explains.

2011-01-11

3,294 reads

Blogs

SQL Server Security: Always Encryption

By

As discussed introduction of Always Encryption blog and initial Encryption at rest as TDE...

SQL Server Security – TDE Encryption

By

Transparent Data Encryption(TDE): TDE was initially introduced in SQL Server 2008 Enterprise Edition; this...

A Las Vegas Break

By

Only a little break for me. I’m actually heading to Las Vegas today for ...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions

By dbruton95

Comments posted to this topic are about the item The Problem Isn't Always Your...

Identity Defaults

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identity Defaults

Visit the forum

Question of the Day

Identity Defaults

What happens when I run this code?

CREATE TABLE dbo.IdentityTest
(
     id int IDENTITY(10) PRIMARY KEY,
     somevalue VARCHAR(20)
)
GO

See possible answers