External Article

SQL Data Aggregation Aggravation

When we have to deal with and store a lot of data, it makes sense to aggregate it so that we store only the information we actually need. If we get this right, this works well, but the design of the system takes care and thought because the problems can be subtle and various. Joe Celko describes some of the ways that things can go wrong and end up providing incorrect, inaccurate or misleading results.

Blogs

Case Studies: Real-World Success Stories of FinOps Implementation

By

Learning any kind of theory is easy, but adapting FinOps and watching it rescue...

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...

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