Articles

Technical Article

Techniques for Uniquely Identifying Database Records

When designing and creating a data model for a data-driven application, the records in tables must each be uniquely identifiable. By having a unique value associated with each record, individual records can be selected, updated, or deleted. Being able to uniquely identify records is so important and standard in a database system that databases allow those designing a database table to specify what column (or columns) make up the primary key.

2006-12-22

3,518 reads

External Article

Tales of Corporate Espionage

All good detective stories have a femme fatale. In the case of corporate espionage scandals, Celia Goodson, a seasoned businesswoman and once a glossily groomed blonde, has been involved in investigating more business transgressions to hit the City in the last three decades than anyone else of her years.

2006-12-21

2,627 reads

Blogs

Microsoft Fabric Data Agents: Bringing Structured and Unstructured Data Together

By

Most enterprise questions do not live neatly in one place. The numbers may be...

Keeping Redshift System Table History Past 7 Days with S3 Tables

By

Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...

Updating the Data API Builder

By

I was updating my session for the Data API Builder (DAB) recently, mostly to...

Read the latest Blogs

Forums

Parameter Sensitive Plan Optimization vs. Parameter Sniffing: What SQL Server Fixes and What It Doesn't

By vgupta

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization vs....

Hyperscale Replicas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hyperscale Replicas I

The End of Summer

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The End of Summer

Visit the forum

Question of the Day

Hyperscale Replicas I

What types of secondary replicas are available for the Azure SQL Database Hyperscale edition?

See possible answers