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

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCP Mangga Dua Square,Telpon/WA 08213111159

By Bonglua

Mangga Dua Square, Komp. Ruko, Jl. Gn. Sahari Blok G No. 8-9, Daerah Khusus...

BCA KCU SUBANG Telp:cs.08218171955

By telediousnom7887

Whatsapp:08218171955 Jl. Otto Iskandardinata No.37, Karanganyar, Kec. Subang, Kabupaten Subang, Jawa Barat 41211

BCA KCP Siantan No.Telp:087757645171

By Xay Nha Nhanh

 Whatsapp:087757645171 Jl. Khatulistiwa No.16, Siantan Hilir, Kec. Pontianak Utara, Kota Pontianak, Kalimantan Barat 78242

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers