Data Quality

External Article

SQL Server Best Practices for Data Quality

  • Article

Accurate data is imperative for an organization to conduct cost effective decision making. Like everything else, change is constant for your data. There is a need to cleanse and validate data when received and on a regular basis. Unfortunately, cleansing and validating data is difficult with the native SQL Server toolset. How do we leverage the SQL Server tool set to achieve these goals?

2020-01-03

Technical Article

Data Degradation

  • Article

The other day at a conference, the subject of data degradation/corrosion arose. The speaker at the conference said that data in a database degraded or corroded over time. The statement was made as if degradation over time applied to all databases. I found this blanket statement to be misguided. Indeed, I think that data does degrade in some databases, but not all.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2009-05-14

2,180 reads

Blogs

A New Word: Semaphorism

By

semaphorism – n. a conversational hint that you have something personal to say on...

SQL Server Linux Container Images Got Smaller: Image Size and Startup Time Across Cumulative Updates

By

This week I was at PASS Data Community Summit in Seattle, and I attended...

Using AI to Build Semantic Models, Ontologies, and Fabric Data Agents

By

(This is the third post in a three-part series on how AI is changing...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

People Matter

By Grant Fritchey

Comments posted to this topic are about the item People Matter

Helping an English Student with R

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Helping an English Student with...

Visit the forum

Question of the Day

Adding Bits I

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