SQLServerCentral Article

NULL Column Analysis

NULL values in columns can indicate a few things, the value isn't known, it's not yet been filled in, or perhaps, as Leo Peysakhovich argues, the column isn't being used? How many SQL Server tables do you have with extra tables and columns that are not being used? Or maybe never have been? This article looks at a statistical analysis of columns using NULLs to determine if you might be able to remove certain columns.

SQLServerCentral Article

Win One of 5 XBOXs!!!!

By now everyone should have heard about the PASS 2004 Summit in Orlando this September. Hopefully you are also aware that SQLServerCentral.com is one of the sponsors for this event and to make it a bit special, we're putting on a reception for everyone that registers for PASS with our promotion code. Read on to see what we've got planned!

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