SQLServerCentral Article

Nullable vs Non-Nullable Columns and Adding Not Null Without Downtime in PostgreSQL

In this article, we are going to talk about nullable and non-nullable columns specifically related to Postgres databases. While the reasons to use nullable or non-nullable columns may seem obvious at first, there are pitfalls associated with each decision that either affect development velocity, affect application performance, or cause downtime. Let's start with definitions. Nullable […]

Blogs

Using SQL Compare with Redgate Data Modeler

By

Redgate recently released SQL Compare v16, which included a new feature to work with...

Who’s the Winningest Coach (with AI Help)

By

I was listening to the radio the other day and the hosts were discussing...

Learning from Mistakes: T-SQL Tuesday #194

By

We’re a week late, once again my fault. I was still coming out of...

Read the latest Blogs

Forums

Azure-SSIS, Self-Hosted Integration Runtime, & Data Gateway?

By jasona.work

Looking to confirm my understanding of these three products and how they can be...

Basic Always On Groups Randomly Stop Synchronizing

By Leo.Miller

In one of my environments I have 3 pairs of Always On SQL 2022...

Learning From Breakage

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Learning From Breakage

Visit the forum

Question of the Day

Adding and Dropping Columns I

I have this table in my SQL Server 2022 database:

CREATE TABLE [dbo].[CityList]
(
[CityNameID] [int] NOT NULL IDENTITY(1, 1),
[CityName] [varchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO
I decide to add two new columns for the StateProvince and Country. What code should I use?

See possible answers