Database Weekly

SQLServerCentral Editorial

The Danger of Safety Assistance Tools

  • Editorial

During a speaker dinner the other week, a lot of topics were swirling around and a few caught my ear. One of these topics dovetailed nicely with a mistake I recently made. More on that later. The discussion was on the effect on safety that all the new safety-based tech is having on driving. Some […]

You rated this post out of 5. Change rating

2024-07-13

97 reads

SQLServerCentral Editorial

Is Perfect Software Attainable?

  • Editorial

I was in a social media discussion the other day where someone said “Perfection isn’t real, but progress is.” This started me thinking, is there really no perfection? Can you not actually create a piece of software that is perfect? Of course you can. As long as your requirements are perfect, and the code does […]

You rated this post out of 5. Change rating

2024-06-08

116 reads

SQLServerCentral Editorial

Realities of Predictive Analysis

  • Editorial

Or for short, “Why you have to play the game” “Don't tell me the odds”, cried out Han Solo just before doing something that seemed impossible. How on Coruscant did he do that? Well, as a certain director said about a certain floating door in a galaxy we all call home. ”It was in the […]

You rated this post out of 5. Change rating

2024-05-18

99 reads

SQLServerCentral Editorial

Do you listen to music when you work?

  • Editorial

I want to make this a participation topic. When you are working, do you listen to music or do you need quiet? And if it isn’t music, do you do something else? TV, movies? For me, it is almost always music. As I write my first Database Weekly newsletter editorial in a few months, I […]

You rated this post out of 5. Change rating

2024-04-20

210 reads

SQLServerCentral Editorial

Sharing the Work You Do 

  • Editorial

During one my yearly review, I got one particularly interesting piece of feedback. “You need to share the work you are doing and share with the company.” This is basically a matter of letting people know about the stuff we are putting out on Simple-Talk.com. It is something that is regularly done here, but to […]

You rated this post out of 5. Change rating

2024-01-27

103 reads

SQLServerCentral Editorial

Being A Bit Less Comfortable in 2024

  • Editorial

I hate coming up with ideas for editorials, but my last editorial of the year gives me a very simple topic just staring me in the face: New Year’s Resolutions. Love them or hate them (or it we are honest, a good bit of both,) this end of one year and the start of another […]

You rated this post out of 5. Change rating

2023-12-30

178 reads

Blogs

Exploring DiskANN: Part 2: PQ, SSDs, caching and beam search

By

How I used AI for this postChatGPT to generate images based on info specifically...

T-SQL Tuesday #202: The Two Outages I Won't Ever Forget

By

My T-SQL Tuesday #202 entry for Marlon Ribunal's invitation on memorable SQL Server outages....

Measuring RAG Solutions: Are We Retrieving the Right Information?

By

A RAG pipeline that answers questions in the demo is not the same thing...

Read the latest Blogs

Forums

Performance Regression After Upgrading from SQL Server 2016 to 2022

By abdalah.mehdoini

Hello everyone, Last week we performed an upgrade of our SQL Server instance, moving...

Adding new column with DEFAULT

By Thomas Franz

Comments posted to this topic are about the item Adding new column with DEFAULT

How do I connect to a SQL Server database on my ISP?

By Doctor Who 2

I've got a web application for my side business. I've added a SQL Server...

Visit the forum

Question of the Day

Adding new column with DEFAULT

Which number will the COUNT() return after executing the following statements:

DROP TABLE IF EXISTS #test;
CREATE TABLE #test (id INT)
INSERT INTO #test (id)
SELECT *
  FROM GENERATE_SERIES(1, 3) AS gs
;

ALTER TABLE #test ADD flag BIT CONSTRAINT DF_#test_flag DEFAULT 0;
go
UPDATE #test SET flag = 0 WHERE id = 1
UPDATE #test SET flag = 1 WHERE id = 2

INSERT INTO #test (id) VALUES (4)

SELECT COUNT(*)
  FROM #test AS t
 WHERE flag = 0
 

See possible answers