External Article

Designing Tables for Audit Data in SQL Server

My company is just starting to look at adding functionality to retain historical data for key tables and columns for auditing purposes in many of our SQL Server databases. I have seen some of your recent tips related to triggers (Forcing Trigger Firing Order in SQL Server and Trigger Alternatives in SQL Server - OUTPUT Clause). Based on using triggers or a similar technology, what is the best way to store the historical data?

Blogs

Future-Proofing: How to Stay Ahead in FinOps

By

Cloud environments don’t sit still. Pricing models change, services evolve, workloads grow, and suddenly...

Introducing the SQL Server on Kubernetes Operator

By

Are you considering replatforming your SQL Server workload due to recent vendor changes, but...

Advice I Like: Rewards from Work

By

The greatest rewards come from working on something that nobody has words for. If...

Read the latest Blogs

Forums

Removing TDE

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Removing TDE

Poor Names

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Poor Names

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

Visit the forum

Question of the Day

Removing TDE

How do I remove TDE encryption of data from database xxx?

See possible answers