Hi,
Though this question has been asked numerous times before, I think I am one of the few people still who are still not 100% sure about what the deprecation of OLDDB means for SSIS/ SSAS,
The deprecation was announced several years ago (more than 5?) and here we are with SSIS 2016 and there is still no support for non OLEDB connection managers for components like Lookups. SSAS Multidimensional still reads via OLE DB drivers. There are other OLEDB only implementations too. Is there any definitive guide for OLEDB deprecation and what it means for SSIS (and SSAS Multidimensional)?
I have trawled through numerous forum posts and links but can’t say for sure if the direction is clear. Switching to ODBC doesn’t seem like an option due to performance reasons. ADO .Net is faster but still isn’t quite as fast as OLEDB.
Ofcourse we could start switching to something like ADO.Net for new development but this is still not what Microsoft recommended as OLEDB had been deprecated in favour for ODBC and also the fact that data loading performance using ADO.Net / ODBC connection manager is still not at par with OLEDB
Does anyone know what exactly is happening around it please? Any link or details published officially would be really helpful.
Though this question has been asked numerous times before, I think I am one of the few people still who are still not 100% sure about what the deprecation of OLDDB means for SSIS/ SSAS,
The deprecation was announced several years ago (more than 5?) and here we are with SSIS 2016 and there is still no support for non OLEDB connection managers for components like Lookups. SSAS Multidimensional still reads via OLE DB drivers. There are other OLEDB only implementations too. Is there any definitive guide for OLEDB deprecation and what it means for SSIS (and SSAS Multidimensional)?
I have trawled through numerous forum posts and links but can’t say for sure if the direction is clear. Switching to ODBC doesn’t seem like an option due to performance reasons. ADO .Net is faster but still isn’t quite as fast as OLEDB.
Ofcourse we could start switching to something like ADO.Net for new development but this is still not what Microsoft recommended as OLEDB had been deprecated in favour for ODBC and also the fact that data loading performance using ADO.Net / ODBC connection manager is still not at par with OLEDB
Does anyone know what exactly is happening around it please? Any link or details published officially would be really helpful.