The Scary DBA

Blog Post

Look Into Chocolatey

Just a suggestion, but I’d say you should look into Chocolatey. Let me explain why. Sabbatical For those who don’t know I was recently on a six-week sabbatical from...

2022-09-23 (first published: )

360 reads

Blog Post

Thank You Andy!

I remember going into Andy Leonard’s session at PASS Summit in Denver. I’m not going to lie, it was kind of sparsely attended, so I got to sit up...

2022-08-02

20 reads

Blog Post

Thank You Tim!

Ah, Tim Ford. I remember the time we were sitting at Ruth Kriss Steakhouse trying to figure out which of the two of us was the dumbest person in...

2022-08-12 (first published: )

261 reads

Blogs

Word to the wise: don’t turn on SQL vulnerability checks on a blog about SQL

By

Recently, in an attempt to thwart leechers (1990s kids will know), I added some...

Dazzling Stuff in Databricks (SQL) – Qualify

By

Once upon a time I had a series about some cool stuff in Snowflake:...

Advice I Like: Overnight Success

By

“Most overnight successes – in fact any significant successes – take at least 5...

Read the latest Blogs

Forums

Why Successful SQL Server Backups Are Not Enough

By Almighty

Comments posted to this topic are about the item Why Successful SQL Server Backups...

Adding Bits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding Bits II

An Unlimited Token Budget

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unlimited Token Budget

Visit the forum

Question of the Day

Adding Bits II

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, true)
GO

See possible answers