The Myth Of Tomorrow
“We’ll fix it in the mix.”
“It’s good enough for right now.”
“We’ll worry about that later.”
“Your check is in the mail.”
Of...
2017-12-04
741 reads
“We’ll fix it in the mix.”
“It’s good enough for right now.”
“We’ll worry about that later.”
“Your check is in the mail.”
Of...
2017-12-04
741 reads
I came across this in a code review not long ago:
Three things pop into my head when I see this...
2017-11-27 (first published: 2017-11-13)
2,652 reads
I never had cause to give much consideration to storage when I was a SQL developer. The companies I worked...
2017-11-19
467 reads
In my experience, there are few database objects more poorly understood, misunderstood, misused, and outright abused, than the humble view....
2017-11-16 (first published: 2017-11-05)
2,003 reads
One of the most common mistakes I see made when creating tables (and I’ve been guilty of this myself too...
2017-10-29
569 reads
I started my IT career twenty years ago as a VB and C developer, wandered into C++ for a bit,...
2017-09-30
360 reads
Once upon a time I had a series about some cool stuff in Snowflake:...
By Steve Jones
“Most overnight successes – in fact any significant successes – take at least 5...
Comments posted to this topic are about the item Why Successful SQL Server Backups...
Comments posted to this topic are about the item Adding Bits II
Comments posted to this topic are about the item An Unlimited Token Budget
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] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, true)
GO
See possible answers