Custom ETL performance issue
We have serious performance issue with a Telco DW application. I have reached my wits end with my analysis; hoping to get some bright ideas from this forum - 1. ETL process starts with a nightly call record file that coule range from 20-25Million records
2. SQL Load direct path into a staging table (I would have prefered an external table, but this is what I have). No issues with the load as such
3. No ETL/ELT tool in use. A .Net application processes the staging tables in multiple streams, does some 'minor' transformations, and inserts into a set of DW tables
0