Paul Hernández (4/15/2013)
Thanks for your quick answers.
In my case the source is a OLE DB component, and the reason to do such a things is the final destination is a Dynamics CRM.
I think the problem is, I´m trying to implement some logic in the ETL side that should be implemented by the CRM developers, but at the end we should determine the simple way for everyone.
So if a column contains 999 nulls and one actual value, that is fine. But 1,000 nulls and you want to lose the column mapping?
Sounds somewhat strange, tbh.
This dynamic (not 'Dynamics'!) mapping will take up a chunk of valuable development time to create a complex solution that ultimately will perform slower (from a SQL Server standpoint anyway) than the simple version. Have you no other choices?
Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this
If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.