Email addresses are very prevalent in IT systems and often used as a natural primary key. The repetitive storage of email addresses in multiple tables is a bad design choice. Following is a design pattern to store email addresses in a single table and to retrieve them efficiently.
2017-09-15 (first published: 2015-09-24)
8,685 reads
A brief introduction to the sparse option and script to help decide when to use it
2016-08-25 (first published: 2015-04-10)
1,727 reads
2014-11-04 (first published: 2014-10-06)
1,365 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,700 reads
By SQLPals
Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...
By Steve Jones
Last week I spent a few days in Cambridge, UK for the Redgate Company...
By alevyinroc
This is long overdue but life and distractions happened. It’s been a little over...
Comments posted to this topic are about the item Adding and Dropping Columns II
Comments posted to this topic are about the item Leveraging DuckDB for OLAP Workloads:...
Comments posted to this topic are about the item More Documentation is Needed
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] GOI decide to drop the stateprovince2 and country2 columns. What code should I use? See possible answers
