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.

2009-05-14

2,180 reads

Blogs

Redgate Summit Comes to the Windy City

By

I love Chicago. I went to visit three times in 2023: a Redgate event,...

Non-Functional Requirements

By

I have found that non-functional requirements (NFRs) can be hard to define for a...

Techorama 2024 – Slides

By

You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...

Read the latest Blogs

Forums

AG listener cant be removed

By ysalem

Testing with AG on Linux with Cluster=NONE. it was all going ok and as...

Remove comma inside Comma Delimited File csv in SSIS Using Script task

By hongho2

Hi, I have two tables: one for headers with 9 fields and another for...

Inserting 100K rows Performance - Baseline Performance

By MichaelT

We're trying to understand how quick new versions of SQL server can be.  Obviously...

Visit the forum

Question of the Day

The "ORDER BY" clause behavior

Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:

create table t1 (id int primary key, city varchar(50));

insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);
If we execute the following query, how will the records be sorted in both environments?
select city

from t1

order by city;

See possible answers