Too often, denormalization is suggested as the first thing to consider when tackling query performance problems. It is said to be a necessary compromise to be made when a rigorous logical design hits an inadequate database system. As the saying goes, “Normalize ‘til it hurts, then denormalize ‘til it works”. In reality, Denormalization always leads eventually to tears.
2008-07-28
7,924 reads
Learn how to build a B-tree similar to those used by databases to implement indexes.
2008-06-25
3,117 reads
Last time, we discussed Table inheritance, which allowed us to easily reduce redundancies in our table design by creating "base" or "super" tables that contain columns and relations that "sub-tables" automatically inherit.
2008-05-28
3,163 reads
In this article I will try to address some of the design suggestions and experiences that I had in managing similar database.
2008-05-19
7,912 reads
Part 15 of this series examines what cost is paid when tables are separated into multiple databases on the same server.
2008-05-05
2,879 reads
In our organization, I have noticed that database requirements are never included as a portion of the system requirements. The requirements always focus on the interface and we derive the database design from the interface as well as fill in some of the gaps.
2008-03-26
3,950 reads
Entity-Attribute-Value model (EAV) is used interchangeably with name for name value pair. This article will try to address advantages and disadvantages of EAV modelling
2008-03-24
7,297 reads
When designing a database, we sometimes come across situations where there are multiple types of entities that we are modeling, but we'd like them to all have certain attributes or relations in common. Using "sub-type" tables is a simple way to implement table inheritance in SQL Server.
2008-03-12
3,864 reads
This is one in a series of articles dealing with Database Design following the design of a single system from start to finish.
2008-01-31
3,879 reads
An exploration of the process of translating a conceptual model to a logical model, and ultimately, a faithful implementation using T-SQL.
2008-01-03
2,897 reads
Creating a Fabric workspace takes about 30 seconds. Restructuring workspaces after people have built...
By Steve Jones
It’s a small change, but a handy one. Flyway Desktop (FWD) now includes the...
By Steve Jones
Software is hard. While I love our Lucid Gravity, I realize that they are...
Comments posted to this topic are about the item Adding new column with DEFAULT...
Comments posted to this topic are about the item Advanced Deployment Scenarios: Stairway to...
Comments posted to this topic are about the item You Need a DBA Pipeline
Which number did the two COUNT(*) return:
DROP TABLE IF EXISTS #tmp CREATE TABLE #tmp (id INT NOT NULL) INSERT INTO #tmp (id) SELECT gs.value FROM GENERATE_SERIES(1, 5) AS gs ALTER TABLE #tmp ADD my_value INT NOT NULL CONSTRAINT df_tmp_my_value DEFAULT 1 SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1 ALTER TABLE #tmp DROP CONSTRAINT df_tmp_my_value ALTER TABLE #tmp ADD CONSTRAINT df_tmp_my_value DEFAULT 2 FOR my_value SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1See possible answers