External Article

Intelligent Conditional Split in an SSIS Package

Conditional Split is one of the most commonly used transforms in any SSIS Package development routine. The limitation with conditional split is that any record that satisfies the first condition from the conditions list is routed to its corresponding path exclusively. In a logical sense, a record might satisfy more than one condition and one might want the record to be routed to all paths for processing, but with the Conditional Split transform this is not possible. We need a more intelligent conditional split where we can selectively route the records to more than one output path. In this tip we will look at how to facilitate this intelligent conditional split.

SQLServerCentral Editorial

Can I really drop that index?

You believe that an index is unused and so could be removed, and yet, your finger hovers nervously over the metaphorical "delete" button. You can't quite bring yourself to do it. Is it really safe to drop this index? Tony wonders if "invisible indexes" might solve this dilemma.

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 Balai Pustaka Tlpn/wa:085373737551

By balijepalli.p

Jl. Balai Pustaka Timur, Blok J No. 225, C, RT.4/RW.3, Wil, Kec. Pulo Gadung,...

Pt BCAFinance Bontang,Telp/Wa 0821.3111.159

By fougito

Jl. R. Suprapto No.81, Api-Api, Kec. Bontang Utara, Kota Bontang, Kalimantan Timur 75313

BCA Multifinance,Telp/Wa 0821.3111.159

By fougito

5X88+8MH, Sampit, Kec. Delta Pawan, Kabupaten Ketapang, Kalimantan Barat 78811

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