SQLServerCentral Article

Parallel Processing of Large Volume ETL Jobs

ETL processing, generally involves copying/moving, transforming, cleaning the records/transactions from one or multiple sources. Most of the batch processing or warehousing projects involve such data processing in millions on daily/weekly basis. Typically, there is a Staging area and production area. Records are cleaned, transformed, filtered and verified from staging to production area. This demands SQL Set theory based queries, parallel processing with multiple processors/CPU. The article focuses on need of SQL Set theory approach and parallel processing while processing large volume of ETL records using programming approach.

External Article

SQL Puzzle 7

After a gap of sixteen months, Lionel Clarke, the creator of the only 3-D maze game to be written in TSQL, returns with a new SQL puzzle. It is very simple. You have to move as much of the data as you can from the source tables to the destination tables.

Blogs

Why your data still can’t answer a simple question 

By

Every organization I talk to has the same problem dressed up in different clothes....

T-SQL Tuesday #197 Invitation – An impactful session or two from a conference

By

I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...

Did You Really Name That Default?

By

Ten years (and a couple jobs) ago, I wrote about naming default constraints to...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions

By dbruton95

Comments posted to this topic are about the item The Problem Isn't Always Your...

Identity Defaults

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identity Defaults

Visit the forum

Question of the Day

Identity Defaults

What happens when I run this code?

CREATE TABLE dbo.IdentityTest
(
     id int IDENTITY(10) PRIMARY KEY,
     somevalue VARCHAR(20)
)
GO

See possible answers