Articles

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?

2008-04-15

5,915 reads

Blogs

Deploying an Updated Model with SQL Compare 16

By

In a previous post, I deployed a model to a database using SQL Compare...

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022

By

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...

Looking Back at the Redgate 2026 Company Kickoff

By

Last week I spent a few days in Cambridge, UK for the Redgate Company...

Read the latest Blogs

Forums

Adding and Dropping Columns II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding and Dropping Columns II

Leveraging DuckDB for OLAP Workloads: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Leveraging DuckDB for OLAP Workloads:...

More Documentation is Needed

By Steve Jones - SSC Editor

Comments posted to this topic are about the item More Documentation is Needed

Visit the forum

Question of the Day

Adding and Dropping Columns II

I have this table in my SQL Server 2022 database:

CREATE TABLE [dbo].[CityList]
(
[CityNameID] [int] NOT NULL IDENTITY(1, 1),
[CityName] [varchar] (30) ,
[Country2] [char] (3),
[stateprovince2] [char] (2),
[Country] [char] (3),
[stateprovince] [char]
) ON [PRIMARY]
GO
I decide to drop the stateprovince2 and country2 columns. What code should I use?

See possible answers